📊 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 ‘Skills’ for AI agents are best understood as folders containing instructions, scripts, and reference materials. This approach improves consistency, onboarding, and scalability in AI workflows. The company ran hundreds of these Skills internally, emphasizing their value as institutional assets.

Anthropic has introduced a new conceptual framework for building AI capabilities, defining Skills as folders containing instructions, scripts, and reference materials rather than simple prompts. This shift aims to make AI agent output more consistent, improve onboarding, and create scalable, durable organizational knowledge assets. The company has tested this approach by running hundreds of Skills across its engineering teams, emphasizing its potential for enterprise AI deployment.

According to a detailed write-up from an Anthropic Claude Code engineer, a Skill is fundamentally a folder that can include instructions, reference documents, scripts, templates, and configuration data. This structure allows AI agents to discover, read, and execute complex workflows, moving beyond the limitations of flat, prompt-based instructions. For businesses, this means transforming ad-hoc prompting into a repeatable, versioned asset that encapsulates tribal knowledge, guardrails, and tools, effectively embedding organizational expertise into AI systems.

Anthropic’s internal testing revealed that organizing Skills into nine categories—such as data fetching, product verification, code scaffolding, and operational runbooks—helps identify gaps and prioritize development. The most impactful Skills, according to Anthropic, are those that verify work quality, as they directly improve output accuracy and reduce mistakes. The company also emphasizes that creating high-quality Skills involves capturing non-obvious, specific knowledge, including ‘gotchas’—traps or pitfalls that could cause errors if overlooked.

Technical lessons highlight that effective Skills should avoid restating obvious facts and instead focus on pushing the model off its defaults through specific instructions and real code snippets. The description of each Skill acts as a trigger for the agent to activate the appropriate workflow, making precise, script-driven instructions essential for success. Anthropic’s approach illustrates how institutional memory can be codified into reusable, versioned assets that evolve and improve over time.

At a glance
reportWhen: published recently, with ongoing applic…
The developmentAnthropic shared insights from running hundreds of ‘Skills’ internally, revealing that they are folders with instructions and tools, not just prompts, which enhances organizational AI capabilities.
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

Transforming AI Organizational Knowledge into Assets

This development matters because it shifts the way organizations build and maintain AI capabilities. Instead of relying on fleeting prompts or manual instructions, companies can create durable, versioned Skills that encapsulate tribal knowledge, guardrails, and automation workflows. This approach enhances consistency, reduces onboarding time, and enables continuous improvement, making AI-driven processes more reliable and scalable. For enterprise AI deployment, adopting Skills as folders can lead to more predictable outcomes and better integration with existing workflows.

Amazon

AI workflow management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Asset Building

Historically, AI teams have relied on prompt engineering—crafting specific instructions for each task. However, this method often results in fragile, ad-hoc setups that require constant re-tuning. Anthropic’s recent work demonstrates a paradigm shift: organizing instructions and tools into structured folders called Skills. This approach is rooted in the recognition that organizational knowledge is best captured as reusable assets rather than ephemeral prompts. The concept builds on prior efforts to improve AI reliability but emphasizes creating a scalable, maintainable library of organizational routines.

Anthropic’s internal experiments involved running hundreds of Skills across various categories, refining them with each edge case and mistake. The company reports that its best Skills started small but improved over time, becoming valuable institutional assets. This process aligns with broader trends in AI deployment, where the focus is shifting from one-off prompts to structured, versioned workflows that can be shared and improved across teams.

“A Skill is not just a prompt; it’s a folder that contains instructions, scripts, and reference materials, enabling AI agents to perform complex, repeatable tasks.”

— Thorsten Meyer, AI researcher

Amazon

AI instruction folder templates

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Impact on Broader Industry Adoption

While Anthropic’s internal results are promising, it is not yet clear how quickly and broadly this approach will be adopted by other organizations. The scalability, maintenance, and integration of Skills across different enterprise environments remain to be tested outside Anthropic’s own context. Additionally, the exact tooling and standards needed for widespread adoption are still evolving, and it is unknown how this will influence future AI development practices.

Amazon

enterprise AI knowledge management tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps in Building and Sharing Skills

Anthropic plans to continue refining its Skills framework, potentially developing standardized tools for creating, versioning, and sharing Skills across teams and organizations. Industry observers anticipate that other AI developers may adopt similar structures, leading to more modular, maintainable AI workflows. Future developments could include integrated development environments for Skills, community-shared libraries, and formal standards for Skill description and management.

Amazon

AI scripting and reference document tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

What exactly is a Skill in Anthropic’s framework?

A Skill is a structured folder containing instructions, scripts, reference documents, templates, and configuration data that enable AI agents to perform complex, repeatable tasks reliably.

How does this approach improve AI deployment in organizations?

It makes AI output more consistent, reduces onboarding time by encapsulating tribal knowledge, and creates reusable, versioned assets that evolve and improve over time.

Is this concept applicable outside of Anthropic?

While originally developed internally, the concept of organizing AI instructions and tools into structured folders could be adopted by other organizations to improve their AI workflows, though standardization is still emerging.

What are the main challenges in implementing Skills at scale?

Challenges include developing tooling for creating, versioning, and sharing Skills, integrating them into existing workflows, and ensuring that Skills remain up-to-date and effective as organizational knowledge evolves.

Source: ThorstenMeyerAI.com

You May Also Like

Forezai · TradingAgents: A Trading Firm Made of Agents

Forezai introduces TradingAgents, an open-source framework of specialized AI agents mimicking trading desk roles to improve decision-making and accountability.

The City That Watches Itself: The Living Digital Twin, And The God’s-Eye View We’re Building

A new development in urban management: cities now create real-time, AI-powered digital twins that monitor and simulate their environments. This raises both efficiency and surveillance concerns.

A Frontier AI Model Just Went Dark For 18 Days. The Kill-Switch Is Real Now.

An advanced AI model was globally switched off for 18 days due to government order, marking a new era of AI control and raising questions about future releases.