Article
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Implement valid Article structured data.
A skill your agent uses when choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps, figure caps, argument-ordered…
MITAuto-check passed
Install Sci Writing
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Science-Skills/skills/sci-writing .claude/skills/sci-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sci-writing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-writing into .claude/skills/sci-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Science-Skills/skills/sci-writing .agents/skills/sci-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sci-writing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-writing into .agents/skills/sci-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Science-Skills/skills/sci-writing .cursor/skills/sci-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sci-writing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-writing into .cursor/skills/sci-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Science-Skills/skills/sci-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Science-Skills/skills/sci-writing .gemini/skills/sci-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sci-writing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-writing into .gemini/skills/sci-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Science-Skills/skills/sci-writing .github/skills/sci-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sci-writing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-writing into .github/skills/sci-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Science-Skills/skills/sci-writing .opencode/skills/sci-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sci-writing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-writing into .opencode/skills/sci-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sci-writing- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 604 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps, figure caps, argument-ordered…
- Works in 4 steps: Establish the phenomenon (the headline… → Rule out the obvious alternative… → Show the mechanism / generality. → …
- Choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps
- SKILL.md covers When to trigger, Pick the format first, What goes where and Structure as argument, not…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sci Writing is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps, figure caps, argument-ordered Results, and deciding what belongs in the main text versus Supplementary Materials.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps
- Argument-ordered Results
- Deciding what belongs in the main text versus Supplementary Materials
Example prompts
- “/sci-writing”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Establish the phenomenon (the headline result).
- Rule out the obvious alternative explanations.
- Show the mechanism / generality.
- Demonstrate the broad implication.
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sci Writing loads about 1.3k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 604 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 604 words, ~1,272 tokens.
Download SKILL.mdSave it as
.claude/skills/sci-writing/SKILL.md (or your agent's skills folder).- name
- sci-writing
- description
- Use when choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps, figure caps, argument-ordered Results, and deciding what belongs in the main text versus 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:
- Establish the phenomenon (the headline result).
- Rule out the obvious alternative explanations.
- Show the mechanism / generality.
- 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.
Before/after: compressing to the Science register
Science prose earns its word budget sentence by sentence. Typical compressions:
| Draft (lab-report register) | Science register |
|---|---|
| "In order to investigate whether X affects Y, we performed a series of experiments in which…" | "To test whether X affects Y, we…" |
| "It is worth noting that the observed effect was statistically significant (p < 0.05)." | "The effect was robust (Δ = 12 ± 2%, P = 0.003, n = 14)." |
| "As can be seen in Fig. 2, there appears to be a trend toward increased activity." | "Activity increased threefold (Fig. 2)." |
| "These results may suggest a possible role for Z in this process." | "Z is required for this process (fig. S4)." |
The pattern: verbs over nominalizations, numbers over adjectives, one hedge maximum per claim, and every figure callout attached to a quantitative statement rather than "as shown in".
Show full SKILL.md (184 more words)Show less
What Science referees expect from the body text
- Each Results paragraph is checkable: a referee can match the claim sentence to a specific panel and a specific statistic without hunting.
- Alternative explanations are ruled out in the main text, even if the ruling-out data live in the SM ("this was not due to A or B; figs. S5 and S6").
- The final paragraph states scope and limits in one or two sentences — referees at a general-science weekly flag manuscripts whose conclusions quietly exceed the shown systems or conditions.
- No forward references to unpublished work as load-bearing evidence.
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-figuresAnti-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.
© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Science-Skills/skills/sci-writing of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sci Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sci Writing this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Articlethedaviddias/Front-End-Checklist | 74k | — | ~421 | Automated safety check: Pass | MIT | |
| Article Magazinenexu-io/open-design | 100k | — | ~495 | Automated safety check: Pass | Apache-2.0 | |
| Article Linksthedaviddias/Front-End-Checklist | 74k | — | ~425 | Automated safety check: Pass | MIT | |
| Article Writingaffaan-m/ECC | 276k | 3 repos | ~295 | Automated safety check: Pass | MIT | |
| Article Writingaffaan-m/ECC | 276k | — | ~385 | Automated safety check: Pass | MIT |
Similar skills
Article Magazine
nexu-io/open-design
Huashu / huashu-md-html-inspired magazine article layout for turning Markdown or notes into a polished long-form HTML essay.
Article Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Optimize article link density.
Article Writing
affaan-m/ECC
根据提供的示例或品牌指导，以独特的语气撰写文章、指南、博客帖子、教程、新闻简报等长篇内容。当用户需要超过一段的精致书面内容时使用，尤其是当语气一致性、结构和可信度至关重要时。
Article Writing
affaan-m/ECC
記事、ガイド、ブログ投稿、チュートリアル、ニュースレター号、その他の長文コンテンツを、提供された例またはブランドガイダンスから派生した独特の声で作成します。ユーザーが段落より長いポーランド済みの書き込みコンテンツを望む場合、特に声の一貫性、構造、および信頼性が重要な場合に使用します。
Article Illustrations
sickn33/agentic-awesome-skills
Generate hand-drawn 16:9 article illustrations with the Grav character IP, sparse annotations, and absurd but clear visual metaphors.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Sci Writing
What does Sci Writing do?
A skill your agent uses when choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps, figure caps, argument-ordered…. Sci Writing is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps, figure caps, argument-ordered Results, and deciding what belongs in the main text versus Supplementary Materials.
When should I use Sci Writing?
Sci Writing fits situations like: choosing the Science (AAAS) format (Research Article vs Report) and holding its length and structure budgets — main-text word caps; argument-ordered Results; deciding what belongs in the main text versus Supplementary Materials.
How do I install Sci Writing in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a claude-code`. Or copy the skill folder (Science-Skills/skills/sci-writing in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sci-writing in your project. Claude Code loads it when a task matches its description.
How do I install Sci Writing in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a codex`. Or copy the skill folder (Science-Skills/skills/sci-writing in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sci-writing in your project. Codex loads it when a task matches its description.
Can I use Sci Writing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sci-writing, .gemini/skills/sci-writing, .github/skills/sci-writing and .opencode/skills/sci-writing in your project.
What does Sci Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Sci Writing is instructions for the agent only.
Does Sci Writing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sci Writing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sci Writing use?
Sci Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sci Writing use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sci Writing?
Skills that share tags, products or a category with Sci Writing: Article (thedaviddias/Front-End-Checklist, 74k stars), Article Magazine (nexu-io/open-design, 100k stars), Article Links (thedaviddias/Front-End-Checklist, 74k stars) and Article Writing (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sci Writing?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.