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 Citation

ASecurity

Use to convert references to Cell Press author–date style — in-text "(Smith et al., 2021)", an alphabetical reference list by first author with full author lists, journal names spelled out. This is the OPPOSITE of Science's numbered-by-appearance style.

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Cell Citation?

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

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

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

Download with Pro
Files
SKILL.md
---
name: cell-citation
description: Use to convert references to Cell Press author–date style — in-text "(Smith et al., 2021)", an alphabetical reference list by first author with full author lists, journal names spelled out. This is the OPPOSITE of Science's numbered-by-appearance style.
---

# Reference Style (cell-citation)

## When to trigger

- References are numbered by appearance (Science/Nature style) and must become author–date.
- The reference list is ordered by citation order instead of alphabetically.
- Author lists are truncated with "et al." in the bibliography.
- You are porting a manuscript from a numbered-style journal to Cell.

## Cell Press citation mechanics

- **In-text: author–date.** Parenthetical "(Smith et al., 2021)" or narrative "Smith et al. (2021) showed…". Multiple: "(Smith et al., 2021; Lee and Cho, 2020)". Two authors: "(Lee and Cho, 2020)". Same author/year: "(Smith et al., 2021a, 2021b)".
- **Reference list: alphabetical by first author's surname** — NOT numbered, NOT by order of appearance.
- **Full author lists** in the bibliography (Cell Press does not truncate to "et al." for typical author counts; confirm the cutoff).
- **Journal names** per Cell Press style (often spelled out / standard form); include year, volume, and pages/article number.
- A **single reference list** covering main text and STAR Methods.

> This is the **opposite** of *Science*, which uses **numbered references in order of appearance**. If you are transferring from Science (or Nature's numbered convention), you must **re-cite in author–date and re-sort alphabetically** — a mechanical but non-trivial conversion.

## Reference formats (shape)

- **Journal article:**
  `Author, A.B., Author, C.D., and Author, E.F. (2021). Title of the article. Journal Name Volume, pages.`
- **Book:**
  `Author, A.B. (2020). Book Title, edition (Publisher).`
- **Chapter:**
  `Author, A.B. (2020). Chapter title. In Book Title, C.D. Editor, ed. (Publisher), pp. xx–yy.`
- **Dataset/code:** cite with repository, accession/DOI, and year (consistent with `cell-data`).
- **Preprint:** include the server (e.g., bioRxiv) and DOI.

> Surname precedes initials in the list; "and" before the final author; year in parentheses after the author list. Use a Cell Press CSL/style file to enforce this.

## Common conversion fixes (numbered → Cell author–date)

| From (Science/numbered)            | To (Cell author–date)                          |
|------------------------------------|------------------------------------------------|
| "*(12)*" in text                   | "(Smith et al., 2021)"                          |
| List ordered by appearance         | list **alphabetical** by first author           |
| "A. B. Author, …" (initials first) | "Author, A.B., …" (surname first)               |
| Truncated "et al." in biblio       | full author list                                |
| Merged notes-and-references list   | references only; move notes to text/footnotes   |
| Numbers resolve to list positions  | every in-text (Author, year) resolves to an entry |

## Tooling

- Use Zotero/EndNote with the **Cell Press** CSL/style; do a final manual pass on author-list completeness and journal-name form (managers often truncate).
- Verify every in-text "(Author, year)" has a matching alphabetical entry, and that a/b suffixes disambiguate same-author/year citations.

## Output format

```
【Style detected】 numbered-by-appearance / Nature / other → Cell author–date
【In-text】 author–date "(Smith et al., 2021)"? yes/no
【List order】 alphabetical by first author? yes/no
【Author lists】 full (not et al.) in biblio? surname-first? yes/no
【Same-author/year】 a/b suffixes applied? yes/no
【Unresolved citations】 [...]
【Next】 cell-submission
```

## Anti-patterns

- **Do not** leave numbered "(12)" citations anywhere in a Cell manuscript.
- **Do not** order the reference list by appearance — Cell is **alphabetical**.
- **Do not** truncate author lists with "et al." in the bibliography.
- **Do not** copy Science's numbered convention by reflex — Cell is author–date.

> Confirm the exact author–date format, author-list cutoff, and journal-name style 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 →