📊 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 ‘Skills’ in AI systems are better understood as folders containing instructions and tools rather than simple prompts. This approach enhances consistency, onboarding, and continuous improvement within organizations. The company ran hundreds of Skills across its engineering team, emphasizing their value as evolving assets.

Anthropic has revealed that its AI ‘Skills’ are not just prompts but comprehensive folders containing instructions, scripts, and reference materials, which it has used across hundreds of engineering projects. This shift from ad-hoc prompting to reusable, institutional units aims to make AI outputs more consistent, improve onboarding, and foster continuous refinement. The approach represents a significant change in how organizations can leverage AI systems for operational tasks.

According to a recent publication by Anthropic, a ‘Skill’ is defined as a container—akin to a folder—that includes instructions, reference documents, scripts, templates, data, configuration, and hooks. This structure allows AI agents to discover, read, and execute the contents dynamically, moving beyond simple prompt-based interactions.

Anthropic’s internal experience involved running hundreds of Skills within its engineering organization, which revealed that Skills serve three core functions: ensuring output consistency across users, compressing onboarding knowledge into usable units, and enabling continuous improvement through iteration. The company emphasizes that Skills are assets, not just tools, and can justify dedicated engineering effort to perfect them.

Anthropic identified nine categories of Skills, including library references, product verification, data analysis, automation, code scaffolding, review, deployment, runbooks, and infrastructure operations. The company highlights that verification Skills—those that check and validate work—are among the most valuable, as they directly impact output quality.

At a glance
reportWhen: published recently, based on internal A…
The developmentAnthropic published a detailed account of its experience using ‘Skills’ as reusable, containerized units for AI-driven work processes, shifting the paradigm from prompts to organizational assets.
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 Operations with Reusable Skills

This development signifies a shift in how organizations can embed AI into their workflows, making automation more reliable and maintainable. By viewing Skills as institutional assets, companies can reduce variability, streamline onboarding, and foster continuous improvement, ultimately leading to more robust AI deployment.

It also demonstrates a move away from fragile prompt engineering towards durable, versioned assets that can evolve over time. This approach could influence industry standards for operational AI and prompt engineering practices, emphasizing structured, reusable components over ad-hoc instructions.

Amazon

AI automation script templates

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompting to Asset-Based AI Development

Traditional AI prompt engineering often involves crafting specific instructions for each interaction, which can be fragile and hard to maintain at scale. Recent industry efforts have sought to improve consistency and reusability, but Anthropic’s approach formalizes this by creating containerized ‘Skills’—structured folders that encapsulate all necessary knowledge and tools.

Previously, organizations relied on repeated prompt tuning or manual scripting. Anthropic’s internal experiments with running hundreds of Skills have shown that this method leads to more predictable outputs, easier onboarding, and scalable improvement. The idea aligns with broader trends towards modular, maintainable AI systems.

This approach also builds on prior practices in software engineering, where reusable modules and version control have become standard, applied here to AI workflows to enhance reliability and institutional memory.

“A Skill is not just a prompt saved in a file; it’s a folder containing instructions, scripts, and knowledge that the agent can discover and execute. This fundamentally changes how we design AI workflows.”

— Thorsten Meyer, AI researcher at Anthropic

Amazon

AI instruction management tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Skills Implementation

While Anthropic’s internal results are promising, it remains unclear how broadly applicable this approach is across different organizations and AI systems. Details about how Skills are maintained, versioned, and scaled in complex environments are still emerging. Additionally, the long-term impact on AI safety, transparency, and governance has not been fully addressed.

It is also uncertain whether other companies will adopt this model at scale or develop alternative structures that achieve similar benefits.

Amazon

AI project verification tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Standardization

Organizations interested in applying the Skills approach will likely begin by cataloging their internal processes and creating containerized units for critical workflows. Industry groups and standards bodies may explore formalizing this concept to promote best practices. Further research and case studies will clarify the scalability and long-term benefits of Skills as organizational assets.

Anthropic may also continue refining its methodology, sharing lessons learned, and developing tooling to facilitate broader adoption.

Amazon

AI infrastructure automation kits

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 container—similar to a folder—that includes instructions, scripts, reference documents, and configurations. It enables AI agents to discover, read, and execute complex workflows reliably.

How does this differ from traditional prompt engineering?

Traditional prompts are single instructions that can be fragile and hard to maintain. Skills are structured, reusable assets that encapsulate all knowledge needed to perform a task, improving consistency and scalability.

What are the benefits of using Skills for organizations?

Skills improve output consistency, reduce onboarding time, enable continuous improvement, and serve as durable institutional assets that evolve over time.

Are Skills applicable outside of AI coding teams?

Yes, the concept can be adapted for operational workflows, automation, and other organizational processes that benefit from structured, reusable knowledge containers.

What challenges might organizations face adopting Skills?

Challenges include developing effective Skills, managing versioning and updates, and integrating this approach into existing workflows and tooling.

Source: ThorstenMeyerAI.com

You May Also Like

RSVP-and-payment co-host tool for supper club hosts

A new co-host dashboard for supper club hosts aims to streamline RSVP, dietary notes, and payments for recurring private dinners, with testing underway.

CULTURE: How SMU Mustangs DEFY NIL Trends—Coach Scott Nady REVEALS Winning Recruiting STRATEGY

SMU head coach Scott Nady discusses how the Mustangs are building a competitive team despite NIL challenges, emphasizing innovative recruiting tactics.

Threlmark: Disk Is the Contract

Threlmark introduces a new approach where project roadmaps are plain JSON files on disk, enabling open, interoperable, and durable planning tools.

Parenting signal monitor: Central Texas families invited to free 30‑minute swim safety lesson

Central Texas families are invited to participate in a free 30-minute swim safety lesson aimed at improving water safety skills.