PythonClaw skill_creator
install
source · Clone the upstream repo
git clone https://github.com/ericwang915/PythonClaw
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ericwang915/PythonClaw "$T" && mkdir -p ~/.claude/skills && cp -r "$T/pythonclaw/templates/skills/meta/skill_creator" ~/.claude/skills/ericwang915-pythonclaw-skill-creator && rm -rf "$T"
manifest:
pythonclaw/templates/skills/meta/skill_creator/SKILL.mdsource content
Skill Creator
When to Use
- The user asks for something no installed skill covers
- An existing skill is too limited and needs a better replacement
- A recurring task would benefit from a dedicated, reusable skill
When NOT to Use
- One-off tasks that existing tools can handle (e.g.,
for shell)run_command - Skills too specific to be reused — generalize first
- Don't hardcode user-specific values (names, URLs, topics) — use parameters
Setup
Uses the
create_skill tool. No API keys or external setup required.
Usage/Commands
- Analyze the gap: identify what capability is missing
- Plan the skill: name, category, scripts, pip dependencies
- Call
with:create_skill
— short, snake_case (e.g.,name
)pdf_summarizer
— one-line summarydescription
— full Markdown bodyinstructions
— e.g.,category
,data
,dev
,webautomation
— dict mapping filenames to source coderesources
— list of pip packagesdependencies
- Activate:
use_skill(skill_name="<name>") - Run it: follow the loaded instructions
Design Principles
- Generic over specific — parameterize everything; avoid hardcoded topics/recipients
- Single responsibility — one skill, one purpose
- Parameterized — use CLI args, not hardcoded values
- Config-driven credentials — read from
underpythonclaw.jsonskills.<name> - Minimal dependencies — only add pip packages when truly needed
- Reusable — ask: "Would this help someone with a different task?"
SKILL.md Body Template
## Instructions <Clear explanation and when to use.> ### Prerequisites <Setup, API keys if needed> ### Usage 1. <steps> 2. Call: `python context/skills/<category>/<name>/<script>.py <args>` 3. <interpret results> ### Examples **Example:** <typical use case> ## Resources | File | Description | |------|-------------| | script.py | <what it does> |
Notes
- Design for reuse: generalize queries, recipients, URLs
- Write production-quality Python with error handling and docstrings
- After creation, call
to load the new instructions before runninguse_skill