📊 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 shared insights from running hundreds of Skills internally, emphasizing that a Skill is a folder—not just a prompt. This approach improves consistency, onboarding, and asset value in AI agent development.
Anthropic has redefined the concept of a Skill in AI agent development, emphasizing that it is a folder containing instructions, scripts, data, and configurations, rather than a mere prompt or markdown file. This shift, based on the company’s experience running hundreds of Skills internally, aims to create more durable, consistent, and reusable organizational assets for AI systems.
In a detailed write-up from a Claude Code engineer, Anthropic explains that a Skill is essentially a container—like a folder—that can hold various components such as instructions, reference documents, runnable scripts, templates, and configuration hooks. This approach allows the AI agent to discover, read, and execute the contents of the folder, making the Skill a comprehensive asset rather than just a prompt.
Anthropic’s internal experience shows that Skills improve output consistency, reduce onboarding time, and compound in value as they are refined over time. The company categorizes Skills into nine types, including library references, product verification, data analysis, automation, code scaffolding, review, deployment, runbooks, and infrastructure operations. The most impactful, according to Anthropic, is verification—ensuring outputs are correct and mistakes are caught.
Technical lessons emphasize that effective Skills should avoid stating what the agent already knows, focus on non-obvious, organization-specific knowledge, and include ‘gotchas’—trap points learned from past errors. Descriptions for Skills act as trigger definitions, matching user requests with the appropriate folder-based Skill, which can include scripts and helper functions for execution.
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.
Why Treating Skills as Folders Changes AI Development
This approach fundamentally shifts how organizations build, maintain, and scale AI agents. By packaging knowledge, tools, and routines into reusable folders, companies can achieve more consistent outputs, streamline onboarding for new team members, and create a growing library of institutional memory. It transforms ad-hoc prompting into durable operational procedures, making AI systems more reliable and easier to evolve over time.
For businesses, this means AI can become a more integral part of operational workflows, with Skills acting as assets that improve with use. The emphasis on verification Skills also highlights a focus on output quality, reducing errors and increasing trust in AI-generated results.
AI development folder structure
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Internal Practice and Industry Implications of Folder-Based Skills
Anthropic’s internal experience with running hundreds of Skills has shown that categorizing and refining them into nine types has helped identify organizational gaps and improve performance. The concept of Skills as folders is a departure from traditional prompt engineering, which often treats prompts as ephemeral instructions. This shift aligns with broader industry efforts to make AI systems more maintainable, scalable, and aligned with business processes.
While the approach is still emerging, it reflects a growing recognition that AI development benefits from structured, asset-based methods rather than ad-hoc prompt tuning. Other organizations are likely to explore similar strategies to improve consistency and knowledge retention in AI workflows.
“A Skill is a folder — one that can contain instructions, reference documents, runnable scripts, templates, data, configuration, and hooks that fire only while the Skill is active.”
— Thorsten Meyer, AI engineer at Anthropic
AI scripting and automation tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unanswered Questions About Folder-Based Skills
It is not yet clear how broadly this approach will be adopted outside Anthropic or how it will scale in different organizational contexts. Details remain internal, and the specific technical implementation, such as integration with existing systems and tooling, are still evolving. Additionally, the long-term impact on AI reliability and maintenance has yet to be empirically measured.
AI instruction and data management software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Industry Adoption and Development
Organizations interested in this approach should evaluate their own knowledge management and automation workflows for potential migration to folder-based Skills. Anthropic is likely to continue refining their implementation, and other AI teams may experiment with similar structures. Future developments may include standardized frameworks for Skills management, tooling for easier creation and updating, and broader industry discussions on best practices for asset-based AI development.
AI agent configuration templates
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does treating a Skill as a folder improve AI consistency?
By containing instructions, scripts, and data in one organized container, Skills ensure that the AI agent follows a well-defined, repeatable process, reducing variability in outputs.
Can this approach be applied to existing AI systems?
Yes, organizations can start by mapping their current prompt-based workflows into folder-based Skills, gradually replacing ad-hoc prompts with structured assets.
What are the main technical requirements for implementing folder-based Skills?
It requires systems capable of discovering, reading, and executing folder contents, including scripts and configurations, and a way to trigger Skills based on user requests or internal events.
Will this method eliminate the need for prompt engineering?
Not entirely, but it shifts the focus from crafting prompts to developing comprehensive, reusable assets that encode organizational knowledge and routines.
Source: ThorstenMeyerAI.com
