scientific-writing

K-Dense-AI/scientific-agent-skills · updated Jun 4, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill scientific-writing
0 commentsdiscussion
summary

### Scientific Writing

  • name: "scientific-writing"
  • description: "Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research..."
  • allowed-tools: "Read Write Edit Bash"
skill.md
name
scientific-writing
description
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
allowed-tools
Read Write Edit Bash
license
MIT license
metadata
version: "1.0" skill-author: K-Dense Inc.

Scientific Writing

Overview

This is the core skill for the deep research and writing tool—combining AI-driven deep research with well-formatted written outputs. Every document produced is backed by comprehensive literature search and verified citations through the research-lookup skill.

Scientific writing is a process for communicating research with precision and clarity. Write manuscripts using IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, and reporting guidelines (CONSORT/STROBE/PRISMA). Apply this skill for research papers and journal submissions.

Critical Principle: Always write in full paragraphs with flowing prose. Never submit bullet points in the final manuscript. Use a two-stage process: first create section outlines with key points using research-lookup, then convert those outlines into complete paragraphs.

When to Use This Skill

This skill should be used when:

  • Writing or revising any section of a scientific manuscript (abstract, introduction, methods, results, discussion)
  • Structuring a research paper using IMRAD or other standard formats
  • Formatting citations and references in specific styles (APA, AMA, Vancouver, Chicago, IEEE)
  • Creating, formatting, or improving figures, tables, and data visualizations
  • Applying study-specific reporting guidelines (CONSORT for trials, STROBE for observational studies, PRISMA for reviews)
  • Drafting abstracts that meet journal requirements (structured or unstructured)
  • Preparing manuscripts for submission to specific journals
  • Improving writing clarity, conciseness, and precision
  • Ensuring proper use of field-specific terminology and nomenclature
  • Addressing reviewer comments and revising manuscripts

Visual Enhancement with Scientific Schematics

⚠️ MANDATORY: Every scientific paper MUST include a graphical abstract plus 1-2 additional AI-generated figures using the scientific-schematics skill.

This is not optional. Scientific papers without visual elements are incomplete. Before finalizing any document:

  1. ALWAYS generate a graphical abstract as the first visual element
  2. Generate at minimum ONE additional schematic or diagram using scientific-schematics
  3. Prefer 3-4 total figures for comprehensive papers (graphical abstract + methods flowchart + results visualization + conceptual diagram)

Graphical Abstract (REQUIRED)

Every scientific writeup MUST include a graphical abstract. This is a visual summary of your paper that:

  • Appears before or immediately after the text abstract
  • Captures the entire paper's key message in one image
  • Is suitable for journal table of contents display
  • Uses landscape orientation (typically 1200x600px)

Generate the graphical abstract FIRST:

python scripts/generate_schematic.py "Graphical abstract for [paper title]: [brief description showing workflow from input → methods → key findings → conclusions]" -o figures/graphical_abstract.png

Graphical Abstract Requirements:

  • Content: Visual summary showing workflow, key methods, main findings, and conclusions
  • Style: Clean, professional, suitable for journal TOC
  • Elements: Include 3-5 key steps/concepts with connecting arrows or flow
  • Text: Minimal labels, large readable fonts
  • Log: [HH:MM:SS] GENERATED: Graphical abstract for paper summary

Additional Figures (GENERATE EXTENSIVELY)

⚠️ CRITICAL: Use BOTH scientific-schematics AND generate-image EXTENSIVELY throughout all documents.

Every document should be richly illustrated. Generate figures liberally - when in doubt, add a visual.

MINIMUM Figure Requirements:

Document TypeMinimumRecommended
Research Papers56-8
Literature Reviews45-7
Market Research2025-30
Presentations1/slide1-2/slide
Posters68-10
Grants45-7
Clinical Reports34-6

Use scientific-schematics EXTENSIVELY for technical diagrams:

python scripts/generate_schematic.py "your diagram description" -o figures/output.png
  • Study design and methodology flowcharts (CONSORT, PRISMA, STROBE)
  • Conceptual framework diagrams
  • Experimental workflow illustrations
  • Data analysis pipeline diagrams
  • Biological pathway or mechanism diagrams
  • System architecture visualizations
  • Neural network architectures
  • Decision trees, algorithm flowcharts
  • Comparison matrices, timeline diagrams
  • Any technical concept that benefits from schematic visualization

Use generate-image EXTENSIVELY for visual content:

python scripts/generate_image.py "your image description" -o figures/output.png
  • Photorealistic illustrations of concepts
  • Medical/anatomical illustrations
  • Environmental/ecological scenes
  • Equipment and lab setup visualizations
  • Artistic visualizations, infographics
  • Cover images, header graphics
  • Product mockups, prototype visualizations
  • Any visual that enhances understanding or engagement

The AI will automatically:

  • Create publication-quality images with proper formatting
  • Review and refine through multiple iterations
  • Ensure accessibility (colorblind-friendly, high contrast)
  • Save outputs in the figures/ directory

When in Doubt, Generate a Figure:

  • Complex concept → generate a schematic
  • Data discussion → generate a visualization
  • Process description → generate a flowchart
  • Comparison → generate a comparison diagram
  • Reader benefit → generate a visual

For detailed guidance, refer to the scientific-schematics and generate-image skill documentation.


Core Capabilities

1. Manuscript Structure and Organization

IMRAD Format: Guide papers through the standard Introduction, Methods, Results, And Discussion structure used across most scientific disciplines. This includes:

  • Introduction: Establish research context, identify gaps, state objectives
  • Methods: Detail study design, populations, procedures, and analysis approaches
  • Results: Present findings objectively without interpretation
  • Discussion: Interpret results, acknowledge limitations, propose future directions

For detailed guidance on IMRAD structure, refer to references/imrad_structure.md.

Alternative Structures: Support discipline-specific formats including:

  • Review articles (narrative, systematic, scoping)
  • Case reports and case series
  • Meta-analyses and pooled analyses
  • Theoretical/modeling papers
  • Methods papers and protocols

2. Section-Specific Writing Guidance

Abstract Composition: Craft concise, standalone summaries (100-250 words) that capture the paper's purpose, methods, results, and conclusions. Support both structured abstracts (with labeled sections) and unstructured single-paragraph formats.

Introduction Development: Build compelling introductions that:

  • Establish the research problem's importance
  • Review relevant literature systematically
  • Identify knowledge gaps or controversies
  • State clear research questions or hypotheses
  • Explain the study's novelty and significance

Methods Documentation: Ensure reproducibility through:

  • Detailed participant/sample descriptions
  • Clear procedural documentation
  • Statistical methods with justification
  • Equipment and materials specifications
  • Ethical approval and consent statements

Results Presentation: Present findings with:

  • Logical flow from primary to secondary outcomes
  • Integration with figures and tables
  • Statistical significance with effect sizes
  • Objective reporting without interpretation

Discussion Construction: Synthesize findings by:

  • Relating results to research questions
  • Comparing with existing literature
  • Acknowledging limitations honestly
  • Proposing mechanistic explanations
  • Suggesting practical implications and future research

3. Citation and Reference Management

Apply citation styles correctly across disciplines. For comprehensive style guides, refer to references/citation_styles.md.

Major Citation Styles:

  • AMA (American Medical Association): Numbered superscript citations, common in medicine
  • Vancouver: Numbered citations in square brackets, biomedical standard
  • APA (American Psychological Association): Author-date in-text citations, common in social sciences
  • Chicago: Notes-bibliography or author-date, humanities and sciences
  • IEEE: Numbered square brackets, engineering and computer science

Best Practices:

  • Cite primary sources when possible
  • Include recent literature (last 5-10 years for active fields)
  • Balance citation distribution across introduction and discussion
  • Verify all citations against original sources
  • Use reference management software (Zotero, Mendeley, EndNote)

4. Figures and Tables

Create effective data visualizations that enhance comprehension. For detailed best practices, refer to references/figures_tables.md.

When to Use Tables vs. Figures:

  • Tables: Precise numerical data, complex datasets, multiple variables requiring exact values
  • Figures: Trends, patterns, relationships, comparisons best understood visually

Design Principles:

  • Make each table/figure self-explanatory with complete captions
  • Use consistent formatting and terminology across all display items
  • Label all axes, columns, and rows with units
  • Include sample sizes (n) and statistical annotations
  • Follow the "one table/figure per 1000 words" guideline
  • Avoid duplicating information between text, tables, and figures

Common Figure Types:

  • Bar graphs: Comparing discrete categories
  • Line graphs: Showing trends over time
  • Scatterplots: Displaying correlations
  • Box plots: Showing distributions and outliers
  • Heatmaps: Visualizing matrices and patterns

5. Reporting Guidelines by Study Type

Ensure completeness and transparency by following established reporting standards. For comprehensive guideline details, refer to references/reporting_guidelines.md.

Key Guidelines:

  • CONSORT: Randomized controlled trials
  • STROBE: Observational studies (cohort, case-control, cross-sectional)
  • PRISMA: Systematic reviews and meta-analyses
  • STARD: Diagnostic accuracy studies
  • TRIPOD: Prediction model studies
  • ARRIVE: Animal research
  • CARE: Case reports
  • SQUIRE: Quality improvement studies
  • SPIRIT: Study protocols for clinical trials
  • CHEERS: Economic evaluations

Each guideline provides checklists ensuring all critical methodological elements are reported.

6. Writing Principles and Style

Apply fundamental scientific writing principles. For detailed guidance, refer to references/writing_principles.md.

Clarity:

  • Use precise, unambiguous language
  • Define technical terms and abbreviations at first use
  • Maintain logical flow within and between paragraphs
  • Use active voice when appropriate for clarity

Conciseness:

  • Eliminate redundant words and phrases
  • Favor shorter sentences (15-20 words average)
  • Remove unnecessary qualifiers
  • Respect word limits strictly

Accuracy:

  • Report exact values with appropriate precision
  • Use consistent terminology throughout
  • Distinguish between observations and interpretations
  • Acknowledge uncertainty appropriately

Objectivity:

  • Present results without bias
  • Avoid overstating findings or implications
  • Acknowledge conflicting evidence
  • Maintain professional, neutral tone

7. Writing Process: From Outline to Full Paragraphs

CRITICAL: Always write in full paragraphs, never submit bullet points in scientific papers.

Scientific papers must be written in complete, flowing prose. Use this two-stage approach for effective writing:

Stage 1: Create Section Outlines with Key Points

When starting a new section:

  1. Use the research-lookup skill to gather relevant literature and data
  2. Create a structured outline with bullet points marking:
    • Main arguments or findings to present
    • Key studies to cite
    • Data points and statistics to include
    • Logical flow and organization
  3. These bullet points serve as scaffolding—they are NOT the final manuscript

Example outline (Introduction section):

- Background: AI in drug discovery gaining traction
  * Cite recent reviews (Smith 2023, Jones 2024)
  * Traditional methods are slow and expensive
- Gap: Limited application to rare diseases
  * Only 2 prior studies (Lee 2022, Chen 2023)
  * Small datasets remain a challenge
- Our approach: Transfer learning from common diseases
  * Novel architecture combining X and Y
- Study objectives: Validate on 3 rare disease datasets

Stage 2: Convert Key Points to Full Paragraphs

Once the outline is complete, expand each bullet point into proper prose:

  1. Transform bullet points into complete sentences with subjects, verbs, and objects
  2. Add transitions between sentences and ideas (however, moreover, in contrast, subsequently)
  3. Integrate citations naturally within sentences, not as lists
  4. Expand with context and explanation that bullet points omit
  5. Ensure logical flow from one sentence to the next within each paragraph
  6. Vary sentence structure to maintain reader engagement

Example conversion to prose:

Artificial intelligence approaches have gained significant traction in drug discovery 
pipelines over the past decade (Smith, 2023; Jones, 2024). While these computational 
methods show promise for accelerating the identification of therapeutic candidates, 
traditional experimental approaches remain slow and resource-intensive, often requiring 
years of laboratory work and substantial financial investment. However, the application 
of AI to rare diseases has been limited, with only two prior studies demonstrating 
proof-of-concept results (Lee, 2022; Chen, 2023). The primary obstacle has been the 
scarcity of training data for conditions affecting small patient populations. 

To address this challenge, we developed a transfer learning approach that leverages 
knowledge from well-characterized common diseases to predict therapeutic targets for 
rare conditions. Our novel neural architecture combines convolutional layers for 
molecular feature extraction with attention mechanisms for protein-ligand interaction 
modeling. The objective of this study was to validate our approach across three 
independent rare disease datasets, assessing both predictive accuracy and biological 
interpretability of the results.

Key Differences Between Outlines and Final Text:

Outline (Planning Stage)Final Manuscript
Bullet points and fragmentsComplete sentences and paragraphs
Telegraphic notesFull explanations with context
List of citationsCitations integrated into prose
Abbreviated ideasDeveloped arguments with transitions
For your eyes onlyFor publication and peer review

Common Mistakes to Avoid:

  • Never leave bullet points in the final manuscript
  • Never submit lists where paragraphs should be
  • Don't use numbered or bulleted lists in Results or Discussion sections (except for specific cases like study hypotheses or inclusion criteria)
  • Don't write sentence fragments or incomplete thoughts
  • Do use occasional lists only in Methods (e.g., inclusion/exclusion criteria, materials lists)
  • Do ensure every section flows as connected prose
  • Do read paragraphs aloud to check for natural flow

When Lists ARE Acceptable (Limited Cases):

Lists may appear in scientific papers only in specific contexts:

  • Methods: Inclusion/exclusion criteria, materials and reagents, participant characteristics
  • Supplementary Materials: Extended protocols, equipment lists, detailed parameters
  • Never in: Abstract, Introduction, Results, Discussion, Conclusions

Abstract Format Rule:

  • NEVER use labeled sections (Background:, Methods:, Results:, Conclusions:)
  • ALWAYS write as flowing paragraph(s) with natural transitions
  • Exception: Only use structured format if journal explicitly requires it in author guidelines

Integration with Research Lookup:

The research-lookup skill is essential for Stage 1 (creating outlines):

  1. Search for relevant papers using research-lookup
  2. Extract key findings, methods, and data
  3. Organize findings as bullet points in your outline
  4. Then convert the outline to full paragraphs in Stage 2

This two-stage process ensures you:

  • Gather and organize information systematically
  • Create logical structure before writing
  • Produce polished, publication-ready prose
  • Maintain focus on the narrative flow

8. Professional Report Formatting (Non-Journal Documents)

For research reports, technical reports, white papers, and other professional documents that are NOT journal manuscripts, use the scientific_report.sty LaTeX style package for a polished, professional appearance.

When to Use Professional Report Formatting:

  • Research reports and technical reports
  • White papers and policy briefs
  • Grant reports and progress reports
  • Industry reports and technical documentation
  • Internal research summaries
  • Feasibility studies and project deliverables

When NOT to Use (Use Venue-Specific Formatting Instead):

  • Journal manuscripts → Use venue-templates skill
  • Conference papers → Use venue-templates skill
  • Academic theses → Use institutional templates

The scientific_report.sty Style Package Provides:

FeatureDescription
TypographyHelvetica font family for modern, professional appearance
Color SchemeProfessional blues, greens, and accent colors
Box EnvironmentsColored boxes for key findings, methods, recommendations, limitations
TablesAlternating row colors, professional headers
FiguresConsistent caption formatting
Scientific CommandsShortcuts for p-values, effect sizes, confidence intervals

Box Environments for Content Organization:

% Key findings (blue) - for major discoveries
\begin{keyfindings}[Title]
Content with key findings and statistics.
\end{keyfindings}

% Methodology (green) - for methods highlights
\begin{methodology}[Study Design]
Description of methods and procedures.
\end{methodology}

% Recommendations (purple) - for action items
\begin{recommendations}[Clinical Implications]
\begin{enumerate}
    \item Specific recommendation 1
    \item Specific recommendation 2
\end{enumerate}
\end{recommendations}

% Limitations (orange) - for caveats and cautions
\begin{limitations}[Study Limitations]
Description of limitations and their implications.
\end{limitations}

Professional Table Formatting:

\begin{table}[htbp]
\centering
\caption{Results Summary}
\begin{tabular}{@{}lccc@{}}
\toprule
\textbf{Variable} & \textbf{Treatment} & \textbf{Control} & \textbf{p} \\
\midrule
Outcome 1 & \meansd{42.5}{8.3} & \meansd{35.2}{7.9} & <.001\sigthree \\
\rowcolor{tablealt} Outcome 2 & \meansd{3.8}{1.2} & \meansd{3.1}{1.1} & .012\sigone \\
Outcome 3 & \meansd{18.2}{4.5} & \meansd{17.8}{4.2} & .58\signs \\
\bottomrule
\end{tabular}

{\small \siglegend}
\end{table}

Scientific Notation Commands:

CommandOutputPurpose
\pvalue{0.023}p = 0.023P-values
\psig{< 0.001}p = < 0.001Significant p-values (bold)
\CI{0.45}{0.72}95% CI [0.45, 0.72]Confidence intervals
\effectsize{d}{0.75}d = 0.75Effect sizes
\samplesize{250}n = 250Sample sizes
\meansd{42.5}{8.3}42.5 ± 8.3Mean with SD
\sigone, \sigtwo, \sigthree*, **, ***Significance stars

Getting Started:

\documentclass[11pt,letterpaper]{report}
\usepackage{scientific_report}

\begin{document}
\makereporttitle
    {Report Title}
    {Subtitle}
    {Author Name}
    {Institution}
    {Date}

% Your content with professional formatting
\end{document}

Compilation: Use XeLaTeX or LuaLaTeX for proper Helvetica font rendering:

xelatex report.tex

For complete documentation, refer to:

  • assets/scientific_report.sty: The style package
  • assets/scientific_report_template.tex: Complete template example
  • assets/REPORT_FORMATTING_GUIDE.md: Quick reference guide
  • references/professional_report_formatting.md: Comprehensive formatting guide

9. Journal-Specific Formatting

Adapt manuscripts to journal requirements:

  • Follow author guidelines for structure, length, and format
  • Apply journal-specific citation styles
  • Meet figure/table specifications (resolution, file formats, dimensions)
  • Include required statements (funding, conflicts of interest, data availability, ethical approval)
  • Adhere to word limits for each section
  • Format according to template requirements when provided

10. Field-Specific Language and Terminology

Adapt language, terminology, and conventions to match the specific scientific discipline. Each field has established vocabulary, preferred phrasings, and domain-specific conventions that signal expertise and ensure clarity for the target audience.

Identify Field-Specific Linguistic Conventions:

  • Review terminology used in recent high-impact papers in the target journal
  • Note field-specific abbreviations, units, and notation systems
  • Identify preferred terms (e.g., "participants" vs. "subjects," "compound" vs. "drug," "specimens" vs. "samples")
  • Observe how methods, organisms, or techniques are typically described

Biomedical and Clinical Sciences:

  • Use precise anatomical and clinical terminology (e.g., "myocardial infarction" not "heart attack" in formal writing)
  • Follow standardized disease nomenclature (ICD, DSM, SNOMED-CT)
  • Specify drug names using generic names first, brand names in parentheses if needed
  • Use "patients" for clinical studies, "participants" for community-based research
  • Follow Human Genome Variation Society (HGVS) nomenclature for genetic variants
  • Report lab values with standard units (SI units in most international journals)

Molecular Biology and Genetics:

  • Use italics for gene symbols (e.g., TP53), regular font for proteins (e.g., p53)
  • Follow species-specific gene nomenclature (uppercase for human: BRCA1; sentence case for mouse: Brca1)
  • Specify organism names in full at first mention, then use accepted abbreviations (e.g., Escherichia coli, then E. coli)
  • Use standard genetic notation (e.g., +/+, +/-, -/- for genotypes)
  • Employ established terminology for molecular techniques (e.g., "quantitative PCR" or "qPCR," not "real-time PCR")

Chemistry and Pharmaceutical Sciences:

  • Follow IUPAC nomenclature for chemical compounds
  • Use systematic names for novel compounds, common names for well-known substances
  • Specify chemical structures using standard notation (e.g., SMILES, InChI for databases)
  • Report concentrations with appropriate units (mM, μM, nM, or % w/v, v/v)
  • Describe synthesis routes using accepted reaction nomenclature
  • Use terms like "bioavailability," "pharmacokinetics," "IC50" consistently with field definitions

Ecology and Environmental Sciences:

  • Use binomial nomenclature for species (italicized: Homo sapiens)
  • Specify taxonomic authorities at first species mention when relevant
  • Employ standardized habitat and ecosystem classifications
  • Use consistent terminology for ecological metrics (e.g., "species richness
how to use scientific-writing

How to use scientific-writing on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add scientific-writing
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill scientific-writing

The skills CLI fetches scientific-writing from GitHub repository K-Dense-AI/scientific-agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/scientific-writing

Reload or restart Cursor to activate scientific-writing. Access the skill through slash commands (e.g., /scientific-writing) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.829 reviews
  • Chen Gonzalez· Dec 28, 2024

    Solid pick for teams standardizing on skills: scientific-writing is focused, and the summary matches what you get after install.

  • Chaitanya Patil· Dec 24, 2024

    scientific-writing reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Isabella Garcia· Dec 20, 2024

    scientific-writing has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Harper Chawla· Nov 19, 2024

    We added scientific-writing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Piyush G· Nov 15, 2024

    I recommend scientific-writing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Diya Liu· Nov 11, 2024

    scientific-writing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Olivia Ramirez· Oct 10, 2024

    scientific-writing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Shikha Mishra· Oct 6, 2024

    Useful defaults in scientific-writing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Charlotte Iyer· Oct 6, 2024

    Keeps context tight: scientific-writing is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Diya Garcia· Oct 2, 2024

    We added scientific-writing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 29

1 / 3