A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them
AIThis post was created with the assistance of artificial intelligence (AI).

📊 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.

Before you orderOffer from Amazon

Get the latest gadgets delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Anthropic has shifted from using prompts to a folder-based ‘Skills’ system, enhancing AI consistency, onboarding, and institutional knowledge. This approach treats Skills as containers for operational assets, not just prompts.

Anthropic has announced a significant shift in how it develops and deploys AI capabilities, moving away from prompt-based instructions toward a system where Skills are structured as folders containing instructions, scripts, and reference materials. This approach aims to create more consistent, reusable, and maintainable organizational assets for AI agents, according to a detailed internal write-up from a Claude Code engineer.

The core innovation is defining a Skill as a folder—not a prompt—containing a variety of resources such as instructions, code, templates, and configuration. This structure allows AI agents to discover, read, and execute complex workflows, encapsulating tribal knowledge and operational guardrails in a single, versioned container.

Anthropic’s internal experience shows that this method improves output consistency across teams, accelerates onboarding by replacing tribal knowledge with accessible assets, and allows Skills to evolve and improve over time as they are refined through real-world use. The company emphasizes that investing in refining Skills—sometimes a full engineer-week per category—yields high returns, as Skills become valuable institutional assets that grow sharper with use.

At a glance
reportWhen: published March 2024
The developmentAnthropic published insights from running hundreds of Skills internally, demonstrating a new organizational method for AI capabilities that emphasizes reusable, containerized units over 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

Implications for AI Development and Organizational Knowledge

This approach transforms AI development from ad-hoc prompt engineering into a systematic, asset-based process that enhances operational reliability, reduces onboarding time, and captures institutional knowledge. For organizations, this means more predictable AI behavior and a scalable way to embed tribal knowledge into AI workflows, potentially setting a new standard in enterprise AI deployment.

Amazon

AI development skills management tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompting to Containerized Skills: Evolving AI Practices

Until now, most teams relied on prompt engineering—crafting specific instructions for each task—to guide AI behavior. Anthropic’s internal experiments, detailed in their recent publication, challenge this paradigm by demonstrating that organizing capabilities into reusable, containerized Skills offers significant advantages. This shift aligns with broader trends toward modular, maintainable AI systems and reflects lessons learned from running hundreds of Skills internally, which are grouped into nine categories such as data analysis, verification, and infrastructure operations.

“Treating Skills as folders containing instructions, scripts, and data fundamentally changes how organizations can build reliable AI systems.”

— Thorsten Meyer, AI researcher

Amazon

AI workflow automation software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Skills Implementation

It is not yet clear how widely adopted this approach will become outside Anthropic, or how it compares in efficiency and cost to traditional prompt engineering across different organizations. Details on how Skills are maintained, updated, and scaled in large enterprise settings remain to be seen, and the precise impact on AI output quality over time is still under evaluation.

Amazon

AI instruction and script organization tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Validation

Anthropic plans to continue refining its Skills library and sharing best practices. Other organizations may experiment with containerized Skills, and further studies will evaluate their impact on AI reliability, onboarding, and operational efficiency. Monitoring how this approach scales and integrates into existing workflows will be key in the coming months.

Amazon

version-controlled AI asset containers

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 data, acting as a reusable and versioned container for operational knowledge, whereas a prompt is a single instruction or question guiding the AI temporarily.

What benefits does the Skills system offer?

Skills improve consistency, accelerate onboarding, and allow continuous refinement, making AI capabilities more reliable and aligned with organizational processes.

Will this approach work for all AI tasks?

While promising for operational and repetitive tasks, the effectiveness of containerized Skills for creative or highly variable tasks remains to be fully tested.

How does this impact AI maintenance and updates?

Skills can be versioned and refined over time, enabling systematic updates that improve performance and reduce the risk of errors compared to prompt re-engineering.

Source: ThorstenMeyerAI.com

HALLOWEEN

Halloween Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

The Defender’s Counter-Cascade.

Google discloses real-world AI exploit; deployment gap in AI-driven security remains critical, impacting global cybersecurity resilience.

How This AI Firm Beat Western Giants In Leadership And Management

A Chinese AI firm, Moonshot’s Kimi K3, beat top Western models in managing a real company during a live competition, highlighting new leadership potential.

PC gamers can get one of 2026’s best roguelikes completely free of charge from Epic for a limited

PC gamers can now get one of 2026’s best roguelikes for free from Epic Games, available for a limited time. Details on the game and how to claim it inside.

Daily Photographic Monitoring To Prevent Gaps And Maintain Oral Health

A new approach tests daily gum-line photo scoring to detect early inflammation, aiming to enhance preventive dental care between visits.