cc-workflow
Use when deciding which cc-* sub-skill to invoke next, or when sequencing a Cancer Cell (Cell Press) manuscript from scope check through peer-review revision. Routes — it does not replace — the specialized skills.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cc-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Cancer Cell Workflow (cc-workflow) ## Overview This is the router. It does not replace any specialized skill — it tells you **which cc-* skill to use at your current stage** of a Cancer Cell (Cell Press) molecular / translational oncology manuscript. Default assumption: unless the user says otherwise, treat the target as **Cancer Cell**, where the bar is a clear molecular mechanism validated across orthogonal systems (cells + in vivo + ideally human data), reported with STAR Methods rigor, framed for translational relevance without overclaiming. ## When to trigger - The user asks "what should I do next?" - A draft arrives and you must diagnose the current bottleneck - Work is thrashing between experiments, figures, and writing - A decision letter / reviewer reports arrive and you must switch into revision mode ## Routing table | Current symptom | Next skill | |------------------------------------------------------------------------|-----------------------------| | Unsure whether the story is a Cancer Cell paper at all | `cc-scope-fit` | | Mechanism rests on one system (cells only / no in vivo / no human data) | `cc-study-design` | | Controls, replicates, randomization, or blindin
- Overview
- When to trigger
- Routing table
- Default order
- Decision shortcuts
- Differences vs. JAMA-style clinical packs
- Worked routing example
- Stage diagnosis cues
- Evidence-spine manifest
- Anti-patterns
What does the cc-workflow skill do?
Use when deciding which cc-* sub-skill to invoke next, or when sequencing a Cancer Cell (Cell Press) manuscript from scope check through peer-review revision. Routes — it does not replace — the specialized skills.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cc-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.