A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them

📊 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 better understood as folders containing instructions, scripts, and assets rather than simple prompts. This approach enhances consistency, onboarding, and institutional knowledge. The company ran hundreds of such Skills internally, emphasizing their value as reusable, evolving assets.

Anthropic has revealed that its approach to building AI agents involves creating ‘Skills’ as structured folders containing instructions, scripts, and reference materials, rather than simple prompts. This shift aims to improve consistency, onboarding, and institutional knowledge within organizations deploying AI. The company’s internal experiments with hundreds of Skills demonstrate how this method can turn ad-hoc prompting into durable, shareable operational assets.

According to a detailed write-up from a Claude Code engineer, Anthropic’s ‘Skills’ are defined as folders that include instructions, reference documents, runnable scripts, templates, and configuration data. Unlike prompts, which are often seen as ephemeral text snippets, Skills serve as comprehensive containers that organizations can discover, read, and execute. This design allows AI agents to perform tasks with greater consistency, as each Skill encapsulates the knowledge and procedures needed for specific workflows.

Anthropic’s internal analysis identified nine categories of Skills, ranging from library references and product verification to automation and infrastructure operations. The company emphasizes that the most valuable Skills are those that verify work quality, as they directly reduce errors and improve output. The process of building Skills involves capturing non-obvious, specific knowledge—like ‘gotchas’—that prevent common mistakes, effectively creating institutional memory.

Technical lessons include avoiding restating obvious information, focusing on non-default, non-generic content, and writing precise, trigger-based descriptions that activate the correct Skills. Bundling real code, helper functions, and environment-specific instructions into Skills is seen as a way to encode organizational practices into reusable, sharable assets.

At a glance
reportWhen: published March 2024
The developmentAnthropic published a detailed account of how it has developed and used hundreds of Skills structured as folders to improve AI agent performance and organizational knowledge management.
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 Workflows with Folder-Based Skills

This approach shifts how organizations deploy and maintain AI agents, moving from ad-hoc prompts to structured, versioned assets that encapsulate institutional knowledge. It enhances operational consistency, reduces onboarding time, and creates a scalable library of reusable procedures. For businesses, this means AI can become a more reliable and integral part of daily workflows, with clear documentation and guardrails embedded within Skills.

By emphasizing Skills as containers, Anthropic’s method addresses core challenges of AI deployment—such as variability in output and difficulty in scaling knowledge transfer—potentially setting a new standard for enterprise AI practices.

Amazon

AI development folder organization tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompts to Structured Organizational Assets

Most teams using AI coding agents currently rely on repeating instructions or prompts, which are often ephemeral and difficult to maintain. Anthropic’s internal experiments with hundreds of Skills demonstrate a different paradigm: packaging knowledge into folders that serve as durable, sharable assets. This approach aligns with broader trends in enterprise AI, where consistency, documentation, and version control are critical.

Historically, AI prompts have been treated as quick fixes or one-off instructions. Anthropic’s insight is that organizing instructions, scripts, and reference data into structured folders creates a more robust foundation for automation and operational procedures. This method also facilitates capturing tribal knowledge, which can otherwise be lost as personnel change.

While the concept of Skills as folders is rooted in technical design, its implications for business processes are significant. It enables organizations to build a library of repeatable, reliable procedures that evolve over time, improving quality and reducing manual oversight.

“A Skill is not just a prompt; it’s a folder—a container that includes instructions, scripts, and reference materials, making it a durable organizational asset.”

— Thorsten Meyer, AI engineer at Anthropic

Amazon

AI scripting and reference document software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Aspects of Skill Implementation and Scaling

It remains unclear how broadly this folder-based Skills approach will be adopted outside Anthropic or how easily organizations can transition from traditional prompt engineering to this model. Details about the specific tooling, integration with existing workflows, and the scalability of managing large Skills libraries are still emerging. Additionally, the long-term maintenance and updating processes for Skills are not fully defined.

AI Automation Made Simple

AI Automation Made Simple

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Enterprise Adoption and Development

Organizations interested in this approach should evaluate their current knowledge management and automation procedures, considering how to structure instructions and scripts as reusable folders. Anthropic is likely to release more detailed tooling and best practices, facilitating broader adoption. Future developments may include integrated management systems for Skills, version control, and automated testing to ensure ongoing reliability.

Amazon

AI knowledge management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How do Skills differ from traditional prompts?

Skills are structured folders containing instructions, scripts, and reference data, making them durable, reusable assets. Prompts are typically short, ephemeral text snippets.

What benefits do folder-based Skills offer?

They improve consistency, facilitate onboarding, capture institutional knowledge, and support scalable automation of organizational workflows.

Can this approach be applied outside AI development teams?

Yes, any organization using AI for automation or decision-making can benefit from structured, reusable Skills as organizational assets.

What are the main challenges in adopting this model?

Challenges include developing tooling for managing Skills, integrating with existing systems, and maintaining the library as procedures evolve.

Source: ThorstenMeyerAI.com

Nothing in this article is financial or investment advice. Cryptocurrency and precious-metal investments carry significant risk — do your own research and consider a licensed advisor.
You May Also Like

Data: The One Thing You Can’t Rent

In 2026, data scarcity and fencing have shifted AI’s competitive edge from compute to proprietary, verified human-made data, reshaping industry dynamics.

The Bubble Question, Disentangled: 1999 vs 2026 Category by Category

A detailed analysis compares the AI investment cycle of 2026 with the 1999 dotcom bubble, highlighting categories of bubble risk and real value.

The Forecast Is the Plan.

Major AI labs publicly commit to automating AI R&D by 2026, signaling a shift from research goals to execution plans with significant implications for the industry.

DojoClaw: The Engine Behind the Fleet

DojoClaw, an AI-driven content factory, now supports more than 450 magazine-style sites by producing scalable, cost-effective pages across a large digital portfolio.