Test Cherry Studio PRs by resolving and checking out a PR, statically inspecting its changes, running interactive UI tests against a safely tracked Electron instance through CDP, producing a structured report, cleaning up only the owned test instance, and restoring the original branch.
skill-creator
skill-creator is an open-source testing skill for Claude Code and compatible agents, published by CherryHQ. Its author describes it as: “Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill…”. The project has 51k stars on GitHub and is available under the AGPL-3.0-only license. Add it to your setup with `git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/skill-creator`.
What skill-creator does
You are running inside Cherry Studio. Skills live in a managed registry that Cherry keeps in sync with the filesystem automatically — there is **no** install or register tool to call, and you should **ignore** any `package_skill.py` / `.skill` packaging steps mentioned later in this file (they apply to Claude Code / Claude.ai, not here).
Installation
Add skill-creator to your agent with:
git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/skill-creatorAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for skill-creator is organised into these sections:
- Cherry Studio workflow (READ FIRST — overrides packaging / install steps below)
- Communicating with the user
- Creating a skill
- Capture Intent
- Interview and Research
- Write the SKILL.md
- Skill Writing Guide
- Writing Style
- Test Cases
- Running and evaluating test cases
- Step 1: Spawn all runs (with-skill AND baseline) in the same turn
- Step 2: While runs are in progress, draft assertions
When to use it
Reach for skill-creator when you want testing help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear AGPL-3.0-only license — safe to read and adapt
- Ships in CherryHQ/cherry-studio, an established project with 50,722 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does skill-creator do?
- Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
- How do I install skill-creator?
- Run git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/skill-creator in your agent, then reload your skills. Review the source at https://github.com/CherryHQ/cherry-studio before installing.
- Is skill-creator free to use?
- Yes. skill-creator is free and open source under the AGPL-3.0-only license, so you can read, run, and adapt it within that license's terms.
- Where does skill-creator come from?
- skill-creator ships inside CherryHQ/cherry-studio, a repository that contains 20 catalogued skills in total. The repository's 50,722 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Testing →
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.