Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I’ve been using 60% Apple-style corner smoothing all the time. But whenever I explain it to Codex or Claude Code, they often miss the point. So I made a skill that anyone can use with their AI agents: npx skills add gabrielobholz/corner-smoothing-skill Now I can simply say: “Create a...

95,520 Aufrufe • vor 16 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 Aufrufe • vor 2 Monaten

Making OpenCode as lean as Pi agent? Just trimmed 25k out of OpenCode's system prompt (from 30k to 4-5k tokens) How? Just disable skills and get rid of massive skill definition bloat. Who needs skills anyway? Just kidding, this is the not the way. It makes the agent lame and defeats the point of using one. But it sets a precedent: Find a way to use skills without their definitions pre-loaded into the system prompt every single turn. Another interesting stuff: Upon testing this temporary "no skill setup" with two of hottest OpenCode Zen free models, Mimo V2.5 vs DeepSeek V4 Flash: One thinks more and talks less One thinks less and talks more Check the video to see which is which If you made it here, I'm finding a way to leanest OpenCode setup that I can get I simply don't believe that OpenCode can't be as lean as Pi Upon tinkering, I made a plugin that temporarily extracts the system prompt while I test, and noticed the hundreds of definitions in it from my .agents/skills directory which is shared across all my coding agents (Cursor, Antigravity, Claude, etc.) Of course disabling skills is not the answer, but it just proved that there is a way to strip the system prompt of these massive skill defs Aside from the system prompt hierarchy that injects confusion imo if you have a conflicting and redundant AGENTS.md which I discovered upon digging into OpenCode's source code Apparently it has prompt.ts/system.ts/instruction.ts/llm.ts and loads base .txt prompts based on model family (claude/gpt-o/gpt-5/codex/gemini/others) that all work together to make OpenCode aware of who it was and how it should use tools and become a "coding agent" Gotta find the most minimal mix that fits right into my workflow Make OpenCode as lean as Pi? We'll see. All in

raymel 👋

37,196 Aufrufe • vor 1 Monat

How to build a viral Web3 app in an afternoon using the ChainGPT AI skill for Claude Code. No coding experience required. I built Roast My Wallet. Paste any Ethereum wallet address, get a savage AI-generated roast of your trading history, a Degen Score out of 100, an on-chain report card, and three AI-generated NFT portraits. Here's exactly how it came together. Setup (3 minutes): 🔸Install Claude Code at 🔸Run /plugin install ChainGPT-org/chaingpt-claude-skill 🔸Get an API key at 🔸Type /chaingpt and describe what you want to build What the skill actually does: The ChainGPT skill doesn't just give you starter code. It knows the entire API. Every endpoint, every parameter, every credit cost, every error code. When I asked it to build the roast feature, it knew to call the LLM endpoint, how to stream the response back to the browser in real time, and how to handle errors automatically. I didn't look up a single thing. How it works under the hood: 1. Pulls real ETH balance and transaction count from the Ethereum blockchain 2. Feeds those numbers into ChainGPT's LLM and streams the roast back live 3. Calculates a Degen Score from your tx count vs balance ratio 4. Generates a report card with letter grades across Trading, Patience, Risk, Diamond Hands, and NGMI 5. Uses the roast text to generate three custom NFT portraits in parallel via VeloGen 6. Packages everything into a downloadable PNG card ready to post 7. Every feature came from describing what I wanted: 8. "Make the API key server-side." Done. 9. "Add an animated arc gauge for the degen score." Done. 10. "Generate NFT portraits using the roast text as context." Done. I never wrote a function or debugged an API response. I described outcomes. The ChainGPT skill handled the rest. If you can describe what you want to build, you can build it. Get your API key. Install the skill. /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build with ChainGPT AI!

ChainGPT

29,279 Aufrufe • vor 2 Monaten

Claude Code can now watch & analyze ANY video 🤯 I built a skill that gives Claude the ability to watch any video file you drop in — UGC ads, competitor Meta ads, organic TikToks, screen recordings, anything. All inside Claude Code. Perfect for DTC brands and agencies who study competitor creative every week to figure out what's working and what to test next. Here's the problem: If you're studying competitor ads on Meta or hooks on TikTok, you're scrubbing through videos manually, pausing to write down hooks, screenshotting on-screen text, and trying to remember what made the ad land by the time you've watched 10 of them. This skill solves it: → Drop any video file into Claude Code → Skill routes it through the Gemini API for native video understanding → Returns a full creative teardown — hook breakdown, target audience, angle, beat-by-beat, on-screen text verbatim → Surfaces the steal-worthy patterns you can apply to your own creative → Same skill works on UGC ads, produced video ads, organic TikToks, and Loom recordings No manual scrubbing. No pausing every 5 seconds. No $200/mo ad intelligence platform. What you get: - Native video understanding via Gemini (not just transcripts) - Structured analysis — hook, angle, audience, pain point, CTA - Verbatim on-screen text and dialogue with timestamps - Hook variations generated directly from competitor ads - About 27 cents per 30-minute video Built 100% in Claude Code with the Gemini API. I recorded a full breakdown showing exactly how I built this and I'm giving away the skill for free. Want the skill? > Comment "CLAUDE" + > Like this post And I'll send it over (must be following so I can DM)

Mike Futia

35,489 Aufrufe • vor 2 Monaten

Claude Code + Nano Banana 2 is f*cking cracked 🤯 I built a skill inside Claude Code that writes JSON image prompts for Nano Banana 2, and the outputs look like they came from a professional photo shoot. One plain-text prompt. Claude rewrites it as structured JSON with lighting, camera, composition, style, and negative prompts. Then fires it off to Nano Banana 2. All inside Claude Code. Perfect for DTC brands and agencies who need high-volume ad creative without booking a shoot. If you're using Nano Banana 2 for product shots and lifestyle images but every generation feels like pulling a slot machine lever — random lighting, inconsistent style, plastic skin, misspelled labels ... This skill fixes the entire output: → You describe what you want in plain English → Claude rewrites it as a structured JSON prompt (lighting, camera angle, lens, depth of field, color grading — all of it) → Fires it to Nano Banana 2 via API → Saves the prompt + image in organized folders → You iterate on the style until it's dialed, then every output matches No more slot machine prompting. No more inconsistent brand imagery. No more burning credits on unusable generations. What you get: - Photo-realistic product shots and lifestyle images on demand - Full control over style, lighting, composition, and camera settings - Saved JSON prompts you can reuse across every campaign - A skill that gets smarter the more feedback you give it Built 100% in Claude Code with a custom skill + Python scripts. I put together a full playbook showing the exact skill, the JSON schema, and the workflow to set this up yourself. Want the full playbook? > Like this post > Comment "BANANA" And I'll send it over (must be following so I can DM)

NOVA

63,725 Aufrufe • vor 4 Monaten

Claude Code + Nano Banana 2 is f*cking cracked 🤯 I built a skill inside Claude Code that writes JSON image prompts for Nano Banana 2, and the outputs look like they came from a professional photo shoot. One plain-text prompt. Claude rewrites it as structured JSON with lighting, camera, composition, style, and negative prompts. Then fires it off to Nano Banana 2. All inside Claude Code. Perfect for DTC brands and agencies who need high-volume ad creative without booking a shoot. If you're using Nano Banana 2 for product shots and lifestyle images but every generation feels like pulling a slot machine lever — random lighting, inconsistent style, plastic skin, misspelled labels ... This skill fixes the entire output: → You describe what you want in plain English → Claude rewrites it as a structured JSON prompt (lighting, camera angle, lens, depth of field, color grading — all of it) → Fires it to Nano Banana 2 via API → Saves the prompt + image in organized folders → You iterate on the style until it's dialed, then every output matches No more slot machine prompting. No more inconsistent brand imagery. No more burning credits on unusable generations. What you get: - Photo-realistic product shots and lifestyle images on demand - Full control over style, lighting, composition, and camera settings - Saved JSON prompts you can reuse across every campaign - A skill that gets smarter the more feedback you give it Built 100% in Claude Code with a custom skill + Python scripts. I put together a full playbook showing the exact skill, the JSON schema, and the workflow to set this up yourself. Want the full playbook? > Like this post > Comment "BANANA" And I'll send it over (must be following so I can DM)

Mike Futia

211,416 Aufrufe • vor 4 Monaten