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 containing instructions, scripts, and reference materials. This approach enhances consistency, onboarding, and continuous improvement in AI workflows. The company ran hundreds of such Skills internally, emphasizing their value as institutional assets.

Anthropic has announced a new approach to building AI skills, defining them as folders containing instructions, scripts, and reference materials rather than simple prompts. This shift aims to create more durable, reusable, and institutionalized AI capabilities, as demonstrated by their internal deployment of hundreds of such Skills. The development matters because it offers a new model for how organizations can standardize and improve AI-driven workflows.

According to a detailed write-up from a Claude Code engineer, Anthropic’s core innovation is to treat Skills as folders that bundle instructions, reference documents, scripts, templates, and configuration data. This contrasts with the common practice of saving prompts as text snippets. The folder structure allows AI agents to discover, read, and execute the contained assets, making the Skills more than just static prompts.

This approach enhances output consistency, simplifies onboarding by encapsulating tribal knowledge, and enables continuous improvement through iterative refinement. Anthropic has identified nine core categories of Skills, ranging from library references and data analysis to operational runbooks, each serving different organizational needs. The most valued are those that verify and check work, which significantly improve output quality.

Anthropic’s internal experiments show that investing engineer time into perfecting a Skill can lead to a compounding asset that evolves and sharpens over time. The company emphasizes that Skills are not cost centers but valuable, appreciating assets that codify how work gets done in an organization.

At a glance
reportWhen: published recently, based on internal A…
The developmentAnthropic published insights on transforming AI skills from simple prompts into reusable, folder-based assets after running hundreds of them across its engineering teams.
Crypto market snapshot
Fear & Greed Index
23/100 — Extreme Fear
Bitcoin BTC$62,682▲ 0.4%
Ethereum ETH$1,764▲ 0.5%
Tether USDT$0.9992▲ 0.0%
BNB BNB$571.04▼ 0.0%
USDC USDC$0.9998▼ 0.0%
XRP XRP$1.14▼ 0.3%
Solana SOL$80.4▼ 3.5%
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

Transforming AI Skills into Organizational Assets

This development signifies a shift in how businesses can structure AI capabilities for reliability and scalability. By treating Skills as folders with bundled instructions and tools, organizations can standardize processes, reduce onboarding time, and create a living library that improves with use. This approach can lead to more predictable AI outputs and safer operational procedures, especially in complex or sensitive workflows.

For companies deploying AI at scale, this methodology offers a blueprint for turning ad-hoc prompts into durable, versioned assets that embed tribal knowledge, guardrails, and best practices. It also underscores the importance of continuous refinement, turning Skills into appreciating assets that grow more effective over time.

AI Workflow Systems: AI Prompts for Freelance Consultants: Practical AI workflow prompts to automate client work, boost productivity, and scale consulting ... Frameworks for the Modern World Book 1)

AI Workflow Systems: AI Prompts for Freelance Consultants: Practical AI workflow prompts to automate client work, boost productivity, and scale consulting … Frameworks for the Modern World Book 1)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Institutionalized Capabilities

Prior to this development, most organizations relied on prompt engineering—crafting specific prompts for each task, often retyped daily or modified for each use case. Anthropic’s move to package knowledge into folder-based Skills represents a fundamental rethinking. This approach aligns with broader trends in AI deployment, where repeatability, consistency, and institutional memory are increasingly valued.

Anthropic’s internal documentation highlights that their best Skills have evolved from simple, hard-won snippets to complex, multi-layered containers that improve through iterative use. This reflects a maturation of AI workflows from ad-hoc prompt tuning toward systematic, reusable, and version-controlled assets.

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

— Thorsten Meyer, AI researcher

Machine Learning: 4 Books in 1: Basic Concepts + Artificial Intelligence + Python Programming + Python Machine Learning. A Comprehensive Guide to Build Intelligent Systems Using Python Libraries

Machine Learning: 4 Books in 1: Basic Concepts + Artificial Intelligence + Python Programming + Python Machine Learning. A Comprehensive Guide to Build Intelligent Systems Using Python Libraries

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Aspects of Implementation and Adoption

It is not yet clear how widely this folder-based Skills approach will be adopted outside Anthropic or how it will scale in different organizational contexts. Details about the specific technical challenges, integration with existing systems, or how organizations will manage versioning and updates remain limited. Additionally, the long-term effectiveness and maintenance costs of such Skills are still to be evaluated.

Agentic AI Playbook: A Practical Guide to Design, Build and Scale AI Agents

Agentic AI Playbook: A Practical Guide to Design, Build and Scale AI Agents

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Standardization

Organizations interested in this approach should begin cataloging their internal knowledge as Skills, focusing on creating reusable, versioned folders. Monitoring how these Skills evolve and improve over time will be critical. Industry-wide, we may see the emergence of standards or tools to facilitate Skills management, similar to software repositories, to support broader adoption.

Further research and case studies are expected to clarify best practices, technical challenges, and the impact of this methodology on AI reliability and organizational efficiency.

Key Education Publishing Social Skills File Folder Game 9.5" x 2.88"

Key Education Publishing Social Skills File Folder Game 9.5" x 2.88"

Ideal for social problem solving

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 reference materials, making it a reusable and versioned asset. A prompt is typically a single input string used temporarily for a specific task.

Why does treating Skills as folders matter?

It enables organizations to standardize workflows, improve consistency, and build institutional knowledge that evolves over time, rather than relying on ad-hoc prompts.

Can this approach improve AI safety and reliability?

Yes, by encapsulating guardrails, checks, and reference data within Skills, organizations can better control AI outputs and reduce errors.

What are the main challenges in implementing folder-based Skills?

Managing version control, updating assets, and integrating with existing AI systems are potential technical hurdles. Organizational discipline in maintaining these repositories is also necessary.

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

UAE Mining Giant’s Strategic US Market Entry Reshapes Industry

Learn how the UAE’s Phoenix Group is reshaping the U.S. mining industry and what this means for the future of technology and sustainability.

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

An analysis of Mistral’s shift to full-stack AI, its on-prem focus for Europe, and the debate over its technical and strategic positioning amid industry giants.

The mandate. Why the US conversational- finance surface does not translate to Europe.

The US launches permissionless finance surfaces, while Europe relies on mandated, licensed frameworks. This shapes market structure and entry barriers.