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 organizing AI capabilities into ‘Skills’ as folders—containing instructions, scripts, and assets—improves consistency, onboarding, and institutional knowledge. This approach shifts AI from ad-hoc prompts to durable, reusable organizational assets.

Anthropic has announced a new approach to managing AI capabilities by defining Skills as folders that contain instructions, scripts, and reference materials, rather than simple prompts. This shift aims to make AI operations more consistent, scalable, and easier to onboard, marking a significant change in enterprise AI deployment.

The company’s internal documentation describes Skills as containers that bundle knowledge, code, and configuration, enabling AI agents to discover, read, and execute complex workflows. This redefinition moves away from viewing Skills as mere text prompts, instead framing them as comprehensive assets that encapsulate organizational procedures and tribal knowledge.

Anthropic’s engineering team has applied this concept across its own organization, creating hundreds of Skills that address various functions such as data analysis, verification, automation, and infrastructure management. The company reports that this approach enhances output consistency, reduces onboarding time, and allows Skills to improve iteratively through accumulated experience.

One key insight from Anthropic’s experience is that Skills should include not just instructions but also reference documents, scripts, and hooks that activate during specific tasks, making them more versatile and reliable. The company emphasizes that building high-quality Skills requires capturing non-obvious, specific knowledge—what they call ‘Gotchas’—that prevent errors and ensure accuracy.

At a glance
reportWhen: published recently, with ongoing implem…
The developmentAnthropic shared insights from running hundreds of ‘Skills’ internally, redefining how AI agents are structured for enterprise use.
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 Management Through Structured Skills

This development indicates a shift from ad-hoc prompt engineering to systematic, reusable organizational assets. By treating Skills as folders containing comprehensive workflows, companies can achieve greater consistency, reduce onboarding efforts, and build a durable institutional memory. This approach could redefine enterprise AI deployment, making it more scalable, reliable, and aligned with business processes, ultimately improving operational efficiency and AI trustworthiness.
AI Workflow Automation for Bloggers: Build a Simple Content System to Research, Write, Optimize, and Repurpose Posts Faster with AI and No-Code Tools (AI Toolkit for Bloggers 2026 Book 8)

AI Workflow Automation for Bloggers: Build a Simple Content System to Research, Write, Optimize, and Repurpose Posts Faster with AI and No-Code Tools (AI Toolkit for Bloggers 2026 Book 8)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Folder-Based Skills

Traditionally, AI teams have relied on prompts—short, often ad-hoc instructions—to guide model outputs. This method is fragile, inconsistent, and difficult to scale across organizations. Anthropic’s recent publication reflects a broader trend toward formalizing AI capabilities into reusable assets. Their internal experience with hundreds of Skills demonstrates that organizing knowledge into folders with instructions, scripts, and hooks leads to more predictable and maintainable AI behavior. The concept aligns with ongoing efforts in the AI community to embed tribal knowledge and operational procedures directly into AI systems, moving beyond simple prompt tuning.

“A Skill is not just a prompt; it’s a folder that contains instructions, reference documents, scripts, and hooks—everything needed to perform a task reliably.”

— Thorsten Meyer, AI researcher at Anthropic

Building AI-Powered Products: The Essential Guide to AI and GenAI Product Management

Building AI-Powered Products: The Essential Guide to AI and GenAI Product Management

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear How Skills Will Scale Outside Anthropic

It is not yet clear how easily this folder-based Skills approach can be adopted by other organizations or integrated into existing AI workflows. The long-term effectiveness and scalability of this method across diverse enterprise environments remain to be seen.
Amazon

AI scripting and instruction management tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps in Formalizing and Sharing Skills

Organizations are expected to experiment with adopting Skills as structured assets, developing best practices for their design and maintenance. Anthropic may release tools or frameworks to facilitate this process, and further industry adoption could follow. Monitoring how Skills evolve and improve over time will be crucial to understanding their full impact on enterprise AI operations.

AI and UX: Why Artificial Intelligence Needs User Experience

AI and UX: Why Artificial Intelligence Needs User Experience

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

What exactly is a Skill in Anthropic’s approach?

A Skill is a folder containing instructions, reference documents, scripts, configuration, and hooks that enable an AI agent to perform a specific task reliably and consistently.

How does this differ from traditional prompt engineering?

Traditional prompt engineering involves crafting short instructions for each task, often ad-hoc and fragile. In contrast, a Skill is a comprehensive, reusable asset that encapsulates all knowledge and tools needed for a task, making it more durable and scalable.

Why is organizing Skills into folders important?

Folders allow bundling multiple assets—instructions, scripts, data—making Skills more versatile, easier to update, and capable of capturing tribal and institutional knowledge that improves over time.

Can other companies adopt this Skills approach?

While promising, it remains to be seen how widely this method can be implemented outside Anthropic. Adoption depends on tooling, organizational culture, and specific use cases.

What are the main benefits of this Skills model?

It enhances output consistency, accelerates onboarding, and creates an evolving knowledge asset that improves with use, ultimately making AI deployment more reliable and aligned with business needs.

Source: ThorstenMeyerAI.com

You May Also Like

Show HN: Leaves – A text-UI Disk Usage Treemap Visualizer

A new open-source project called Leaves offers a text-based disk usage treemap tool for terminal environments, filling a gap for remote and server analysis.

Today’s NYT Connections Hints, Answers and Help for June 27, #1112

Get the latest confirmed hints, answers, and assistance for the NYT Connections puzzle on June 27, 2024, puzzle #1112.

Postgres Data Stored In Parquet On S3: LTAP Architecture Explained

An overview of how Postgres data is stored as Parquet files on S3 using the LTAP architecture, highlighting confirmed technical details and implications.

The Switch: You Never Owned the AI You Depend On

Recent events reveal that AI models are controlled via access points that can be shut off instantly by governments or companies, exposing dependency risks.