What A Skill Is In OpenClaw: Anatomy And Discovery

OpenClaw skills are pluggable capabilities — manifest plus procedure plus examples — that a soul discovers and invokes when the job calls for them. Understanding the anatomy is the first step to building or auditing one. Skills are how an OpenClaw agent grows hands OpenClaw is an open-source agentic framework that runs on your own machine.

10 min · Reviewed 2026

Skills are how an OpenClaw agent grows hands

OpenClaw is an open-source agentic framework that runs on your own machine. Out of the box, an OpenClaw soul — the term OpenClaw uses for an active agent instance — can read files, run commands, and talk to its model. Anything beyond that is a skill: a self-contained bundle of instructions and tools that the soul loads on demand when a request matches.

If you have used Claude Code skills or MCP servers, the shape will feel familiar. The difference is that OpenClaw skills run inside your local soul, are described in plain text the model reads, and discover themselves through trigger descriptions rather than through a custom UI.

The three parts of a skill

Manifest: a small frontmatter block with name, description, and any permissions or trigger keywords. The description is what the soul matches against the user's request.
Procedure: the natural-language instructions the soul follows once the skill is loaded — what steps to run, what tools to call, what output to produce.
Examples and assets: optional templates, sample inputs, helper scripts, or reference data the procedure can point at when it needs concrete shape.

How a soul discovers a skill

When you start a session, OpenClaw scans the configured skill directories and reads each manifest. Only the manifests load into the system prompt at first — not the full procedures. The soul sees a catalog of available skills with their trigger descriptions. When the user's request rings a match, the soul loads the matching skill's procedure into context and follows it.

Invocation: explicit and implicit

Mode	How it fires	When to use
Implicit (lazy)	Soul matches request to skill description and pulls in the procedure	Common workflows where users phrase requests naturally
Explicit (named)	User types `/skill-name` or names it directly	Skills with side effects, multiple matches, or ambiguous triggers
Forced (config)	Configuration pins certain skills to always load	Workspace-wide rules you never want skipped

Where skills live

User-scoped — in your home directory, available to every soul you spawn
Workspace-scoped — checked into a project, version-controlled with your team
Plugin-scoped — shipped by a third-party plugin or registry, namespaced by source
Built-in — bundled with the OpenClaw distribution itself

The big idea: an OpenClaw skill is a manifest plus a procedure plus optional examples, discovered lazily by a soul that scans descriptions and loads only what matches. The description is the resume; the procedure is the interview.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openclaw-skills-anatomy-creators

What is the main idea of "What A Skill Is In OpenClaw: Anatomy And Discovery"?
1. OpenClaw skills are pluggable capabilities — manifest plus procedure plus examples — that a soul discovers and invokes when the job calls for them.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "What A Skill Is In OpenClaw: Anatomy And Discovery"?
1. manifest
2. skill
3. procedure
4. soul
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. Manifest: a small frontmatter block with name, description, and any permissions or trigger keywords.
4. Treat the AI output as automatically correct
What should a careful learner remember about "Manifest plus procedure plus examples — that is the whole pattern"?
1. Use AI to draft or organize ideas about skill, then verify before acting.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use AI for drafting and comparison, but verify before publishing or relying on it.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about skill be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about skill.
Which action would help you apply "What A Skill Is In OpenClaw: Anatomy And Discovery" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Treat the AI output as automatically correct
4. Procedure: the natural-language instructions the soul follows once the skill is loaded — what steps to run, what.

← Back to interactive lesson

Tendril · Creators · Tools Literacy