article
Generate technical articles and documentation using AI. Use for writing blog posts, documentation, and technical content.
What this skill does
# Article Generator Create technical articles and documentation with AI assistance. ## Prerequisites ```bash # Claude CLI for article generation npm install -g @anthropic-ai/claude-cli export ANTHROPIC_API_KEY=your_api_key # Or Gemini as alternative pip install google-generativeai export GEMINI_API_KEY=your_api_key ``` ## Article Operations ### Generate Article ```bash claude --print --model opus "Write a technical article about: [topic] Requirements: - Target audience: [developers/beginners/etc] - Length: ~[1500] words - Include code examples - Practical focus Structure: 1. Hook/intro that establishes the problem 2. Context/background 3. Main content with examples 4. Best practices 5. Conclusion with next steps" ``` ### Quick Draft ```bash gemini -m pro -o text -e "" "Write a first draft article about: [topic] Keep it concise (~800 words) with: - Clear thesis - 3-4 main points - One code example - Actionable takeaway" ``` ### Expand Outline ```bash gemini -m pro -o text -e "" "Expand this outline into a full article: OUTLINE: 1. [Point 1] 2. [Point 2] 3. [Point 3] For each section, provide: - 2-3 paragraphs - Relevant examples - Transitions between sections" ``` ## Article Types ### Tutorial ```bash claude --print --model opus "Write a step-by-step tutorial for: [task] Format: - Prerequisites section - Numbered steps with code - Expected output at each step - Common errors and fixes - Complete working example at end" ``` ### Comparison Article ```bash gemini -m pro -o text -e "" "Write a comparison article: COMPARING: [Option A] vs [Option B] CONTEXT: [Use case] Include: - Overview of each - Feature comparison table - Code examples for each - When to use which - Clear recommendation" ``` ### Explainer ```bash gemini -m pro -o text -e "" "Write an explainer article about: [concept] Audience: [technical level] Cover: - What it is (simple definition) - Why it matters - How it works (with diagrams if helpful) - Real-world examples - Common misconceptions" ``` ### How We Built It ```bash gemini -m pro -o text -e "" "Write a 'how we built it' article based on: PROJECT: [description] TECH STACK: [technologies] CHALLENGES: [key challenges faced] SOLUTIONS: [how you solved them] Format as engineering blog post with: - Problem statement - Architecture decisions - Implementation details - Lessons learned - Results/metrics" ``` ## Content Enhancement ### Verify Technical Accuracy ```bash ARTICLE=$(cat draft.md) gemini -m pro -o text -e "" "Review this technical article for accuracy: $ARTICLE Check: 1. Code examples work correctly 2. Technical claims are accurate 3. Best practices are current 4. No outdated information 5. Security considerations Flag any issues with corrections." ``` ### Improve Readability ```bash ARTICLE=$(cat draft.md) gemini -m pro -o text -e "" "Improve the readability of this article: $ARTICLE Focus on: - Clearer sentences - Better transitions - Active voice - Removing jargon - Adding helpful examples" ``` ### Add Code Examples ```bash ARTICLE=$(cat draft.md) gemini -m pro -o text -e "" "Add practical code examples to this article: $ARTICLE For each concept: - Add working code snippet - Include comments - Show expected output - Provide variations where helpful" ``` ### Generate Revision ```bash ARTICLE=$(cat draft.md) FEEDBACK="[feedback from reviewers]" gemini -m pro -o text -e "" "Revise this article based on feedback: CURRENT: $ARTICLE FEEDBACK: $FEEDBACK Incorporate the feedback while maintaining the article's voice and structure." ``` ## Structure Templates ### Blog Post Template ```markdown # [Catchy Title] [1-2 sentence hook that identifies the problem] ## The Problem [Describe the pain point readers face] ## The Solution [Introduce your approach] ### [Key Point 1] [Explanation with code example] ### [Key Point 2] [Explanation with code example] ## Putting It Together [Complete example combining the concepts] ## Conclusion [Summary and call to action] ``` ### Tutorial Template ```markdown # How to [Do Something] ## Prerequisites - [Requirement 1] - [Requirement 2] ## What We're Building [Brief description and screenshot/diagram] ## Step 1: [First Step] [Instructions] ```code [Example] ``` ## Step 2: [Second Step] ... ## Complete Code ```code [Full working example] ``` ## Next Steps [Where to go from here] ``` ## Best Practices 1. **Start with the reader** - What problem do they have? 2. **Show, don't tell** - Use code examples 3. **One idea per section** - Keep it focused 4. **Use concrete examples** - Abstract concepts need grounding 5. **Include working code** - Test everything 6. **End with action** - Tell readers what to do next 7. **Get feedback** - Have someone else read it 8. **Revise ruthlessly** - First drafts are just the start
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.