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

Cell Writing

ASecurity

Use to structure a Cell Article and hold its length — Summary, Introduction, Results, Discussion, STAR Methods, figure legends, references — with main-text length and display-item budgets, and Results subheadings driving the single arc.

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Cell Writing?

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

Security grade badge for Cell Writing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-cell-writing/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-cell-writing)

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

Download with Pro
Files
SKILL.md
---
name: cell-writing
description: Use to structure a Cell Article and hold its length — Summary, Introduction, Results, Discussion, STAR Methods, figure legends, references — with main-text length and display-item budgets, and Results subheadings driving the single arc.
---

# Main-Text Writing & Structure (cell-writing)

## When to trigger

- Unsure how a Cell Article is structured.
- The main text is over length, or the Discussion repeats the Results.
- The Methods are written as a free-text section (Cell uses STAR Methods).
- Results wander instead of advancing the single narrative arc.

## Cell Article structure (in order)

1. **Summary** — single paragraph, ≤ ~150 words (`cell-summary`).
2. **Introduction** — ≈3–4 short paragraphs setting up the hypothesis (`cell-framing`).
3. **Results** — the bulk; organized by the arc, **with descriptive subheadings**.
4. **Discussion** — concise interpretation, limitations, significance; does **not** re-list results.
5. **STAR Methods** — Structured, Transparent, Accessible Reporting (separate skill, `cell-star-methods`).
6. **Figure legends** — each stands alone (title + per-panel + statistics).
7. **References** — author–date style (`cell-citation`).
8. **Supplemental information** — supporting figures/tables/videos.

> Cell does **not** use a free-text Methods section — methods live in **STAR Methods** with a Key Resources Table. This is non-negotiable for Cell Press.

## Length and display-item budget

- **Main text** ≈ **45,000 characters including spaces** (this typically counts Introduction, Results, Discussion, **and figure legends**, but not STAR Methods/references) — a working target; confirm the current cap.
- **Display items**: up to ~**7–8** figures/tables typical for a Cell Article; additional supporting items go to Supplemental Information.
- STAR Methods and references are outside the main-text character budget but have their own expectations.

> Numbers are working targets. The principle is fixed: Cell Articles are full stories but tightly written; supporting detail goes to Supplemental Information and STAR Methods.

## Results: subheadings that carry the arc

- Use **descriptive subheadings** that read as mini-claims ("Protein X is required for Y", not "Microscopy experiments").
- Each Results block: **claim sentence first**, then the evidence (figure callout + numbers + statistics), then the inference.
- Order by the **logic of the argument** (phenomenon → mechanism → causality → generality), not by chronology of experiments.
- Each subheading should map to one or two figures.

## Discussion discipline (concise)

- Interpret — don't recap. State what the mechanism means for the field.
- Address the **main alternative explanation** and how you exclude it.
- State **limitations** honestly (builds credibility and pre-empts reviewers).
- End on the broad significance / open question — not "more work is needed" filler.

## Length discipline tactics

- One idea per paragraph; lead with the claim.
- Move validation, controls, and orthogonal confirmations to Supplemental Information (cited as "Figure S3", "Table S1").
- Cut "In order to" → "To"; cut "It is worth noting that" and throat-clearing.
- Demote any result that doesn't serve the single arc.

## Cross-references

- Main figures: "Figure 1" (Cell spells out "Figure"); panels "Figure 1A".
- Supplemental: "Figure S1", "Table S1", "Video S1".
- STAR Methods sections are referenced by name (e.g., "see STAR Methods").

## Output format

```
【Sections present】 Summary / Intro / Results / Discussion / STAR Methods / legends / refs
【Methods format】 free-text (FIX → STAR Methods) / STAR Methods (ok)
【Main-text length】 ~N chars incl. legends → over/under ~45,000
【Display items】 N → within ~7–8? main vs Supplemental split
【Results subheadings】 claim-style + argument-ordered? yes/no
【Discussion】 interpretive (not a recap)? limitations stated? yes/no
【Next】 cell-figures
```

## Anti-patterns

- **Do not** write a free-text Methods section — Cell requires STAR Methods.
- **Do not** let the Discussion re-list the Results.
- **Do not** order Results chronologically when an argument order is clearer.
- **Do not** keep arc-irrelevant results in the main text to look comprehensive.

> Confirm exact length and item caps against current Cell Press author guidelines.

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 →