Markdown to HTML Report
MegaSuperKitty/WeClaw
Drafts a report in Markdown with numbered inline citations and a references section, then renders it to a styled HTML file through a Jinja2 template on Windows.
A skill your agent uses when writing the two front-matter artifacts Science (AAAS) demands — the one-sentence summary for the table of contents and the ≤125-word single-paragraph abstract — both…
Install Sci Abstract
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-abstract -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-abstract --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-abstract .claude/skills/sci-abstract && 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-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-abstract into .claude/skills/sci-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-abstract", 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-abstractType 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-abstract -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-abstract --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-abstract .agents/skills/sci-abstract && 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-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-abstract into .agents/skills/sci-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-abstract", 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-abstract -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-abstract --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-abstract .cursor/skills/sci-abstract && 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-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-abstract into .cursor/skills/sci-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-abstract", 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-abstract--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-abstract -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sci-abstract --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-abstract .gemini/skills/sci-abstract && 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-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-abstract into .gemini/skills/sci-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-abstract", 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-abstractInstalls 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-abstract -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-abstract .github/skills/sci-abstract && 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-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-abstract into .github/skills/sci-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-abstract", 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-abstract -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-abstract --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-abstract .opencode/skills/sci-abstract && 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-abstract" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Science-Skills/skills/sci-abstract into .opencode/skills/sci-abstract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sci-abstract", 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-abstract- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 815 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing the two front-matter artifacts Science (AAAS) demands — the one-sentence summary for the table of contents and the ≤125-word single-paragraph abstract — both…
- Works in 2 steps: One-sentence summary (≤ ~125 characters) → Abstract (≈ 100–125 words, unstructured…
- Tasks that involve Markdown
- SKILL.md covers When to trigger, Two distinct artifacts Science…, Hard constraints and Jargon blacklist (rewrite on…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sci Abstract is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the two front-matter artifacts Science (AAAS) demands — the one-sentence summary for the table of contents and the ≤125-word single-paragraph abstract — both readable by any scientist and both leading with the quantified advance rather than the method. Late-stage polish skill for the flagship AAAS weekly.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Markdown. 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
- Tasks that involve Markdown
Example prompts
- “/sci-abstract”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
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 Abstract loads about 1.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 815 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). 815 words, ~1,657 tokens.
Download SKILL.mdSave it as
.claude/skills/sci-abstract/SKILL.md (or your agent's skills folder).- name
- sci-abstract
- description
- Use when writing the two front-matter artifacts Science (AAAS) demands — the one-sentence summary for the table of contents and the ≤125-word single-paragraph abstract — both readable by any scientist and both leading with the quantified advance rather than the method. Late-stage polish skill for the flagship AAAS weekly.
Abstract & One-Sentence Summary (sci-abstract)
When to trigger
- Significance, framing, and format are settled (do this late).
- The abstract reads like a method recap with no result.
- There is no one-sentence summary, or it restates the title.
- The abstract exceeds ~125 words or is dense with jargon/acronyms.
Two distinct artifacts Science requires
1. One-sentence summary (≤ ~125 characters)
A single declarative sentence for the table of contents and editors. It is not the title and not the first line of the abstract.
- States the finding and its general point.
- No undefined acronyms; readable by any scientist.
- Active voice. Example shape: "A single mutation rewires metabolism, explaining cold tolerance across insects."
2. Abstract (≈ 100–125 words, unstructured prose)
Science abstracts are short, single-paragraph, no subheadings. Target the educated general scientist, not the subfield.
Recommended five-move structure (no labels in the text):
- Context / stakes (1 sentence) — the broad problem.
- Gap / question (1 sentence) — what was unknown.
- What we did (1 sentence) — approach, in plain terms.
- Key result, quantified (1–2 sentences) — the advance, with numbers.
- Implication (1 sentence) — why a broad community should care.
Hard constraints
- ≤ ~125 words (check the current author guidelines for the exact cap; treat 125 as the ceiling).
- No subheadings, no citations, no figure/table references in the abstract.
- Define any acronym on first use, or avoid it.
- At least one quantified result — not "significantly increased" but "increased 2.4-fold (P < 0.001)".
- First sentence is comprehensible to a scientist outside the field.
Jargon blacklist (rewrite on sight)
- "Herein we report…", "Importantly,", "Interestingly,", "Notably,"
- Strings of ≥2 undefined acronyms in one sentence.
- "elucidate", "delineate", "interrogate", "leverage" as filler verbs.
- Hedging stacks: "may potentially suggest that it could…".
Quantification check
Every claim of effect must carry a number somewhere in the paper, and the headline effect should be in the abstract: magnitude + unit + uncertainty (CI or P). If the abstract has zero numbers, it is not finished.
What the editorial board reads first
Because Science triages most submissions in-house before any referee sees them, your one-sentence summary and abstract are frequently the only prose a professional editor reads before deciding to read further. Calibrate to that reality:
| Editor's silent question | Where they look | What kills it |
|---|---|---|
| "Would our general readership care?" | one-sentence summary | a subfield claim only specialists parse |
| "Is there a result, or just an approach?" | abstract sentences 3–4 | method recap with no quantified finding |
| "Is this overstated?" | abstract last sentence | an implication asserted, not demonstrated |
| "Can I send this summary to a referee verbatim?" | the whole summary | undefined acronyms, hedging stacks |
The abstract is one unstructured paragraph — unlike a structured clinical abstract (Background/Methods/Results/Conclusions). Do not import a NEJM/JAMA structured-abstract template; Science runs continuous prose with no labels.
Show full SKILL.md (367 more words)Show less
Worked micro-example (illustrative)
A team finds that a single gut bacterium's enzyme degrades a common drug, explaining why some patients respond and others do not. Walk the moves (numbers illustrative only):
- One-sentence summary (≈110 chars): "A single gut-microbial enzyme inactivates a widely used drug, explaining variable patient response."
- Abstract (≈120 words, prose): Stake — drug response varies unpredictably between patients. Gap — the gut microbiome was suspected but no mechanism was known. Approach — we screened 412 isolates and reconstituted the activity in vitro. Result — one enzyme reduced active-drug levels by 73% (95% CI 65–80%; P < 0.001), and its abundance predicted response in a 96-patient cohort (AUC 0.84). Implication — microbial enzymology may be a general, modifiable axis of drug variability.
Notice: the headline number (73%, CI, P) sits in the abstract, not buried in a figure; the last sentence reaches a broad audience (pharmacology, microbiology, clinical medicine) without claiming proof of causation in humans.
Referee and editor pushback patterns
| Pushback you will hear | The Science-specific fix |
|---|---|
| "The summary just restates the title." | Make it state the consequence, not the topic — the lesson a non-specialist takes away. |
| "I read the abstract and still don't know the result." | Put the quantified headline (magnitude + uncertainty) in sentences 4–5; delete one context sentence to fit. |
| "Reads like an abstract for a specialist journal." | Replace the field-internal opener with the broad stake; cut acronym chains. |
| "The last line over-claims." | Hedge to what the data show; "may be a general axis" not "is the cause" — confirm the claim survives sci-fit. |
Calibration anchors (confirm against current author guidelines)
- One-sentence summary: target ≤ ~125 characters; it is a distinct required field, not the first abstract line.
- Abstract: target ≤ ~125 words, single paragraph, no subheadings, no citations, no figure references.
- Exactly one paragraph — the convention is firm even as the word ceiling may shift; verify the current cap.
- At least one quantified headline effect with uncertainty; zero-number abstracts are unfinished.
Output format
【One-sentence summary】 "..." (char count: N ≤ 125)
【Abstract】 single paragraph (word count: N ≤ 125)
【Five moves present?】 context / gap / approach / quantified result / implication
【Quantified headline result?】 yes/no + the number
【Jargon hits removed】 [...]
【Next】 sci-citationAnti-patterns
- Do not make the one-sentence summary a paraphrase of the title.
- Do not open the abstract with method or organism; open with the stake.
- Do not end on "further work is needed" — end on the implication.
- Do not pad to sound comprehensive; the cap is a feature.
© 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-abstract of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sci Abstract 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 Abstract this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Markdown to HTML ReportMegaSuperKitty/WeClaw | 370 | — | ~456 | Automated safety check: Pass | MIT | |
| Paper Interpretationdigoal/blog | 8.6k | — | ~1.5k | Automated safety check: Pass | GPL-2.0 | |
| Suikonwiizo/suiko | 114 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Deepxiv Baseline TableDeepXiv/deepxiv_sdk | 804 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Mindmap Renderai4s-research/ai4s-skills | 237 | 1 repos | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
Suiko
nwiizo/suiko
日本語文書のAI由来の均一さ、翻訳調、不自然さ、論旨、読解負荷を、決定的なRust CLIと目視で診断し、依頼に応じて書く・直す。日本語の学術論文・研究報告では、中心命題、用語、論証、DOCX/PDF納品を監査契約で確認する。Use when the user explicitly mentions suiko, asks whether Japanese text looks…
Deepxiv Baseline Table
DeepXiv/deepxiv_sdk
Build a markdown baseline table for a research topic using deepxiv search, brief, head, and experiment-section reads, extracting paper title, URL, open-source status, datasets, benchmark scores, and…
Mindmap Render
ai4s-research/ai4s-skills
Generate beautiful, high-resolution mindmaps from Markdown unordered lists.
Writing Core
Norman-bury/research-writing-skill
A skill your agent uses when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks
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…
Related
Categories
Questions about Sci Abstract
What does Sci Abstract do?
A skill your agent uses when writing the two front-matter artifacts Science (AAAS) demands — the one-sentence summary for the table of contents and the ≤125-word single-paragraph abstract — both…. Sci Abstract is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the two front-matter artifacts Science (AAAS) demands — the one-sentence summary for the table of contents and the ≤125-word single-paragraph abstract — both readable by any scientist and both leading with the quantified advance rather than the method.
When should I use Sci Abstract?
Sci Abstract fits situations like: tasks that involve Markdown.
How do I install Sci Abstract in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-abstract -a claude-code`. Or copy the skill folder (Science-Skills/skills/sci-abstract in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sci-abstract in your project. Claude Code loads it when a task matches its description.
How do I install Sci Abstract in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sci-abstract -a codex`. Or copy the skill folder (Science-Skills/skills/sci-abstract in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sci-abstract in your project. Codex loads it when a task matches its description.
Can I use Sci Abstract 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-abstract -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-abstract, .gemini/skills/sci-abstract, .github/skills/sci-abstract and .opencode/skills/sci-abstract in your project.
What does Sci Abstract need to run?
SKILL.md names no scripts, command-line tools or credentials: Sci Abstract is instructions for the agent only.
Does Sci Abstract 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 Abstract 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 Abstract use?
Sci Abstract 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 Abstract use?
About 1.7k tokens (SKILL.md is roughly 6.6k 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 Abstract?
Skills that share tags, products or a category with Sci Abstract: Markdown to HTML Report (MegaSuperKitty/WeClaw, 370 stars), Paper Interpretation (digoal/blog, 8.6k stars), Suiko (nwiizo/suiko, 114 stars) and Deepxiv Baseline Table (DeepXiv/deepxiv_sdk, 804 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sci Abstract?
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.