skill-creator
An AI agent skill from sipeed/picoclaw, scored 68 out of 100 by code.
Code score by group
It loses the most points in Done criteria (11), the group that checks whether there is a checklist and a step that verifies the work.
What the author says it does
Create, update, or review Picoclaw skills. Use when writing a new skill, modifying an existing SKILL.md, turning a repeated workflow into a reusable skill, or organizing scripts, references, and assets for a skill.
This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.
- Repository
- sipeed/picoclaw
- Folder
- workspace/skills/skill-creator
- License
- MIT
- GitHub stars
- 30,126
- SKILL.md lines
- 359
- Other files
- 0
Add skill-creator to your agent
npx skills add sipeed/picoclaw --skill skill-creator
The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.
More skills from sipeed/picoclaw
-
hardware
Read and control I2C and SPI peripherals on Sipeed boards (LicheeRV Nano, MaixCAM, NanoKVM).
67C -
agent-browser
Browser automation via agent-browser CLI. Use when the user needs to navigate websites, fill forms, click buttons, take screenshots, extract data, or test web apps.
66C -
picoclaw-agent
Configure, extend, debug, or contribute to PicoClaw itself. Use when the task is about PicoClaw CLI commands, config.json, gateway, auth, models, skills, MCP servers, cron, routin…
62C -
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
58C -
weather
Get current weather and forecasts with verified location matching (no API key required).
58C -
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
50D -
github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
48D
Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.