Create Claw Skill
Generate OpenClaw- and pi-coding-agent–compatible agent skills using ecosystem conventions instead of Claude Code patterns.
Overview
Create-claw-skill is an agent skill most often used in Build (also Ship, Operate) that scaffolds OpenClaw-native SKILL.md patterns and live doc lookup for the pi-coding-agent ecosystem.
Install
npx skills add https://github.com/gupsammy/claudest --skill create-claw-skillWhat is this skill?
- Documents OpenClaw-only patterns (clawdocs CLI, sub-agent sessions) absent from Claude Code skill docs
- Includes fetch-and-summarize page workflow via web_fetch with 3–5 sentence summaries and link callouts
- Steers authors toward live clawdocs slugs (tools/skills, system-prompt, exec) instead of hardcoded docs
- Supports user-invocable skills with argument hints for URL-driven fetch flows
- Fetch workflow uses a 4-step process (fetch, 3–5 sentence summary, links, error handling)
- Documents 3 clawdocs command modes: get, search, fetch
Adoption & trust: 1 installs on skills.sh; 253 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You know how to write Claude Code skills but lack OpenClaw-specific conventions for clawdocs, delegation, and user-invocable skill bodies.
Who is it for?
Builders shipping custom OpenClaw skills who need fetch-page examples plus ecosystem-specific authoring rules in one place.
Skip if: Teams only on Claude Code with no OpenClaw gateway, or anyone who only needs a one-off URL summary without authoring a reusable skill package.
When should I use this skill?
Authoring or converting agent skills for OpenClaw / pi-coding-agent when Claude Code defaults do not apply.
What do I get? / Deliverables
You get OpenClaw-aligned skill structure, documented research commands, and fetch/summarize patterns ready to ship in the OpenClaw catalog.
- OpenClaw-conformant SKILL.md draft with process steps
- clawdocs lookup commands embedded for maintainable doc references
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Skill authoring is core agent-tooling work during product build, even when the resulting skill will run later in ship or operate. OpenClaw skill templates, clawdocs lookups, and sub-agent delegation are agent-runtime packaging concerns, not generic app frontend or backend code.
Where it fits
Scaffold a new fetch-page skill with argument-hint and web_fetch steps for OpenClaw.
Pull live tools/skills and system-prompt pages via clawdocs instead of pasting stale markdown into SKILL.md.
Validate user-invocable skill UX and error messages before publishing to an OpenClaw skill registry.
Regenerate skill bodies when OpenClaw config or gateway docs change slugs or delegation behavior.
How it compares
Use as an OpenClaw skill authoring guide—not a generic skills.sh meta skill or an MCP server integration.
Common Questions / FAQ
Who is create-claw-skill for?
Solo and indie developers packaging agent skills for OpenClaw, pi-coding-agent, or clawdocs-driven workflows who already use Claude Code–style SKILL.md but need platform-specific patterns.
When should I use create-claw-skill?
During Build when drafting agent-tooling skills; during Ship when hardening user-invocable fetch skills; during Operate when refreshing skills against drifting OpenClaw docs via clawdocs.
Is create-claw-skill safe to install?
Review the Security Audits panel on this Prism page and treat generated skills that call web_fetch or shell as network- and filesystem-capable before enabling in production agents.
SKILL.md
READMESKILL.md - Create Claw Skill
# Fetch Page Fetch the content of a URL and produce a concise summary. ## Process 1. Fetch the URL passed as `$1` using the `web_fetch` tool 2. Summarize the main content in 3–5 sentences, preserving key facts and figures 3. List any notable links or resources mentioned in the page 4. If the URL is inaccessible, report the error and suggest checking the URL format # OpenClaw Ecosystem Patterns OpenClaw-specific patterns that skill authors need to know when generating skills for the pi-coding-agent / OpenClaw ecosystem. These patterns have no equivalent in Claude Code and represent conventions unique to OpenClaw's architecture. --- ## 1. Documentation Research Use `clawdocs` CLI to look up OpenClaw's own documentation from within generated skill bodies: ```bash # Fetch a specific documentation page (no header, quiet mode) clawdocs get "tools/skills" --no-header -q # Search for relevant pages by slug clawdocs search "frontmatter" --slugs-only # Fetch a topic page clawdocs fetch "concepts/system-prompt" --no-header -q ``` Common useful slugs: `tools/skills`, `concepts/system-prompt`, `tools/exec`, `tools/sessions`, `config/gateway`, `tools/groups`. Generated skills that need to reference live OpenClaw config or query capabilities should use `clawdocs` rather than hardcoding documentation that may drift. --- ## 2. Sub-Agent Delegation OpenClaw uses `sessions_spawn` for background delegation. This is the equivalent of Claude Code's `Task(subagent_type=...)`, with key differences: - `sessions_spawn` is **non-blocking** — it launches the sub-agent and the result is announced back to chat when complete (the main agent continues without waiting) - **No `subagent_type`** — all sub-agents are general purpose; there are no specialized agent types to route to - Sub-agents receive only `AGENTS.md` + `TOOLS.md` in their system prompt — they do not inherit the current agent's skills, persona context, or conversation history - Sub-agents can read skill files via the `read` tool if you reference the skill path When to use `sessions_spawn` vs inline execution: - Use inline for steps that must complete before the next step starts - Use `sessions_spawn` for parallel work, long-running operations, or steps whose results are independently useful without blocking the main workflow --- ## 3. Cross-Skill References There is no `Skill` tool in OpenClaw — the model cannot programmatically invoke another skill. Skills are triggered by the routing model when the user's message matches the description. To reference another skill from within a generated skill body: **Option A — Tell the model to read the skill:** ```markdown Read `{baseDir}/../<other-skill-name>/SKILL.md` via the `read` tool to access its instructions. ``` **Option B — Tell the user to invoke it:** ```markdown Instruct the user to type `/<other-skill-name>` to trigger the [other skill] workflow. ``` **Option C — Copy the relevant instructions inline** — for small, stable sub-procedures that shouldn't require the user to switch workflows. Fully qualified skill references are not needed in OpenClaw (there is no plugin namespace to qualify against in frontmatter); just reference by skill name. --- ## 4. Tool Groups OpenClaw organizes tools into groups. When writing skill bodies that reference tools, use the correct OpenClaw tool names (not Claude Code tool names): | Group | Tools | Purpose | |-------|-------|---------| | `group:fs` | `read`, `write`, `edit`, `apply_patch` | File system operations | | `group:runtime` | `exec` (primary), `bash`, `process` | Shell / subprocess execution | | `group:web` | `web_search`, `web_fetch` | Web access | | `group:sessions` | `sessions_spawn`, `sessions_list`, `sessions_get` | Sub-agent delegation | **Key translation table** (Claude Code → OpenClaw): | Claude Code | OpenClaw | |-------------|----------| | `Ba