📊 Full opportunity report: A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Anthropic has shifted its AI strategy by defining Skills as folders, not prompts, containing instructions, scripts, and assets. This approach enhances consistency, onboarding, and asset value. The company ran hundreds of Skills internally, emphasizing their role as durable organizational assets.
Anthropic has announced a fundamental redefinition of what constitutes a ‘Skill’ in AI agent development, framing it as a folder containing instructions, scripts, and data rather than a simple prompt. This shift aims to create durable, reusable organizational assets, moving beyond ad-hoc prompting to structured, versioned capabilities that improve consistency and onboarding across teams.
In a detailed write-up from a Claude Code engineer, Anthropic explains that a Skill is a folder—not just a prompt—containing various components such as instructions, reference documents, scripts, templates, and configuration files. This structure allows AI agents to discover, read, and execute the contents dynamically, leading to more reliable outputs.
This approach transforms how organizations develop and maintain AI capabilities, emphasizing the importance of bundling tribal knowledge, guardrails, and tools into a single, versioned asset. The company reports that its internal use of hundreds of Skills has led to improved consistency, faster onboarding, and the ability to iteratively improve capabilities over time. Anthropic’s internal catalog identifies nine categories of Skills, ranging from code scaffolding to infrastructure operations, with verification Skills deemed most valuable because they catch mistakes before output reaches users.
Anthropic advocates dedicating engineering effort to perfecting Skills, viewing them as appreciating assets that encapsulate organizational knowledge, rather than disposable prompts or notes. The company’s approach underscores the importance of defining Skills precisely, including clear descriptions and ‘gotchas’—trap points learned from experience—to ensure effective activation and use by AI agents.
A Skill is a folder, not a prompt
Anthropic published what it learned running hundreds of Skills across its own engineering org. Read as a business memo, the point is bigger than a coding trick: this is how ad-hoc prompting becomes durable institutional capability — the SOPs your agents actually follow, versioned and shared.
“A Skill is just a clever markdown prompt you save in a file.”
A folder the agent can discover, read & run — instructions, scripts, references, templates, config & on-demand hooks.
The knowledge of how your organization actually operates can be captured, versioned, shared & executed — and the thing capturing it is a humble folder with a script and a gotchas list inside. For the builder, that’s context engineering with real tools attached. For whoever owns the budget, it’s the difference between AI that starts from zero every morning and an asset that compounds. Caveats: best practices are still evolving, checked-in Skills cost context, and curation beats accumulation. Start with one Skill, one gotcha, and the category that catches your mistakes.
Implications for Organizational AI Development
This new understanding of Skills as folders containing comprehensive instructions and assets has significant implications for how companies develop, deploy, and maintain AI systems. It shifts the focus from one-off prompts to durable, versioned capabilities that can be shared, improved, and scaled across teams. This approach promises more consistent outputs, faster onboarding of new personnel, and an overall increase in the value derived from AI investments. As organizations adopt this model, it could redefine standard operating procedures for AI-driven workflows, making them more reliable and easier to audit or update.
AI development folder structure tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
From Prompt Engineering to Asset Building
Until now, most teams using AI coding agents relied on prompt engineering—crafting and reusing prompts to guide model behavior. However, this method often results in inconsistent outputs and poor scalability. Anthropic’s internal experience with hundreds of Skills, developed over time, demonstrates that packaging knowledge into structured folders improves reliability. The concept of Skills as assets builds on prior efforts but formalizes it as a reusable, version-controlled container for organizational knowledge. This development aligns with broader trends toward modular, maintainable AI systems.
“Viewing Skills as folders containing instructions and scripts fundamentally changes how organizations can build and scale reliable AI capabilities.”
— Thorsten Meyer, AI researcher
Handbook of Research on Scripting, Media Coverage, and Implementation of E-learning Training in Lms Platforms
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unclear Aspects of Skills Implementation
It remains unclear how widely adopted this approach will become outside Anthropic, or how easily organizations can transition from prompt-based methods to folder-based Skills. Details about the tooling, standards, and management practices for maintaining large Skills libraries are still emerging. Additionally, the long-term impact on AI performance and cost-efficiency has yet to be fully assessed.
AI-Assisted Creative Asset Version Control: Digital Content Management That Tracks Project Evolution
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Broader Adoption and Development
Organizations interested in this approach should evaluate how to structure their own Skills libraries, focusing on categorization, documentation, and version control. Anthropic is expected to continue refining its internal practices and may release tools or frameworks to facilitate adoption. Monitoring how the industry responds and whether other AI developers adopt similar models will be key in understanding the future landscape of organizational AI capabilities.
The Field Guide to Extending Your AI: MCP Servers, Skills, Hooks, and Subagents — and How to Search Before You Build
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How is a Skill different from a prompt?
A Skill is a folder containing instructions, scripts, and data—an organized asset—whereas a prompt is a single instruction or question sent to the AI. Skills enable reusable, structured capabilities that can be discovered and executed dynamically.
What benefits does packaging Skills as folders provide?
Packaging Skills as folders improves consistency, accelerates onboarding, and creates a durable asset that can be iteratively improved, shared, and versioned across teams.
Will this approach work for all types of AI tasks?
While particularly beneficial for complex, repetitive, or operational workflows, the folder-based Skills approach can be adapted to various AI applications requiring reliability and maintainability.
What are the main challenges in adopting Skills as folders?
Challenges include establishing standards for folder structure, managing version control, integrating with existing workflows, and training teams to design effective Skills.
Is this approach specific to Anthropic’s models?
While developed by Anthropic, the concept of organizing AI capabilities into structured, reusable assets could be adopted by other organizations and AI platforms seeking more reliable and scalable solutions.
Source: ThorstenMeyerAI.com
