Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Cc Workflow

ASecurity

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.

1,052 stars
0 votes
0 copies
1 views
Added 6/4/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill cc-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cc Workflow?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Cc Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-cc-workflow/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-cc-workflow)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: cc-workflow
description: 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.
---

# 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 blinding are unclear           | `cc-study-design`           |
| No Key Resources Table; cell lines unauthenticated; antibodies unvalidated | `cc-reporting-standards` |
| `n` undefined, pseudo-replication risk, wrong test, error bars unlabeled | `cc-statistics`            |
| Representative images with no quantification; multi-panel figure messy | `cc-figures-tables`         |
| Need Summary / Highlights / eTOC blurb / graphical abstract            | `cc-structured-abstract`    |
| Missing IACUC/IRB approval, consent, biosafety, or data-availability statement | `cc-ethics-registration` |
| Prose overclaims; Results read like a lab notebook; weak Discussion    | `cc-writing-style`          |
| Need a cover letter framing fit and significance                       | `cc-cover-letter`           |
| About to submit and need a final preflight                             | `cc-submission`             |
| Reviewer reports arrived; need a point-by-point response               | `cc-peer-review-revision`   |

## Default order

1. `cc-scope-fit` — confirm mechanism + translational relevance before investing more
2. `cc-study-design` — design / audit orthogonal validation, controls, replicates, in vivo rigor
3. `cc-reporting-standards` — STAR Methods, Key Resources Table, authentication, RRIDs
4. `cc-statistics` — define `n`, pick tests, correct for multiplicity, label error bars
5. `cc-figures-tables` — multi-panel mechanistic figures with quantification + image integrity
6. `cc-structured-abstract` — Summary, Highlights, eTOC blurb, graphical abstract
7. `cc-ethics-registration` — approvals, consent, biosafety, data-deposition statements
8. `cc-writing-style` — Cell Press prose and claim calibration (polish stage)
9. `cc-cover-letter` — significance / fit / suggested reviewers
10. `cc-submission` — pre-submission preflight
11. `cc-peer-review-revision` — after reviewer reports

> `cc-writing-style` and `cc-structured-abstract` are **late-stage polish** — do not finalize them while the mechanism or in vivo validation is still missing.

## Decision shortcuts

- "It's only in cell lines" → `cc-study-design` (add in vivo / human validation)
- "Reviewers will ask if the cell line is authenticated" → `cc-reporting-standards`
- "I used n=3 wells from one experiment" → `cc-statistics` (pseudo-replication)
- "I have a beautiful blot but no densitometry" → `cc-figures-tables`
- "My title promises a therapy but I have no in vivo efficacy" → `cc-scope-fit` then `cc-writing-style`
- "No GEO accession yet" → `cc-ethics-registration` / `cc-submission`
- "Three reviewers, consultative cross-review" → `cc-peer-review-revision`

## Differences vs. JAMA-style clinical packs

If the work is a clinical trial or epidemiological cohort with patient-level outcomes as the core unit, a clinical-trial pack (CONSORT / STROBE / registration) fits better. Cancer Cell's unit is a **mechanism validated across systems**, not a trial endpoint.

## Anti-patterns

- **Do not** skip `cc-scope-fit` — editors triage on mechanism + translational fit first
- **Do not** let `cc-figures-tables` polish panels before `cc-statistics` has fixed `n` and tests
- **Do not** let `cc-peer-review-revision` draft a response before the revised experiments / text exist

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →