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

Sci Workflow

ASecurity

Use when deciding which sci-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for Science (AAAS). Routes — it does not replace — the specialized skills.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Sci Workflow?

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

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

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

Download with Pro
Files
SKILL.md
---
name: sci-workflow
description: Use when deciding which sci-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for Science (AAAS). Routes — it does not replace — the specialized skills.
---

# Science Workflow Router (sci-workflow)

## Overview

This is the router. It does not replace any specialized skill. It tells you **which sci-* skill to use at the current stage** of a manuscript aimed at *Science* (AAAS).

Default assumption: unless the user states otherwise, the target is **Science** (the flagship research journal), not *Science Advances*, *Science Translational Medicine*, or other family titles. Family titles share house style but differ on scope and length — flag the difference if the user names one.

## When to trigger

- "What should I do next with this draft?"
- A draft arrives and you must diagnose the current bottleneck.
- The user is switching between experiments, writing, and revision and has lost the thread.
- Reviews arrive from Science and you need to switch into rebuttal mode.

## The single most important gate

Science rejects **most submissions without external review**. The editorial bar is **broad significance and general interest**, not technical correctness alone. So the first question is never "is the science right?" — it is **"does this clear the desk-reject filter for a general audience?"** Route to `sci-fit` first, always.

## Routing table

| Current symptom                                              | Next skill          |
|-------------------------------------------------------------|---------------------|
| Not sure the result is broad/general-interest enough        | `sci-fit`           |
| Result is significant but the "why it matters" is buried    | `sci-framing`       |
| No one-sentence summary; abstract reads narrow/jargon-heavy  | `sci-abstract`      |
| Unsure whether this is a Research Article or a Report; over length | `sci-writing` |
| Figures over panel/word budget; fonts/colors non-compliant  | `sci-figures`       |
| Stats under-reported; n/error bars/tests unclear; not reproducible | `sci-statistics` |
| No data/code/materials availability plan                    | `sci-data`          |
| References not in Science numbered style                     | `sci-citation`      |
| Need an editor-facing pitch for why Science should review it | `sci-cover-letter`  |
| About to submit; need a preflight checklist                 | `sci-submission`    |
| Received reviews / an R&R decision                           | `sci-rebuttal`      |

## Default order

1. `sci-fit` — clear the broad-significance / general-interest bar first
2. `sci-framing` — lock the conceptual advance and the "why now"
3. `sci-writing` — choose format (Research Article vs Report) and hold length
4. `sci-figures` — finalize display items within budget
5. `sci-statistics` — rigor & reproducibility reporting
6. `sci-data` — data / code / materials availability
7. `sci-abstract` — abstract + one-sentence summary (late polish)
8. `sci-citation` — reference style pass
9. `sci-cover-letter` — significance-forward editor pitch
10. `sci-submission` — preflight
11. `sci-rebuttal` — after review

> `sci-abstract` and `sci-citation` are **late-stage polish**. Do not perfect the abstract before the significance and format are settled.

## Decision shortcuts

- "A specialist would care, but would a geneticist *and* a physicist?" → `sci-fit`
- "My intro starts with background, not with the advance" → `sci-framing`
- "My Report main text is 4,000 words" → `sci-writing` (Reports target ~2,500)
- "Methods are in the main text" → `sci-writing` (Reports push Methods to Supplementary)
- "Bar chart with no individual data points / no n" → `sci-statistics` + `sci-figures`
- "No accession numbers / no code repo" → `sci-data`
- "Editor needs to see the hook in 3 sentences" → `sci-cover-letter`

## How Science differs from its siblings and from Nature

- **Science (Reports / Research Articles)** vs **Science Advances** (open-access, broader acceptance, longer): if the work is solid but not top-1% general interest, Advances may be the realistic target — say so.
- **Science vs Nature**: both gate on broad significance, but Science requires a **one-sentence summary** and uses a **single numbered reference list with full author names**; Nature uses a different reference and summary-paragraph convention. Do not copy a Nature-formatted manuscript over without a style pass (`sci-citation`, `sci-abstract`).

## Anti-patterns

- **Do not** skip `sci-fit` and start polishing prose — the modal outcome is desk rejection.
- **Do not** let `sci-figures` beautify panels before the format/length decision in `sci-writing`.
- **Do not** generate a rebuttal before the main text is actually revised.

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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".

1066601 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', ...

686011 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.

651 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 →