📊 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 as ‘Skills’ structured like folders—containing instructions, scripts, and assets—improves consistency and onboarding. This approach shifts from prompts to durable, shareable organizational assets.

Anthropic has introduced a new framework for building AI capabilities, defining Skills as folders rather than prompts. This approach, based on extensive internal deployment, aims to make AI outputs more consistent, scalable, and maintainable across organizations. You can learn more about organizing AI capabilities as Skills. The development signals a shift in how companies can embed organizational knowledge into AI systems for long-term, reliable use.

In a detailed write-up, Anthropic explains that a Skill is not merely a prompt saved as text but a folder containing instructions, reference documents, scripts, templates, and configuration data. This structure allows AI agents to discover, read, and execute the contents dynamically, effectively turning organizational knowledge into a reusable asset. For a deeper dive, see how Skills are structured like folders.

Anthropic’s internal experiments involved running hundreds of Skills across its engineering teams, leading to the identification of nine core categories, including data fetching, code scaffolding, verification, and operational procedures. The most impactful Skills, according to Anthropic, are those that verify output quality, reducing errors and improving reliability. Read more about the concept of Skills as organizational assets.

By formalizing Skills as containers of procedural and contextual knowledge, the company aims to standardize outputs, accelerate onboarding, and build a cumulative library of institutional expertise that improves over time. This approach contrasts sharply with traditional prompt engineering, which often involves retyping instructions repeatedly without permanence or version control.

At a glance
reportWhen: published March 2024
The developmentAnthropic published insights from running hundreds of ‘Skills’ internally, emphasizing a folder-based approach over prompt-based methods for AI agent 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 Organizational Knowledge into Reusable AI Assets

This development matters because it offers a practical way for companies to embed long-term, durable capabilities into their AI systems. By treating Skills as structured containers, organizations can ensure more consistent outputs, reduce onboarding time for new staff, and create a growing library of institutional knowledge that improves with use. It shifts the focus from ad-hoc prompt tuning to building reusable, versioned assets that can be shared and maintained over time, potentially transforming AI deployment practices across industries.

Amazon

AI development organizational tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Asset-Based AI Capabilities

Until now, most AI teams relied on prompt engineering—crafting and reusing prompts for specific tasks—which often led to inconsistent results and repeated effort. Anthropic’s internal experience with running hundreds of Skills revealed that organizing capabilities into folders containing instructions, scripts, and reference data creates a more durable, scalable approach. This shift aligns with broader trends toward modular, maintainable AI systems and reflects lessons learned from deploying AI in complex, real-world environments.

Previous efforts focused on prompt tuning or fine-tuning models; Anthropic’s approach emphasizes creating a library of structured capabilities that can be discovered, read, and executed dynamically, akin to software modules. This method enables better control, repeatability, and continuous improvement of AI behavior.

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

— Thorsten Meyer, AI researcher at Anthropic

Amazon

AI skills management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Uncertainties in Adoption and Implementation Challenges

It is not yet clear how widely this folder-based Skills approach will be adopted outside Anthropic or how easily organizations can transition from traditional prompt engineering. Details about the tooling, integration complexity, and scalability across different AI platforms remain under development. Additionally, the long-term impact on AI safety, control, and performance consistency is still being evaluated.

Amazon

AI instruction and script folders

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Refinement

Anthropic plans to further develop and document its Skills framework, encouraging other organizations to experiment with folder-based assets. Industry collaborations and tools are expected to emerge to facilitate adoption. Monitoring how this approach influences AI reliability, maintainability, and organizational knowledge management over the coming months will be critical.

Amazon

AI knowledge base templates

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does a Skill differ from a traditional prompt?

A Skill is a structured folder containing instructions, scripts, and assets, whereas a prompt is a simple text instruction. Skills enable dynamic discovery and execution of complex capabilities, making them more durable and reusable.

What are the main benefits of using Skills as folders?

Skills improve output consistency, facilitate onboarding by capturing organizational knowledge, and create a library of assets that can grow and improve over time.

Are Skills applicable across different AI platforms?

While Anthropic’s implementation is specific, the concept of organizing capabilities as structured assets could translate to other systems with appropriate tooling and integration.

What challenges might organizations face adopting this approach?

Potential challenges include tooling complexity, integration with existing workflows, and ensuring that Skills remain maintainable as they grow in number and complexity.

Will this approach replace prompt engineering entirely?

It’s unlikely to replace prompt engineering immediately but offers a complementary, more durable method for building organizational AI capabilities.

Source: ThorstenMeyerAI.com

You May Also Like

A Frontier AI Model Just Went Dark for 18 Days. The Kill-Switch Is Real Now.

An advanced AI model was globally disabled for 18 days following US government orders, marking a new era of AI regulation and control.

The Switch: You Never Owned the AI You Depend On

A U.S. order against Anthropic and OpenAI’s GPT-4o retirement show how model access can vanish, leaving AI users and builders exposed.

Apertus. The architectural template.

Apertus, developed by Swiss federal research institutions, introduces a new model for European sovereign AI, emphasizing openness, multilingual support, and compliance.

SpaceX Owns Every Layer of AI Now. The Model Is Still the Weak Link.

SpaceX’s $60 billion acquisition of Cursor completes its control over AI infrastructure, but the core model still faces performance limitations.