cherry-studio
Review Skills in CherryHQ/cherry-studio, with license, maintenance context, and source paths.
- Skills
- 15
- Repository stars
- 49,062
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Repository
- Canonical name
- cherry-studio
- Public sources
- 1
- License context
- AGPL-3.0
Source entries
Agent Skills from cherry-studio
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
CherryHQ/cherry-studio
cherry-assistant-guide
Review cherry-assistant-guide's use cases, installation, workflow, and original source instructions.
CherryHQ/cherry-studio
cherry-electron-dev
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance across instructions and launch or replace one only when required.
CherryHQ/cherry-studio
cherry-pr-test
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.
CherryHQ/cherry-studio
create-skill
Create a new skill in the current repository. Use when the user wants to create/add a new skill, or mentions creating a skill from scratch. This skill follows the workflow defined in .agents/skills/README.md and helps scaffold, validate, and sync new skills.
CherryHQ/cherry-studio
demand-first-review
Use when reviewing a PR, API, IPC channel, endpoint, parameter, type, config, or architectural extension point that adds or expands shared surface area, especially when consumers are absent, exports are unused or speculative, existing consumers are hack-heavy, forward compatibility is claimed, or multiple similar APIs may express one demand.
CherryHQ/cherry-studio
faq-collector
Review faq-collector's use cases, installation, workflow, and original source instructions.
CherryHQ/cherry-studio
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
CherryHQ/cherry-studio
gh-create-issue
Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.
CherryHQ/cherry-studio
gh-create-pr
Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads `.github/pull_request_template.md`, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of skipping sections.
CherryHQ/cherry-studio
gh-pr-review
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks, React/UI conventions, and tests. Supports single-agent review with interactive fix selection or multi-agent reviewer-verifier review with risk-based auto-fix. To diagnose gaps in the s
CherryHQ/cherry-studio
issue-reporter
Use it for research tasks; the detail page covers purpose, installation, and practical steps.
CherryHQ/cherry-studio
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch with PR. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository