RI

rigorous-technical-writer

Improves technical writing for maximum precision.

Install

mkdir -p .claude/skills/rigorous-technical-writer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16552" && unzip -o skill.zip -d .claude/skills/rigorous-technical-writer && rm skill.zip

Installs to .claude/skills/rigorous-technical-writer

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Rewrite, draft, or improve technical prose to be precise, reviewer-resistant, compact, and explicit about assumptions and uncertainty. Use for ML paper sections (abstract, introduction, method, related work, conclusion), rebuttals, technical reports, or any writing where precision and defensibility matter. Triggers on: "rewrite this", "improve this paragraph", "make this more precise", "write the abstract", "draft the method section", "tighten this prose", "make this reviewer-proof", "remove vague claims".
511 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • Rewrite technical prose for precision
  • Draft technical sections like abstracts or methods
  • Improve clarity and scope control in writing
  • Make prose reviewer-resistant
  • Explicitly state assumptions and uncertainty

How it works

The skill tightens technical prose by preserving meaning while improving clarity, precision, scope control, and reviewer resistance, explicitly stating assumptions and uncertainty.

Inputs & outputs

You give it
Text to rewrite or topic/outline to draft from, optional target section and known weaknesses
You get back
Rewritten text, changes made, remaining risks, and suggested alternatives in markdown format

When to use rigorous-technical-writer

  • Rewriting paper sections
  • Improving technical report prose
  • Drafting precise method sections

About this skill

Inputs

  • text (text, required): The prose to rewrite or the topic/outline to draft from.
  • target_section (enum, optional): Which paper section this is for — changes the style constraints.
    • Example: abstract
  • known_weaknesses (text, optional): Known weaknesses or reviewer concerns to pre-empt in the writing.

Output Format

Format: markdown

Required sections:

  • rewritten_text
  • changes_made
  • remaining_risks
  • suggested_alternatives

Rigorous Technical Writer - Core Instructions

You are tightening technical prose for precision and defensibility. The goal is not to sound more impressive. The goal is to say exactly what is supported, under the right scope, with the right caveats.

Preserve meaning while improving:

  • clarity
  • precision
  • scope control
  • reviewer resistance
  • explicit assumptions

Do not smuggle in stronger claims than the source text can support. If the original wording is vague because information is missing, flag that gap instead of pretending the prose alone can solve it.

The final text should be easier to defend under review than the original.

Constraints

  • Do not change the meaning — only improve precision and defensibility.
  • Do not add claims not present in the original.
  • Do not remove caveats that are factually warranted.
  • Mark every significant change so the author can review it.
  • If a claim cannot be made precise without more information, flag it.

Self-Check Before Responding

  • Is every claim scoped to what was actually shown?
  • Are all implicit assumptions now explicit?
  • Are qualitative claims replaced with quantified ones where possible?
  • Is the "remaining risks" section honest about what prose cannot fix?

When not to use it

  • When the goal is to sound more impressive
  • When the task involves adding claims not present in the original text
  • When the task involves removing factually warranted caveats

Limitations

  • Does not change the meaning of the text
  • Does not add claims not present in the original
  • Does not remove factually warranted caveats

How it compares

This skill systematically refines technical writing for precision and defensibility, providing a structured output that highlights changes and remaining risks, which goes beyond simple grammar or style corrections.

Compared to similar skills

rigorous-technical-writer side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
rigorous-technical-writer (this skill)02moNo flagsAdvanced
docs-write226moNo flagsBeginner
content-research-writer1510moNo flagsBeginner
doc-coauthoring168moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

docs-write

metabase

Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).

22139

content-research-writer

ComposioHQ

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

15111

doc-coauthoring

anthropics

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

1686

research-grants

davila7

Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.

694

teams-channel-post-writer

daymade

Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.

591

write-docs

tldraw

Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.

665

Search skills

Search the agent skills registry