skill-creator

Create, update, and review Picoclaw skills with structured SKILL.md guidance.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/qiushido/picoclaw-lite --skill skill-creator-qiushido
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/qiushido/picoclaw-lite/tree/main/workspace/skills/skill-creator
Command: npx skills add https://github.com/qiushido/picoclaw-lite --skill skill-creator-qiushido

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective agent skills requires knowing the right structure, naming rules, frontmatter format, and how to organize scripts, references, and assets. This Skill provides the complete methodology so new or updated skills are consistent, concise, and correctly triggered. ## Core Features & Use Cases - Skill Authoring Guidance: Step-by-step process covering understanding use cases, planning reusable resources, creating the directory, editing SKILL.md, verifying, and iterating. - Progressive Disclosure Patterns: Patterns for splitting content between SKILL.md and reference files to keep context usage lean. - Bundled Resource Rules: Clear criteria for when to include scripts/, references/, and assets/ directories and what to avoid. - Use Case: When you notice a repeated workflow, such as rotating PDFs or generating frontend boilerplate, use this Skill to turn it into a reusable, well-structured Picoclaw skill. ## Quick Start Create a new Picoclaw skill named pdf-rotator that rotates PDF files, following the skill-creator guidelines.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Picoclaw skill?

Create a directory under workspace/skills/<skill-name>/ containing a SKILL.md file with YAML frontmatter defining name and description, followed by Markdown instructions. Add optional scripts/, references/, or assets/ directories only when the skill actually needs them.

What should go in a SKILL.md description field?

The description must state both what the skill does and when it should trigger, since it is the primary mechanism the agent uses for discovery. Include all when-to-use information in the frontmatter, not in the body, because the body loads only after triggering.

When should I use scripts versus references in a skill?

Use scripts/ for deterministic, repeatedly rewritten executable code like PDF rotation, and references/ for detailed documentation the agent loads only when needed, such as schemas or API specs. Keep SKILL.md lean by moving detailed material into reference files.

What files should not be included in a skill?

Do not include auxiliary documentation such as README.md, INSTALLATION_GUIDE.md, QUICK_REFERENCE.md, or CHANGELOG.md. A skill should contain only the files an agent needs to perform the task, avoiding clutter and context waste.

How long should a SKILL.md body be?

Keep the SKILL.md body under 500 lines and under 5k words, splitting content into reference files when approaching that limit. Reference files should link directly from SKILL.md with clear guidance on when to read them.