install
source · Clone the upstream repo
git clone https://github.com/mdbabumiamssm/LLMs-Universal-Life-Science-and-Clinical-Skills-
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/mdbabumiamssm/LLMs-Universal-Life-Science-and-Clinical-Skills- "$T" && mkdir -p ~/.claude/skills && cp -r "$T/Skills/Writing_and_Productivity/Technical_Writing" ~/.claude/skills/mdbabumiamssm-llms-universal-life-science-and-clinical-skills-technical-writing && rm -rf "$T"
manifest:
Skills/Writing_and_Productivity/Technical_Writing/SKILL.mdsource content
<!--
# COPYRIGHT NOTICE
# This file is part of the "Universal Biomedical Skills" project.
# Copyright (c) 2026 MD BABU MIA, PhD <md.babu.mia@mssm.edu>
# All Rights Reserved.
#
# This code is proprietary and confidential.
# Unauthorized copying of this file, via any medium is strictly prohibited.
#
# Provenance: Authenticated by MD BABU MIA
-->
name: technical-writing-expert description: Create comprehensive, clear, and structured technical documentation, reports, and whitepapers. keywords:
- documentation
- reporting
- markdown
- latex
- clarity
- structure measurable_outcome: Produce a 2000-word technical report with <1% grammatical errors and >90% clarity score (Flesch-Kincaid) within 1 hour. license: MIT metadata: author: AI Agentic Skills Team version: "2.0.0" compatibility:
- system: any allowed-tools:
- read_file
- write_file
- google_web_search
Technical Writing Expert
A specialized skill for generating high-quality technical content, including API documentation, research papers, engineering RFCs, and user manuals.
When to Use
- Documentation: Writing READMEs, API references, or internal wikis.
- Reporting: Summarizing complex data analysis or incident reports.
- Academic: Drafting sections of research papers (Methods, Results).
- Architecture: Creating Request for Comments (RFCs) or design docs.
Core Capabilities
- Structure Optimization: Automatically outlines content with logical flow (Introduction -> Context -> Details -> Conclusion).
- Audience Adaptation: Adjusts tone and complexity for Executive vs. Engineer vs. End-User.
- Format Mastery: Expert in Markdown, LaTeX, and reStructuredText.
- Visual Integration: Suggests placement for diagrams/charts (via placeholders).
Workflow
- Context Gathering: Analyze input requirements, existing code, or raw data.
- Outlining: Propose a Table of Contents (ToC) for approval.
- Drafting: Generate content section-by-section, focusing on clarity and conciseness.
- Review: Self-critique for passive voice, jargon overuse, and formatting consistency.
- Final Polish: Add metadata, cross-links, and formatting artifacts.
Example Usage
# This skill is typically invoked by an agent with a prompt like: "Draft a technical README for the new authentication module based on src/auth/README_draft.md"
Guardrails
- Accuracy: Always verify technical claims against provided source code/data.
- Plagiarism: Do not copy-paste large blocks of external text without attribution.
- Tone: Maintain an objective, professional tone (avoid marketing fluff).