Loading lesson…
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.
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.
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.
| 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 |
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.
15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openclaw-skills-anatomy-creators
What is the core idea behind "What A Skill Is In OpenClaw: Anatomy And Discovery"?
Which term best describes a foundational idea in "What A Skill Is In OpenClaw: Anatomy And Discovery"?
A learner studying What A Skill Is In OpenClaw: Anatomy And Discovery would need to understand which concept?
Which of these is directly relevant to What A Skill Is In OpenClaw: Anatomy And Discovery?
Which of the following is a key point about What A Skill Is In OpenClaw: Anatomy And Discovery?
What is one important takeaway from studying What A Skill Is In OpenClaw: Anatomy And Discovery?
Which of these does NOT belong in a discussion of What A Skill Is In OpenClaw: Anatomy And Discovery?
What is the key insight about "Manifest plus procedure plus examples — that is the whole pattern" in the context of What A Skill Is In OpenClaw: Anatomy And Discovery?
What is the key insight about "This is the progressive-disclosure pattern" in the context of What A Skill Is In OpenClaw: Anatomy And Discovery?
What is the key insight about "Trigger descriptions decide everything" in the context of What A Skill Is In OpenClaw: Anatomy And Discovery?
Which statement accurately describes an aspect of What A Skill Is In OpenClaw: Anatomy And Discovery?
What does working with What A Skill Is In OpenClaw: Anatomy And Discovery typically involve?
Which of the following is true about What A Skill Is In OpenClaw: Anatomy And Discovery?
Which best describes the scope of "What A Skill Is In OpenClaw: Anatomy And Discovery"?
Which section heading best belongs in a lesson about What A Skill Is In OpenClaw: Anatomy And Discovery?