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 learned that organizing AI Skills as folders rather than prompts enhances consistency, onboarding, and continuous improvement. This approach turns ad-hoc prompts into durable institutional tools, impacting AI deployment strategies.

Anthropic has revealed that its approach to building AI capabilities involves organizing ‘Skills’ as folders containing instructions, scripts, and reference materials, rather than simple prompts. This shift aims to make AI outputs more consistent, facilitate onboarding, and create a durable knowledge base, marking a significant advance in enterprise AI deployment.

According to a detailed write-up from a Claude Code engineer, Anthropic’s ‘Skills’ are not just saved prompts but structured folders that include instructions, reference documents, runnable scripts, templates, data, and configuration. This design allows AI agents to discover, read, and execute the contents of these folders, effectively turning them into reusable assets that encode organizational knowledge and procedures.

Anthropic emphasizes that this approach transforms ad-hoc prompting into a standardized, institutional capability. Skills help ensure output consistency across team members, streamline onboarding by encapsulating tribal knowledge, and improve over time as they are refined through real-world edge cases. The company reports dedicating significant engineering effort—up to a week—to perfect a single Skill, viewing these as assets that appreciate in value.

Furthermore, Anthropic identified nine core categories of Skills, ranging from API references and product verification to infrastructure operations, each critical for automating and verifying various business processes. Among these, verification Skills—those that check the output—are considered most impactful, as they directly improve quality and reduce errors.

At a glance
reportWhen: published recently, based on internal A…
The developmentAnthropic published a detailed report on how its team developed and uses ‘Skills’—structured folders containing instructions and assets—to improve AI performance and organizational knowledge.
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 Development with Structured Skills

This development signals a shift from ephemeral prompts to durable, reusable organizational assets, potentially redefining AI deployment in enterprise settings. By framing Skills as folders that encapsulate knowledge, Anthropic demonstrates a scalable method for maintaining consistency, reducing onboarding time, and continuously improving AI performance. This approach could influence how companies design their AI workflows, moving toward more systematic and maintainable practices that embed tribal knowledge into operational routines.

AI for Small Business Made Simple: A Step-by-Step Guide to Using AI Tools Without Any Tech Skills

AI for Small Business Made Simple: A Step-by-Step Guide to Using AI Tools Without Any Tech Skills

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Asset Building

Until now, most AI teams relied on manually crafted prompts that needed frequent re-creation, often leading to inconsistent outputs and onboarding challenges. Anthropic’s internal experiments and documentation show a deliberate move away from these ad-hoc prompts toward structured Skills—organized containers of instructions and assets—that serve as institutional memory. This approach aligns with broader trends in enterprise AI, emphasizing maintainability and knowledge reuse.

Anthropic’s insights build on existing practices but formalize them into a scalable system, with the company investing significant effort into cataloging and refining Skills across nine categories. This methodology reflects a maturation in AI deployment, emphasizing repeatability and continuous improvement rather than one-off prompt tuning.

“A Skill is not just a prompt saved in a file; it’s a folder with instructions, scripts, and references that the agent can discover and execute.”

— Thorsten Meyer, AI researcher at Anthropic

Create a Podcast with AI (No Experience Needed) : A Step-by-Step Guide to Planning, Scripting, Recording, Editing, and Launching a Podcast Using ChatGPT, AI Tools, and Automation

Create a Podcast with AI (No Experience Needed) : A Step-by-Step Guide to Planning, Scripting, Recording, Editing, and Launching a Podcast Using ChatGPT, AI Tools, and Automation

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Uncertainties Around Skill Implementation and Adoption

While Anthropic’s internal documentation and engineer insights outline the concept of Skills as folders, it is not yet clear how widely this approach has been adopted outside of their organization or how it compares in effectiveness to traditional prompt engineering at scale. Details about how organizations can transition to this model or integrate it into existing workflows remain under development.

Growing a Healthy Knowledge Base: The Forward-Looking Approach to Technical Documentation: Engineering Manager’s Handbook

Growing a Healthy Knowledge Base: The Forward-Looking Approach to Technical Documentation: Engineering Manager’s Handbook

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Future Adoption and Industry Impact of Folder-Based Skills

Next steps include broader testing of this approach across different teams and industries, as well as developing tools to streamline the creation and management of Skills. Industry observers will watch for how this model influences enterprise AI deployment, whether it becomes a standard practice, and how it impacts the economics of AI development and maintenance.

Luminar Neo User Guide 2026: Step-by-Step Instructions to Transform Your Pictures Using Simple AI Tools: The Jargon-Free Handbook for Non-Tech-Savvy Creators (Jargon-Free Manuals)

Luminar Neo User Guide 2026: Step-by-Step Instructions to Transform Your Pictures Using Simple AI Tools: The Jargon-Free Handbook for Non-Tech-Savvy Creators (Jargon-Free Manuals)

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 assets, whereas prompts are typically just text snippets. Skills enable reusable, organized, and more reliable AI behaviors.

Why does organizing Skills as folders matter for businesses?

This approach helps ensure consistent outputs, simplifies onboarding, and allows continuous improvement of AI capabilities by treating Skills as evolving assets.

Can this approach be applied outside of Anthropic?

While Anthropic’s internal documentation suggests broad applicability, it remains to be seen how widely adopted this model will be across different organizations and AI systems.

What are the main categories of Skills identified?

Anthropic identified nine categories, including API references, product verification, data analysis, automation, code scaffolding, review, deployment, runbooks, and infrastructure operations.

What remains uncertain about this approach?

It is still unclear how scalable and adaptable this folder-based model is in diverse organizational contexts and whether it will replace prompt engineering practices industry-wide.

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

Voice Assistant Usage Has Reached 60% Among Consumers, a Study Shows

Unlock the secrets behind the 60% surge in voice assistant usage among consumers and discover what this trend means for our technological future.

The Silent Sync: How Block‑Pruning Saves Terabytes for Node Runners

A explores how block-pruning reduces storage requirements for node runners, enabling efficient, secure blockchain validation—discover the secrets behind this silent sync.

What Is Onchain

Blockchain technology relies on on-chain processes for secure transactions, but scalability issues pose intriguing challenges that warrant deeper exploration.

What Is Crypto Ledger

Many are curious about crypto ledgers; discover how they ensure secure, transparent transactions that could change your understanding of digital finance forever.