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 are not just prompts but folders containing instructions, scripts, and assets. This approach improves consistency, onboarding, and institutional knowledge in AI agent deployment. The development highlights a shift toward durable, reusable organizational assets.

Anthropic has announced that Skills are best understood as folders—containing instructions, scripts, and reference assets—rather than just prompts. This reframing aims to improve the consistency, onboarding, and institutional memory of AI agents used within organizations, based on Anthropic’s internal experience running hundreds of Skills across its engineering teams.

In a detailed write-up, Anthropic’s Claude Code engineer explained that a Skill is a container—an organized folder—holding various components like instructions, reference documents, runnable scripts, templates, data, and configuration files. This structure allows AI agents to discover, read, and execute inside the folder, making the process more durable and reusable than simple prompt-based instructions.

Anthropic’s internal use of Skills revealed a clustering into nine categories, including library references, product verification, data analysis, automation, code scaffolding, review, deployment, runbooks, and infrastructure operations. The company emphasizes that the most valuable Skills are those that verify and check work, as they significantly improve output quality and reduce errors.

Technical lessons from Anthropic highlight that effective Skills should avoid restating obvious information, instead focusing on non-obvious, organization-specific knowledge, and include ‘Gotchas’—traps or pitfalls that the agent must avoid. Descriptions of Skills serve as trigger definitions, matching user requests with the appropriate folder-based Skill for execution.

At a glance
reportWhen: published recently, with ongoing intern…
The developmentAnthropic shared insights from running hundreds of Skills internally, emphasizing their nature as folders rather than prompts, with implications for AI deployment strategies.
Crypto market snapshot
Fear & Greed Index
23/100 — Extreme Fear
Bitcoin BTC$62,657▲ 0.3%
Ethereum ETH$1,763▲ 0.3%
Tether USDT$0.9991▲ 0.0%
BNB BNB$570.42▼ 0.2%
USDC USDC$0.9998▼ 0.0%
XRP XRP$1.13▼ 0.5%
Solana SOL$80.35▼ 3.7%
TRON TRX$0.3247▲ 0.6%
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

Implications for AI Deployment and Organizational Knowledge

This approach to Skills as folders transforms how organizations build, share, and maintain AI capabilities. It shifts the focus from ad-hoc prompting to durable, versioned assets that encode tribal knowledge, improve output consistency, and streamline onboarding. For businesses, this could mean more reliable and scalable AI integration, with a repository of institutional memory that evolves over time. The recognition that Skills are assets rather than prompts suggests a new standard for operational excellence in AI-powered workflows.
Amazon

AI development folder organization tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Internal Use and Broader Industry Impact

Anthropic’s internal experiments with Skills have revealed a structured approach to organizing AI capabilities, which they categorize into nine core types. These range from reference management to operational procedures, with verification Skills identified as the most impactful. Their findings reflect a broader industry challenge: moving beyond simple prompt engineering toward building reusable, maintainable AI assets.

Prior to this, most teams relied on repeated manual prompt crafting, which is inefficient and fragile. Anthropic’s insights suggest that packaging knowledge into Skills can serve as a form of institutional memory, allowing organizations to scale AI deployment without losing consistency or quality. The concept aligns with ongoing industry efforts to create more robust, explainable, and maintainable AI systems.

“Treating Skills as folders containing instructions and assets fundamentally changes how organizations can build durable AI capabilities.”

— Thorsten Meyer, AI researcher

Amazon

AI scripting and automation software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Aspects of Skill Implementation and Adoption

It is not yet clear how widely other organizations will adopt this folder-based approach or how it will scale in different operational contexts. Details about integration with existing systems, version control practices, and the ease of creating and maintaining Skills across diverse teams remain to be seen. Additionally, the long-term impact on AI transparency and explainability is still under discussion.

Amazon

AI reference document management system

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Future Steps Toward Standardizing Skill-Based AI Assets

Anthropic plans to continue refining its Skills framework and share best practices with industry partners. There may be developments in tooling to facilitate easier creation, versioning, and sharing of Skills as folders. Broader adoption could lead to a shift in how organizations structure AI workflows, emphasizing durable, asset-based approaches over ad-hoc prompting.

Amazon

AI agent deployment templates

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 performance?

It allows for more consistent, reusable, and maintainable instructions and assets, reducing errors and onboarding time, and enabling better institutional memory.

Are Skills meant to replace prompts entirely?

No, Skills are a structural enhancement that encapsulate prompts, instructions, and assets into durable containers, making AI deployment more systematic.

Will this approach work for all types of AI tasks?

While promising for operational and repetitive tasks, its effectiveness in highly creative or unpredictable tasks remains to be tested.

What are the main challenges in implementing Skills as folders?

Challenges include establishing version control, creating standardized descriptions, and integrating with existing systems and workflows.

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

OpenEuroLLM. The third path.

OpenEuroLLM, a major pan-European project, faces significant compute challenges in developing multilingual sovereign LLMs, with first models due July 2026.

Private AI prompt workspace for sensitive teams

A new private AI prompt workspace tailored for small, regulated teams begins testing, aiming to enhance data control and security in sensitive workflows.

Vocal-strain load tracking for working singers

A new app prototype aims to monitor vocal strain in professional singers, helping prevent injury during touring schedules through daily voice analysis.

The Local-First Agentic Operator

A new approach demonstrates that one operator, using agentic AI, can build and manage a diverse software portfolio once requiring organizations.