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 Reporting Standards

ASecurity

Use when assembling STAR Methods and the Key Resources Table for a Cancer Cell (Cell Press) manuscript, and when ensuring rigor / reproducibility (cell-line authentication, mycoplasma, antibody validation, ARRIVE animal reporting, data/code deposition). It governs reporting; it does not design experiments.

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Cc Reporting Standards?

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

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

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

Download with Pro
Files
SKILL.md
---
name: cc-reporting-standards
description: Use when assembling STAR Methods and the Key Resources Table for a Cancer Cell (Cell Press) manuscript, and when ensuring rigor / reproducibility (cell-line authentication, mycoplasma, antibody validation, ARRIVE animal reporting, data/code deposition). It governs reporting; it does not design experiments.
---

# Rigor, Reproducibility & STAR Methods (cc-reporting-standards)

## When to trigger

- Drafting or auditing the Methods section for a Cell Press submission
- Reviewers may flag unauthenticated cell lines, undefined reagents, or missing deposition
- Need to build the Key Resources Table (KRT) and assign RRIDs
- Animal or sequencing work needs structured rigor reporting

## STAR Methods structure

Cell Press uses **STAR Methods** (Structured, Transparent, Accessible Reporting). Organize methods under standardized headings:

1. **Key Resources Table (KRT)** — at the top; tabulates every critical reagent/resource with source, identifier, and RRID.
2. **Resource availability** — Lead contact; Materials availability (plasmids, cell lines, mouse strains); Data and code availability.
3. **Experimental model and study participant details** — cell lines, animals, human subjects, organoids/PDX provenance.
4. **Method details** — full protocols, reproducible by an expert.
5. **Quantification and statistical analysis** — what test, what `n`, what software (links to `cc-statistics`).

## Key Resources Table — what must carry an RRID / identifier

| Category | Required detail |
|----------|-----------------|
| Antibodies | Host, clone, vendor, catalog #, RRID, dilution/application |
| Cell lines | Name, sex/origin, source, authentication status, RRID (Cellosaurus) |
| Chemicals / inhibitors | Vendor, catalog #, identifier |
| Critical kits | Vendor, catalog # |
| Deposited data | Repository + accession (GEO/SRA/PRIDE/PDB) |
| Oligos / sgRNAs / primers | Full sequences |
| Recombinant DNA / plasmids | Source, Addgene # / RRID |
| Organisms / strains | Strain, source, RRID (e.g., MGI/JAX) |
| Software / algorithms | Name, version, URL, RRID |

## Cell-line rigor (frequent reviewer target)

- **Authenticate** human cell lines (STR profiling); reference Cellosaurus; state the source.
- **Mycoplasma testing** — state that lines were tested negative; give frequency.
- Flag any misidentified/commonly contaminated lines (ICLAC register) and justify use.
- Report passage range and culture conditions enough to reproduce.

## Antibody validation

- Give clone, catalog, RRID, and **application-specific** validation (KO/KD control, single band of expected MW, IHC titration with positive/negative tissue).
- For new/critical antibodies, show validation in the supplement.

## Animal reporting (ARRIVE 2.0 essentials)

- Species, strain, sex, age, source; housing and husbandry.
- **Sample size** rationale; **randomization**; **blinding** of outcome assessment.
- Inclusion/exclusion criteria; humane endpoints; number used and analyzed.
- IACUC protocol number and approving institution (statement routed via `cc-ethics-registration`).

## Data and code availability

- Deposit and cite accessions in the KRT and availability statement:
  - Sequencing / arrays → **GEO/SRA**; controlled human genomics → **dbGaP/EGA**
  - Proteomics → **PRIDE**; metabolomics → MetaboLights/Workbench
  - Structures → **PDB** (+ **EMDB** for cryo-EM maps)
- Custom code → versioned public repo with a citable DOI (e.g., Zenodo).
- "Available on request" is unacceptable for these data types.

## Checklist

- [ ] STAR Methods headings used; KRT at top
- [ ] Every antibody, cell line, organism, plasmid, software has source + RRID
- [ ] Human cell lines STR-authenticated; mycoplasma-negative stated
- [ ] Antibody validation described (and shown for critical ones)
- [ ] Animal section reports sample size, randomization, blinding, exclusions
- [ ] All large datasets deposited; accessions in KRT + availability statement
- [ ] Custom code deposited with DOI
- [ ] Lead contact and materials-availability statements present

## Anti-patterns

- Cell lines with no authentication or mycoplasma statement
- Antibodies listed as "anti-X (Abcam)" with no catalog/RRID/validation
- Animal methods with no randomization/blinding/sample-size basis
- Sequencing data "available upon request" with no accession
- Methods too thin to reproduce the experiment

## Output format

```
【STAR Methods】headings complete? KRT present?
【KRT gaps】reagents missing source/RRID: [...]
【Cell-line rigor】authenticated? mycoplasma? contaminated-line flags?
【Antibody validation】adequate / show in supplement: [...]
【Animal rigor】ARRIVE elements present? [...]
【Deposition】GEO/SRA/PRIDE/PDB accessions + code DOI status
【Next step】cc-statistics or cc-ethics-registration
```

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 →