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 Writing

ASecurity

Use to choose the Science format (Research Article vs Report) and hold its length and structure budgets — main text, word/figure caps, and what belongs in Supplementary Materials.

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-writing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sci Writing?

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

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

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

Download with Pro
Files
SKILL.md
---
name: sci-writing
description: Use to choose the Science format (Research Article vs Report) and hold its length and structure budgets — main text, word/figure caps, and what belongs in Supplementary Materials.
---

# Main-Text Writing & Format (sci-writing)

## When to trigger

- Unsure whether the work is a **Report** or a **Research Article**.
- The main text is over length, or Methods are bloating the body.
- The structure wanders (lab-notebook order instead of argument order).
- Co-authors keep adding paragraphs and the paper is creeping past budget.

## Pick the format first

| Format               | Use when                                                | Main-text target | Display items |
|----------------------|---------------------------------------------------------|------------------|---------------|
| **Report**           | A single, decisive advance told quickly                 | ~2,500 words     | ≤ 4 (figs+tables) |
| **Research Article** | A larger study needing more development/multiple results | ~4,500 words     | ≤ 6 (figs+tables) |

> Numbers are working targets; confirm current caps in the author guidelines. The principle is fixed: **Science main texts are short**, and most detail lives in Supplementary Materials.

## What goes where

- **Main text (Report)**: no section headers beyond the flow; combined results-and-discussion narrative. **Methods are NOT in the main text** — they go to Supplementary Materials (Materials and Methods).
- **Main text (Research Article)**: may use brief headers; still lean. Extended methods → Supplementary.
- **Supplementary Materials**: full Materials and Methods, supplementary figures/tables, supplementary text, captions, and additional data. This is where rigor lives without bloating the body.

## Structure as argument, not chronology

Order the Results by the **logic of the claim**, not the order experiments were run:

1. Establish the phenomenon (the headline result).
2. Rule out the obvious alternative explanations.
3. Show the mechanism / generality.
4. Demonstrate the broad implication.

Each Results paragraph: **claim sentence first**, then the evidence (figure callout + numbers), then the inference.

## Length discipline tactics

- One idea per paragraph; lead sentence is the claim.
- Move any sentence that a general reader can skip → Supplementary.
- Methods detail, validation, controls → Supplementary (cited as "fig. S3", "table S1").
- Cut "In order to" → "To"; cut "It is worth noting that"; cut throat-clearing.

## Reference and supplement cross-refs

- Main figures: "Fig. 1"; supplementary: "fig. S1" (lowercase f); tables: "Table 1" / "table S1".
- Supplementary Materials are cited in the main text and listed at the end.

## Output format

```
【Format】 Report (~2,500w / ≤4 items) or Research Article (~4,500w / ≤6 items)
【Current main-text word count】 N → over/under budget by M
【Methods location】 main text (FIX → move to SM) / Supplementary (ok)
【Results order】 argument-ordered? yes/no
【Items in main vs SM】 main: [...] / SM: [...]
【Next】 sci-figures
```

## Anti-patterns

- **Do not** keep a full Methods section in a Report's main text.
- **Do not** structure Results chronologically when a logical order is clearer.
- **Do not** treat the word cap as negotiable by shrinking font in figures — move content to SM instead.
- **Do not** add a standalone Discussion that repeats Results; integrate the interpretation.

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 →