{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/69b2ef7a25f345603a1b4b3f/69bc3e791861d127d567ffd4?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"Episode 3: Turn Claude into an Autonomous Workforce","thumbnail_width":200,"thumbnail_height":200,"thumbnail_url":"https://open-images.acast.com/shows/69b2ef7a25f345603a1b4b3f/1773944065152-70fdb8bc-6c29-41a8-a882-7cf6504531b5.jpeg?height=200","description":"<p>This episode breaks down Claude Skills — the technology that transforms a standard AI chatbot into a self-managing, autonomous workforce.</p><p><br></p><p>Tank and Link open with the \"amnesiac intern\" problem — why copy-pasting the same prompts every day is killing productivity — and explain how Skills solve it permanently.</p><p><br></p><p><strong>What they cover:</strong></p><p><br></p><p><strong>What a Skill actually is.</strong> Not a long prompt — a full folder structure containing instruction files, Python scripts, brand templates, and data files. The AI gets tools, not just text.</p><p><br></p><p><strong>Progressive context loading.</strong> How Claude manages hundreds of skills without burning through tokens — scanning a \"menu\" of tiny summaries first, then only loading what's needed for the task.</p><p><br></p><p><strong>Three ways to trigger skills.</strong> Plain language, explicit name-drop, or a direct slash command. Plus the safety switch that prevents high-stakes skills (like deploying code) from ever running autonomously.</p><p><br></p><p><strong>Parallel execution.</strong> How one person can fire off four different AI agents simultaneously — calendar planning, project review, diagram generation, audience analysis — all running in the background while they focus on creative work.</p><p><br></p><p><strong>Anti-AI-slop design.</strong> Anthropic's official front-end design skill that explicitly bans purple gradients, Arial fonts, and generic rounded corners — and how to prompt for actual taste.</p><p><br></p><p><strong>The Figma MCP.</strong> How Claude plugs directly into Figma files to read raw design data and generate pixel-perfect code, not guesswork from screenshots.</p><p><br></p><p><strong>Real business use cases.</strong> A multimillion-dollar agency using skills to automate their entire sales pipeline — LinkedIn lead scraping, personalised follow-up emails, and campaign cloning — all from a single slash command.</p><p><br></p><p><strong>The gotchas section.</strong> Why the most important part of any skill is a list of known mistakes the AI makes, not just instructions on what to do.</p><p><br></p><p><strong>Skills 2.0 and the auto-research loop.</strong> Skills that test themselves, grade their own output against a rubric, rewrite their own instructions, and iterate overnight until they hit near-perfect performance.</p><p><br></p><p><strong>The closing thought:</strong> What happens when you build a skill whose job is to observe your habits and invent new skills you haven't thought of yet?</p>","author_name":"Tank and Link @ Foundry Works Ai"}