skillboardUpdated every 6 hours
skillboardCreate 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.
Cherry Studio workflow (READ FIRST — overrides packaging / install steps below) 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 / packaging steps mentioned later in this file (they apply to Claude Code / Claude.ai, not here). To create a new skill, write it straight into Cherry's managed skills directory: 1. Resolve the directory once by…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/skill-creator · pinned to the source commit
git clone https://github.com/CherryHQ/cherry-studio.git
cd cherry-studio
git checkout 18c287b020ff95cc2a12fc389ea4748957fbaf49
mkdir -p ".claude/skills/skill-creator"
cp -r "resources/skills/skill-creator" ".claude/skills/skill-creator"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 18c287b020ff. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
Instructs shell/process/package operations that run commands on the host.
Evidence: subprocess· fingerprint f77b7310faf3f1f4
Uses encoding/eval patterns that can hide executable content.
Evidence: [redacted]· fingerprint 7f712a33096ba821