📊 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 demonstrated that building AI capabilities involves creating reusable ‘Skills’ as folders with instructions and tools, rather than simple prompts. This approach enhances consistency, onboarding, and institutional memory, marking a shift in how organizations deploy AI.

Anthropic has revealed that its internal AI ‘Skills’ are structured as folders containing instructions, scripts, and assets, not just prompts. This approach, based on extensive internal testing, aims to standardize and improve organizational AI workflows, making them more durable and reusable. The development marks a significant shift from ad-hoc prompting to a more systematic, asset-based method of deploying AI in business settings.

In a detailed write-up, a Claude Code engineer explained that a ‘Skill’ is fundamentally a folder that can include instructions, reference documents, scripts, templates, data, configuration, and hooks. This redefinition moves away from the common misconception that skills are merely saved prompts. Instead, these folders serve as containers for how an organization performs specific tasks, embedding tribal knowledge, guardrails, and tools in a reusable package.

Anthropic’s internal experiments with hundreds of Skills have shown that they improve output consistency, streamline onboarding, and enable continuous improvement. The company identified nine categories of Skills, ranging from library references to infrastructure operations, with verification Skills deemed the most valuable for ensuring output quality. The emphasis is on building Skills that check work, rather than generate it, to catch errors and enforce standards.

At a glance
reportWhen: announced March 2024
The developmentAnthropic published insights from running hundreds of ‘Skills’ internally, redefining skills as folders containing instructions, scripts, and assets instead of prompts.
A Skill Is a Folder, Not a Prompt — Insights
AI Dispatch · Insights · 1 July 2026

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.

✕ The misconception

“A Skill is just a clever markdown prompt you save in a file.”

✓ What it actually is

A folder the agent can discover, read & run — instructions, scripts, references, templates, config & on-demand hooks.

Anatomy of a Skill — the file system is context engineering
my-skill/the unit you share & version
├─ SKILL.mdroot instructions + a description written for the model (its trigger)
├─ references/deep detail pulled in only when needed — progressive disclosure
├─ scripts/real code, so the agent composes instead of rebuilding boilerplate
├─ assets/templates & files to copy into the output
├─ config.jsonsetup the agent asks for if it’s missing (e.g. which Slack channel)
└─ hooks + memoryon-demand guardrails + an append-only log so it remembers
Why it matters: the folder itself is the knowledge base. The agent reads the root, then reaches deeper only when the task demands it — the same way you’d hand a new hire a one-pager that points to the detailed docs.
The nine types — a gap-analysis map for your own library
1Library / API reference
2Product verification ★ top impact
3Data fetching & analysis
4Business-process automation
5Code scaffolding & templates
6Code quality & review
7CI/CD & deployment
8Runbooks
9Infrastructure operations
By Anthropic’s own measurement, verification Skills — the ones that check the work — moved output quality the most. If you build one category well, build that one.
The craft — what separates a good Skill from a useless one
Gotchas = highest-signal section Describe for the model, not humans (it’s the trigger) Don’t state the obvious Ship scripts, not just prose On-demand guardrail hooks (/careful, /freeze) Let it remember (log / SQLite) Don’t railroad — leave room to adapt
The take

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.

Source: “Lessons from building Claude Code: How we use skills,” Thariq Shihipar (Anthropic), Claude blog, 3 June 2026. Categories, examples & measured claims are Anthropic’s; framing is the author’s. Docs: code.claude.com/docs/en/skills.
thorstenmeyerai.com

Implications for Organizational AI Deployment

This approach signifies a move toward institutionalizing AI capabilities, making them durable assets rather than transient prompts. By packaging knowledge into folders, companies can ensure consistent outputs, reduce onboarding time, and develop a growing library of best practices. This method also shifts focus from prompt engineering to building comprehensive, maintainable assets that evolve with organizational needs, potentially transforming how AI is integrated into business operations.

AI Workflow Systems: AI Prompts for Freelance Consultants: Practical AI workflow prompts to automate client work, boost productivity, and scale consulting ... Frameworks for the Modern World Book 1)

AI Workflow Systems: AI Prompts for Freelance Consultants: Practical AI workflow prompts to automate client work, boost productivity, and scale consulting … Frameworks for the Modern World Book 1)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompting to Asset-Based AI Skills

Prior to this development, most organizations relied on ad-hoc prompts, which are often retyped daily and lack durability. Anthropic’s internal experience with hundreds of Skills led to the insight that structuring these as folders containing instructions and tools creates a more reliable, scalable system. The concept aligns with broader trends in AI deployment emphasizing modularity, versioning, and institutional memory, moving beyond simple prompt tuning.

This shift was driven by Anthropic’s need to improve AI output consistency and onboarding efficiency, especially as they scaled their use of AI in engineering and operational tasks. The nine categories of Skills identified serve as a framework for organizations to assess their own capabilities and gaps.

“A Skill is not just a prompt saved as text; it’s a folder that bundles instructions, scripts, and knowledge, making it a reusable asset.”

— Thorsten Meyer, AI researcher

Amazon

AI project organization tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unresolved Questions About Skills Implementation

It remains unclear how widely this folder-based Skills approach has been adopted outside Anthropic or how it performs across different organizational contexts. Details about the scalability, integration challenges, and long-term maintenance of such Skills are still emerging. Additionally, the precise tooling and version control mechanisms for managing these folders are not fully disclosed.

Amazon

AI scripting and instruction folders

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 will likely begin by cataloging their internal procedures into similar folder structures, focusing on verification and automation Skills. Future developments may include standardized tools for creating, managing, and updating Skills across teams, as well as further empirical data on their impact on AI reliability and productivity. Anthropic may also publish more detailed technical guidelines or open-source tools to facilitate adoption.

Amazon

AI asset management system

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does a Skill as a folder improve AI reliability?

By bundling instructions, scripts, and reference materials, a Skill ensures consistent application of knowledge and guardrails, reducing variability and errors in AI outputs.

Can this approach be applied outside of Anthropic?

Potentially, yes. The concept of packaging organizational knowledge into reusable assets can be adapted to other companies, though implementation details and tooling may vary.

What are the main challenges in adopting folder-based Skills?

Challenges include integrating the Skills into existing workflows, managing updates and versioning, and developing tooling for easy creation and maintenance.

Will this change how prompt engineering is done?

Yes. Instead of crafting prompts each time, teams will focus on building and refining Skills as assets, leading to more durable and scalable AI deployment strategies.

Source: ThorstenMeyerAI.com

You May Also Like

Fraunhofer ISE achieves 34.4 efficiency for III-V germanium solar module

Fraunhofer ISE reports a new efficiency record of 34.4% for its III-V germanium solar module, utilizing shingle-matrix technology and space-grade cells.

Podman 6: machine usability improvements (2025)

Podman 6 introduces significant improvements in machine management, including provider-agnostic commands and simplified creation, boosting user experience.

A War Room for Your Next Idea: Inside IdeaClyst

Thorsten Meyer AI describes IdeaClyst as a local-first workspace for testing startup ideas before founders commit months of work.

Nothing’s budget brand CMF won’t be releasing a new phone this year

Nothing’s budget brand CMF won’t release a new phone in 2024 due to rising memory costs, but plans for other products remain unchanged.