📊 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 are best understood as folders, not prompts, enabling organizations to build reusable, maintainable AI capabilities. This approach improves consistency, onboarding, and institutional knowledge.

Anthropic has revealed a new approach to building AI capabilities: defining Skills as folders that contain instructions, scripts, data, and configurations, instead of just saved prompts. This shift aims to make AI agent behaviors more durable, consistent, and shareable across organizations, marking a significant development in enterprise AI deployment.

In a detailed write-up from a Claude Code engineer, Anthropic explained that Skills are not merely text prompts but containers that include instructions, reference documents, executable scripts, and hooks that activate during specific tasks. This redefinition enables organizations to package their operational knowledge into reusable units, transforming ad-hoc prompting into institutional assets.

Anthropic’s internal experience shows that running hundreds of Skills across their engineering teams improved output consistency, simplified onboarding, and facilitated continuous improvement. These Skills cluster into nine categories, covering everything from API references to infrastructure operations, with verification Skills identified as the highest value for quality control.

At a glance
reportWhen: announced March 2024
The developmentAnthropic shared insights from running hundreds of Skills internally, emphasizing their nature as comprehensive folders rather than simple 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

How Skills as Folders Reshape AI Organizational Practices

This development matters because it shifts the focus from ephemeral prompts to durable, versioned assets that encode tribal knowledge and guardrails. For companies, this approach enhances operational consistency, accelerates onboarding, and creates a foundation for continuous improvement, making AI deployment more reliable and scalable.

Amazon

AI skills management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Asset Building in Enterprise AI

Prior to this insight, most teams relied on manually crafting prompts that were often discarded after use. Anthropic’s internal experiments with hundreds of Skills demonstrated that packaging knowledge into structured folders leads to more maintainable and scalable AI systems. This aligns with broader trends in enterprise AI, where robustness and repeatability are critical.

The concept builds on existing practices but emphasizes a shift towards modular, reusable units that encapsulate organizational expertise and operational procedures, akin to software libraries or runbooks.

“A Skill is a folder, not just a prompt. It contains instructions, scripts, and knowledge that make AI behaviors durable and shareable.”

— Thorsten Meyer, AI engineer at Anthropic

Amazon

enterprise AI knowledge base tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unresolved Questions About Skills Implementation and Adoption

It is still unclear how widely this approach will be adopted outside Anthropic or how organizations will integrate Skills into existing workflows. Details about tooling, standards, and the ease of creating and maintaining Skills at scale remain to be seen. Additionally, the long-term impact on AI transparency and control is yet to be evaluated.

Amazon

AI scripting and instruction containers

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Organizations Implementing Skills Frameworks

Organizations interested in this approach should begin cataloging their operational knowledge into structured folders, focusing on high-value categories like verification and automation. Future developments may include standardized tools for creating, sharing, and updating Skills, as well as metrics to evaluate their effectiveness in real-world applications.

Amazon

AI automation and workflow tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How is a Skill different from a prompt?

A Skill is a folder containing instructions, scripts, and knowledge, whereas a prompt is a simple text instruction. Skills are reusable assets that encode organizational procedures and guardrails.

What benefits does packaging knowledge into folders provide?

It improves consistency, accelerates onboarding, and creates a durable record of operational procedures that can evolve over time, making AI systems more reliable and scalable.

Can this approach be applied outside of AI development teams?

Yes, the concept of bundling procedural knowledge into structured assets can benefit various organizational functions that rely on automation and process consistency.

What challenges might organizations face adopting this method?

Developing standards for Skill creation, maintaining version control, and integrating Skills into existing workflows could pose initial hurdles.

Will Skills replace traditional prompting entirely?

Not necessarily; Skills aim to complement prompts by providing structured, reusable assets that enhance robustness and repeatability.

Source: ThorstenMeyerAI.com

You May Also Like

Anchor. The Schwarz Group model.

Schwarz Group’s €11B investment in a data center campus exemplifies a scalable industrial-anchor AI model in Europe. Its replication is structurally limited.

Postgres Transactions Are A Distributed Systems Superpower

New developments show Postgres transactions as a powerful tool for distributed systems, enhancing reliability and consistency in complex environments.

Fair-value appraisals for used GPUs and AI hardware

A new manual valuation method is being tested to establish fair market prices for used AI hardware, helping brokers resolve pricing disputes.

Raw-feed licensing. The contract that doesn’t exist yet.

The industry lacks a standard contract for raw-feed licensing for downstream AI rewriting, creating a significant legal and economic gap.