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 designing AI skills as comprehensive folders—containing instructions, scripts, and data—improves consistency, onboarding, and scalability. This approach shifts the focus from prompts to structured assets, influencing how organizations deploy AI.

Anthropic has revealed that its internal AI Skills are structured as folders containing instructions, scripts, and assets, rather than simple prompts. This approach, shared by a Claude Code engineer, signifies a shift in how organizations can build durable, reusable AI capabilities that improve consistency, onboarding, and operational efficiency.

The core insight from Anthropic is that a Skill is not just a prompt or a text snippet but a folder—a container that includes instructions, reference documents, scripts, templates, configuration, and hooks. This structure allows AI agents to discover, read, and execute the contents dynamically, making the Skills more robust and adaptable. Anthropic’s internal research shows that this method turns ad-hoc prompting into a durable institutional capability. By packaging knowledge into these folders, organizations can standardize outputs, streamline onboarding, and continuously improve Skills through iteration. The company has categorized its internal Skills into nine types, ranging from library references to infrastructure operations, with verification Skills identified as particularly high-value for quality control. This approach contrasts with traditional prompt engineering, emphasizing structured assets over ephemeral instructions. Experts note that this method enables organizations to embed tribal knowledge, guardrails, and automation tools directly into their AI workflows, making them more reliable and scalable.
At a glance
reportWhen: published March 2024
The developmentAnthropic published insights from running hundreds of AI Skills internally, emphasizing that Skills are folders, not prompts, which enhances organizational AI capabilities.
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 Skill Development for Organizational Use

This shift from prompts to folder-based Skills represents a fundamental change in how organizations can deploy AI at scale. It allows for consistent outputs across teams, faster onboarding for new staff, and a continuous improvement cycle as Skills are refined over time. For businesses, this means more reliable AI automation, better knowledge retention, and a strategic asset that appreciates as it evolves. The approach could influence industry standards, encouraging companies to treat AI capabilities as structured assets rather than ad-hoc prompts, ultimately making AI deployment more predictable and manageable.
Amazon

AI development folder structure tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Asset-Based AI Skills

Prior to this development, most organizations relied on prompt engineering—crafting specific instructions for AI models on a per-use basis. While effective for short-term tasks, this approach often led to inconsistencies, onboarding challenges, and difficulty scaling. Anthropic’s internal experiments with hundreds of Skills demonstrated that packaging these as folders containing instructions, code, and data creates a reusable, scalable framework. This method aligns with broader trends in AI development, emphasizing modularity, version control, and institutional memory. The company’s categorization into nine Skill types provides a practical roadmap for organizations to identify gaps and improve their AI workflows systematically.

“A Skill is a folder—containing instructions, scripts, and assets—not just a prompt. This change fundamentally shifts how organizations can build durable AI capabilities.”

— Thorsten Meyer, AI researcher at Anthropic

Amazon

AI scripting and instruction management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Scalability and Implementation

It is not yet clear how widely this folder-based Skills approach has been adopted outside Anthropic or how easily other organizations can implement it at scale. Details on tooling, integration with existing systems, and long-term maintenance are still emerging, and there is ongoing discussion about best practices for structuring and updating Skills across complex organizations.
Amazon

AI workflow automation templates

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 evaluate their current workflows and identify knowledge assets that can be encapsulated as Skills. Future developments may include standardized frameworks, tooling support, and industry benchmarks to facilitate widespread adoption. Anthropic and other AI developers are likely to publish further guidance and case studies demonstrating how to implement folder-based Skills effectively at scale.
Amazon

AI knowledge base organization tools

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

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

How does this approach improve AI deployment?

It standardizes outputs, accelerates onboarding, and allows continuous improvement by packaging tribal knowledge and automation tools into reusable assets.

Can other organizations adopt this folder-based Skills model?

While promising, adoption depends on existing infrastructure and workflows. Organizations will need to develop or acquire tooling to manage and discover Skills effectively.

What are the main challenges of implementing Skills as folders?

Challenges include structuring knowledge effectively, maintaining version control, and integrating with current AI systems without disrupting existing processes.

Will this method replace prompt engineering entirely?

Not necessarily; it offers a more durable, scalable alternative for institutional knowledge and automation, complementing prompt engineering for quick tasks.

Source: ThorstenMeyerAI.com

You May Also Like

Waves, Not a Wall: Inside DeepMind’s Map From AGI to Superintelligence

DeepMind researchers publish a detailed framework outlining pathways from human-level AI to superintelligence, highlighting scaling, paradigm shifts, and challenges.

The United States: The High-Variance Bet

The US is pursuing a minimal regulation strategy for AI and social safety nets, emphasizing market dynamism over federal oversight amid rapid technological change.

Singapore: Engineer the Transition

Singapore’s comprehensive approach to workforce transition combines reskilling, AI innovation, and targeted policies, aiming to pre-empt automation displacement.

After the Paycheck: The Book I Wrote Because Nobody Else Would Tell the Truth About AI and Your Income

Author Thorsten Meyer releases ‘After the Paycheck,’ analyzing AI’s real influence on jobs, ownership, and the economy, emphasizing ownership over automation.