📊 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 organizing AI capabilities into reusable ‘Skills’—folders containing instructions, scripts, and data—improves consistency, onboarding, and scalability. This approach shifts the focus from prompts to institutional assets, offering a new model for AI-driven workflows.

Anthropic has revealed that its internal approach to building AI capabilities involves organizing knowledge and procedures into reusable Skills, which are folders containing instructions, scripts, and reference materials. This shift from prompt-based instructions to containerized assets aims to enhance consistency, onboarding, and iterative improvement across its engineering teams.

According to a detailed write-up from a Claude Code engineer, Skills are not just saved prompts but comprehensive folders that include instructions, reference documents, executable scripts, templates, and configuration data. This design allows AI agents to discover, read, and execute internal procedures, effectively turning ad-hoc prompts into durable institutional assets.

Anthropic’s internal analysis identified nine categories of Skills, ranging from library references and product verification to infrastructure operations. The company emphasizes that high-value Skills, especially those focused on verification, significantly improve output quality by catching mistakes and enforcing standards automatically.

This approach enables organizations to standardize outputs, reduce onboarding time, and build a library of evolving best practices. Anthropic suggests that investing engineering effort into refining Skills can lead to continuous improvement and a more reliable AI deployment process.

At a glance
reportWhen: published March 2024
The developmentAnthropic published a detailed account of how it developed and uses hundreds of Skills to improve AI operations, emphasizing a shift from prompt-based instructions to containerized knowledge assets.
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 of Skills as Organizational Assets

This development matters because it shifts AI operational practices from transient prompts to durable, versioned assets that encapsulate tribal knowledge and guardrails. For businesses, this means more consistent outputs, faster onboarding of new team members, and a scalable way to improve AI performance over time. It also suggests a new paradigm where AI capabilities are managed as institutional assets, not just ad-hoc instructions.

AI Bookkeeping Automation Prompt System: Copy-Paste Prompts, Templates, and AI Workflows to Save Time on Categorization, Reconciliation, and Reporting (AI Systems for Accountants Book 1)

AI Bookkeeping Automation Prompt System: Copy-Paste Prompts, Templates, and AI Workflows to Save Time on Categorization, Reconciliation, and Reporting (AI Systems for Accountants Book 1)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on Prompt Engineering and Organizational Knowledge

Traditional AI deployment relies heavily on prompt engineering—crafting specific instructions for each task. While effective for small-scale or one-off tasks, this approach struggles with consistency and scalability. Recent industry efforts have aimed to automate and standardize AI workflows, but most remain centered on prompts. Anthropic’s approach, as detailed in its recent publication, represents a shift toward modular, reusable components that mirror organizational procedures and knowledge management practices.

This move aligns with broader trends in AI operationalization, where companies seek to embed best practices, guardrails, and institutional memory directly into their AI systems, rather than relying solely on prompt crafting each time a task is performed.

“Transforming instructions into containerized Skills fundamentally changes how organizations can scale and maintain AI capabilities.”

— Thorsten Meyer, AI researcher

Amazon

AI knowledge management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Skills Implementation

It is not yet clear how broadly this Skills framework will be adopted outside Anthropic or how easily organizations can transition from traditional prompt engineering to this container-based approach. Details on integration with existing systems and long-term maintenance of Skills are still emerging.

Amazon

AI scripting and reference folders

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Refinement

Organizations interested in this approach should evaluate their current procedures and identify key areas where Skills can improve consistency and scalability. Future developments may include standardized tools for creating, managing, and updating Skills, as well as industry-wide best practices for implementation.

Amazon

AI development environment tools

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 comprehensive folders containing instructions, scripts, reference materials, and configurations, rather than simple text prompts. They enable AI agents to discover, read, and execute complex procedures, making them more durable and scalable assets.

What benefits do Skills offer over prompt engineering?

Skills improve output consistency, reduce onboarding time, and allow continuous refinement through iterative updates. They turn ad-hoc instructions into institutional assets that can be reused and improved over time.

Can Skills be integrated with existing AI workflows?

While details are still emerging, the framework suggests that Skills can complement or replace prompt-based workflows, especially in environments where standardization and repeatability are critical.

What categories of Skills did Anthropic identify?

Anthropic classified Skills into nine categories, including library references, product verification, data analysis, automation, code scaffolding, review, deployment, runbooks, and infrastructure operations.

Is this approach applicable to other organizations?

Potentially, yes. The core idea of containerizing organizational knowledge and procedures can be adapted to various contexts, but implementation details and benefits may vary depending on scale and existing infrastructure.

Source: ThorstenMeyerAI.com

You May Also Like

Build vs Buy a Prebuilt AI Workstation

Struggling to choose between building or buying an AI workstation? Discover the cost, performance, and control tradeoffs to make the smart move in 2026.

Glasspane: One Dataset, Three Views

Glasspane introduces a new approach to infrastructure transparency, offering role-aware views of one dataset to build demonstrable trust for stakeholders.

The Role of AI in Optimizing Electric Bus Routes

Journey into how AI transforms electric bus routing, unlocking smarter, more efficient transit—discover the innovations that could change transportation forever.

Different Game, or Already Lost? Reading Mistral’s Sovereignty Bet

Analysis of Mistral’s strategic shift from model lab to full-stack provider and its implications for AI sovereignty and competition.