These are the workflows the Cherry Studio team runs every day. We package them as skills so our AI agents handle the boring stuff — browser testing, filing bugs across two systems, drafting PRDs, turning transcripts into content, processing expenses.
We're sharing the ones we've cleaned up enough to be useful outside our walls. We'll keep adding more as we make them shareable.
Most of these cut "coordination tax" — the handoffs between tools and people that burn time but don't need human judgment.
| Pattern | Example | What the skill automates |
|---|---|---|
| Test → Track in two systems | Find a staging bug → file in Feishu Bitable + GitHub simultaneously | Captures browser evidence (DOM, console, network, screenshots), writes both records, deduplicates against existing issues |
| Requirement → Structured PRD → Issue | A feature idea from a meeting note → bilingual draft → GitHub issue | Enforces research (search existing issues, PRs, code), locks format (Background/Goal/Spec/Verification/Related), requires human approval before creation |
| Transcript → Publishable content | A recorded talk → blog post or thread | Learns style from past writing, fact-checks against sources, corrects ASR errors |
| Invoice → Reimbursement → Ledger | A stack of receipts → approval workflow → financial record | Batch aggregation, approval routing, dashboard |
The pattern: humans decide, the skill formats, tracks, and syncs across systems.
| Skill | Purpose | What it does |
|---|---|---|
| test-and-report | Manual testing + dual-track bug filing | Captures browser evidence, files simultaneously to Feishu Bitable and GitHub, enforces dedup, prompts for priority |
| Skill | Purpose | What it does |
|---|---|---|
| prd-creator | Bilingual PRD → GitHub issue | Research phase, opinionated format, human approval gate, Project board integration |
| transcript-to-content | Transcripts → posts or articles | Style learning, source fact-checking, ASR correction, multi-format output |
| Skill | Purpose | What it does |
|---|---|---|
| expense-reimbursement | Invoice → reimbursement → ledger | Batch aggregation, approval workflow, financial dashboard |
| Skill | Purpose | What it does |
|---|---|---|
| cv-expert | JD-matched resume optimization | 7-dimension diagnosis, Gap Q&A to mine real experience, Word-comment annotations, 校招 / 社招 modes |
| interview-retro | Post-interview retrospective | Per-question analysis, 5-dimension scoring, better-answer templates, next-round prep checklist → Feishu doc |
These skills reference our internal stack (Feishu, Cloudflare R2, specific repos) because that's where we run them. The workflow patterns are what's reusable:
- Dual-track submission — filing simultaneously in a project tracker and a dev tracker, with dedup
- Approval-gated issue creation — requiring human review before an agent creates a GitHub issue
- Style-grounded content generation — grounding output in a corpus of past writing
Adapt them to your stack. More skills coming.