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 shifted from viewing AI Skills as prompts to treating them as folders—comprehensive containers for instructions, code, and knowledge—aiming to improve consistency, onboarding, and organizational learning. This approach emphasizes building reusable, versioned assets over ad-hoc prompting.

Anthropic has announced a new approach to developing AI Skills, defining them as folders that contain instructions, code, reference documents, and configurations—rather than mere prompts. This shift aims to create durable, reusable organizational assets that improve the consistency and efficiency of AI deployment across teams, marking a significant change in how AI capabilities are structured and maintained.

In a detailed write-up from a Claude Code engineer, Anthropic explained that its internal practice involves packaging knowledge into Skills as folders, not prompts. Each folder can include instructions, scripts, templates, data, and hooks that activate during use, enabling agents to discover and execute complex workflows. This conceptual reframe moves away from the idea of saving prompts as text snippets, instead emphasizing structured containers that reflect actual business processes.

Anthropic identified nine core categories of Skills, ranging from library and API reference to infrastructure operations. The most impactful are those for verification—ensuring output quality—and business-process automation. The company reports that its best Skills started small but improved iteratively as they captured edge cases and institutional knowledge, turning Skills into assets that appreciate in value over time.

This methodology aims to standardize outputs, streamline onboarding, and build a knowledge base that evolves. Anthropic advocates dedicating engineer time to perfecting a single Skill category, viewing these as investments that compound in organizational value.

At a glance
reportWhen: published March 2024
The developmentAnthropic published insights from running hundreds of Skills internally, redefining Skills as folders containing instructions, scripts, and assets rather than simple prompts.
Crypto market snapshot
Fear & Greed Index
23/100 — Extreme Fear
Bitcoin BTC$62,727▲ 0.7%
Ethereum ETH$1,762▲ 0.6%
Tether USDT$0.9991▲ 0.0%
BNB BNB$571.31▲ 0.4%
USDC USDC$0.9998▼ 0.0%
XRP XRP$1.14▼ 0.4%
Solana SOL$80.4▼ 3.1%
TRON TRX$0.3246▲ 0.5%
Live data · CoinGecko · alternative.me (24h change)
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 Capabilities into Organizational Assets

This approach matters because it shifts AI development from ad-hoc prompt engineering to structured, maintainable assets that embed tribal knowledge and guardrails. Treating Skills as folders enhances consistency, reduces onboarding time, and creates a scalable way to improve AI behavior over time. For organizations relying on AI, this could lead to more reliable, transparent, and efficient deployment, especially in complex operational environments.

AI Product Management Handbook: How to Pivot Your Career into High-Paying AI Product Roles Without a Computer Science Degree

AI Product Management Handbook: How to Pivot Your Career into High-Paying AI Product Roles Without a Computer Science Degree

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompting to Structured Asset Management

Historically, many teams have relied on prompt engineering—crafting specific instructions for each task—to control AI outputs. Anthropic’s internal experience, shared publicly in March 2024, reveals a shift toward building reusable, versioned containers of knowledge called Skills. The company’s internal experiments show that Skills, when properly constructed, can serve as durable assets that evolve and improve, contrasting with the ephemeral nature of prompts.

This development builds on broader trends in AI deployment, emphasizing reliability, repeatability, and institutional memory, moving beyond simple prompt tuning to more sophisticated organizational practices.

“A Skill is not a prompt saved in a text file. It’s a folder—containing instructions, scripts, and reference documents—that the agent can discover and execute.”

— Thorsten Meyer, AI engineer at Anthropic

AI Real Estate Playbook: How to Reclaim Your Time, Multiply Your Income, and Clone Yourself

AI Real Estate Playbook: How to Reclaim Your Time, Multiply Your Income, and Clone Yourself

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Aspects of Implementation and Adoption

It remains uncertain how widely this approach will be adopted outside Anthropic or how easily other organizations can implement similar folder-based Skills systems. Details about the tooling, integration with existing workflows, and scalability across different industries are still emerging. Additionally, the long-term impact on AI performance and maintenance costs has not yet been fully evaluated.

Amazon

AI knowledge base software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Validation

Organizations interested in this approach should assess their current Knowledge Management practices and consider developing prototype Skills as folders. Future developments may include standardized tools for creating, versioning, and sharing Skills across teams. Anthropic is likely to continue refining its methodology and share best practices to encourage wider industry adoption.

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.

Key Questions

How does treating Skills as folders improve AI consistency?

Folders can contain comprehensive instructions, scripts, and configurations, enabling AI agents to follow standardized workflows and guardrails, leading to more predictable outputs.

Can this approach be applied outside of Anthropic?

Potentially, yes. However, implementation requires a structured knowledge management system and discipline in creating and maintaining Skills as reusable assets. Adoption may vary based on organizational resources and technical maturity.

What are the main benefits of this folder-based Skills system?

It enhances output consistency, reduces onboarding time, captures institutional knowledge, and allows Skills to improve iteratively, turning them into valuable organizational assets.

What challenges might organizations face in adopting this model?

Challenges include developing the tooling for managing Skills as folders, integrating with existing workflows, and maintaining the quality and relevance of Skills over time.

Will this change how AI models are trained or just how they are used?

This approach primarily affects how AI is used and maintained, not the core training of models. It emphasizes building structured, reusable assets for deployment and operational consistency.

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

How High Refresh Rate Screens Change the Trading Desk Experience

Inevitable improvements in trading efficiency await as high refresh rate screens revolutionize your desk, but discovering their full impact requires deeper exploration.

The $9 Billion Signature Tax: How DocuSign’s Business Model Survives on One Assumption

A new open source project, DocuSeal, challenges DocuSign’s dominance with a self-hosted, cost-effective solution. Here’s what’s confirmed and what’s still uncertain.

DDR5 Now, DDR6 Soon: A Buyer’s Field Guide

Learn why buying DDR5 now is recommended over waiting for DDR6, which is still in development and costly. Understand the best options for 2026-2028.

How NAS Storage Helps Crypto Teams Protect Their Content Archives

Boost your crypto team’s data security with NAS storage—discover how its features can keep your content safe and what you need to know next.