Write rigorous scientific manuscripts, research papers, grant proposals, and literature reviews. Use when drafting or revising any part of a scientific document including abstracts, introductions, methods, results, and discussions. Applies IMRAD structure, citation styles (APA/AMA/Vancouver/IEEE), reporting guidelines (CONSORT/STROBE/PRISMA), and publication standards. Triggers on requests to write research papers, journal articles, scientific reports, academic manuscripts, grant applications, or improve scientific prose.
/plugin marketplace add yibeichan/claude-skills/plugin install yibeichan-claude-skills@yibeichan/claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/citation_styles.mdreferences/field_conventions.mdreferences/figures_tables.mdreferences/reporting_guidelines.mdWrite publication-ready scientific manuscripts using established academic conventions and evidence-based practices.
Every substantive claim requires support from peer-reviewed literature. Use appropriate hedging: "suggests" for correlational evidence, "demonstrates" for causal evidence. Never assert without citation or data support.
Scientific writing prioritizes precision. Use domain-specific terminology correctly, define terms on first use, prefer active voice in methods, and avoid vague qualifiers ("very significant" → "statistically significant, p < 0.001").
Methods must enable replication: include all parameters, software versions, statistical tests, sample sizes, inclusion/exclusion criteria, effect sizes alongside p-values, and relevant reporting guideline compliance.
Stage 1: Outline with Evidence Create structured outlines with bullet points marking main arguments, key citations, data points, and logical flow. This is scaffolding—not the final manuscript.
Stage 2: Convert to Prose Transform outlines into complete paragraphs with proper transitions, integrated citations, and logical sentence flow. Final manuscripts contain NO bullet points except in specific Methods subsections (inclusion criteria, materials lists).
Write as flowing paragraph(s), NOT labeled sections. Cover: (1) context/problem, (2) methods summary, (3) key findings with statistics, (4) significance. Typically 150-300 words. Only use structured format if journal explicitly requires it.
Example structure:
[Context sentence establishing importance]. [Gap or problem addressed].
[Study objective]. [Methods: design, N, key measures]. [Primary result with
statistics]. [Secondary findings]. [Conclusion and implications].
Follow funnel structure:
Standard subsections:
Include power analysis. Report all conditions. Enable replication.
Structure: (1) preliminary analyses, (2) primary hypotheses, (3) secondary/exploratory (labeled).
Report consistently:
No interpretation here—save for Discussion.
Structure: (1) summary without statistics, (2) interpretation in literature context, (3) limitations, (4) implications, (5) future directions, (6) conclusion.
Address alternative explanations. Avoid overclaiming.
For detailed citation formatting by style, see references/citation_styles.md.
Match guideline to study type:
For checklists and details, see references/reporting_guidelines.md.
| Section | Tense |
|---|---|
| Introduction (established facts) | Present |
| Introduction (prior studies) | Past |
| Methods | Past |
| Results | Past |
| Discussion (your findings) | Past |
| Discussion (interpretations) | Present |
| Conclusions | Present |
| Error | Correction |
|---|---|
| "Data shows..." | "Data show..." (plural) |
| "Proves that..." | "Suggests/demonstrates that..." |
| "Significant" (colloquial) | "Substantial" or "statistically significant" |
| "In order to" | "To" |
| "Due to the fact that" | "Because" |
For comprehensive field conventions, see references/field_conventions.md.
For detailed guidance, see references/figures_tables.md.
Stage 1: Planning
Stage 2: Drafting
Stage 3: Revision
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.