Documentation & Writing for Claude Code

Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. This skill should be used when looking up documentation for any programming library or framework, finding code examples for specific APIs or features, verifying correct usage of library functions, or obtaining current information about library APIs that may have changed since training.

Convert documents and files to Markdown using markitdown. Use when converting PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx, .xls), HTML, CSV, JSON, XML, images (with EXIF/OCR), audio (with transcription), ZIP archives, YouTube URLs, or EPubs to Markdown format for LLM processing or text analysis.

Use this skill when the user wants to read or search their Monologue notes through the Monologue Notes REST API. It covers authentication with the MONOLOGUE_API_KEY environment variable, safe token handling, listing notes, fetching a single note, pagination, filters, and error handling. The API is read-only and should be accessed with direct HTTP requests such as curl or any equivalent REST client.

> This skill provides comprehensive instructions for interacting with the Raindrop.io bookmarks service via its REST API using curl and jq. It covers authentication, CRUD operations for collections, raindrops (bookmarks), tags, highlights, filters, import/export, and backups. Use this skill whenever the user asks to work with their bookmarks from Raindrop.io, including reading, creating, updating, deleting, searching, or organising bookmarks and collections.

Generate beautiful code snippet images using ray.so. This skill should be used when the user asks to create a code image, code screenshot, code snippet image, or wants to make their code look pretty for sharing. Saves images locally to the current working directory or a user-specified path.

Connect Claude Code to Outline for document search, reading, creation, and management

Russian text quality — ~1,044 rules for typography, info-style, editorial, UX writing, business correspondence, and AI-text cleanup

Essential Elixir and Phoenix LiveView development guide with enforced skills, hooks, and patterns for idiomatic code

Skill: Spectrum 2 component documentation on-demand. Fetches S2 design guidelines, component options, and usage patterns without loading a persistent MCP server.

Advisory-only editor for spoken-out, dictated essays in the learnbiostats studio. Directs STRUCTURE, flags grammar, and suggests strategic language — but never modifies the writer's text unless the writer explicitly says "apply"/"rewrite this." Deliberately has no Write/Edit/Bash tools, so it physically cannot alter a draft; it returns a line-referenced, suggestion-only critique. Use to review a draft (writing/drafts/*.md), critique a spoken article, run a structural/line/voice pass, or do a pre

Generative note/post writer for the learnbiostats studio. Assembles publish-ready, Obsidian-vault-style notes and Substack-ready posts FROM the writer's own evergreen claims — composition from existing material, never invention of claims the writer has not made. Writes in the writer's voice (learning-in-public-voice lens, overridden by writing/voice-profile.md). Every sentence traces to an evergreen note (provenance recorded). Use to turn a cluster of evergreen notes into a post draft, draft a v

Shape-watcher for the substacker publication. Every 4-6 weeks reads the accumulating corpus, proposes emerging sections (when active-launch is not pre-planned), audits drift on existing sections, maintains section-map.md and per-section profiles. Also handles active mode — classifies drafts into sections, derives per-section voice overlays once a section has 3+ posts, hands off visual identity to cognitive-design-architect. Use every 4-6 weeks for the standard cycle, or on-demand when launching

Two-pass review (structural + voice) on substacker drafts. Produces marked-up critique, never a replacement draft. Flags voice-don'ts (delve, unpack, paradigm shift, generic opener), catches hedges that weaken rather than specify, blocks AI-explainer slop, verifies opener/closer/analogy-weight/rhythm/citation-form/section-breaks. Loads global voice-profile + per-section voice overlay. Use before publishing any draft. Trigger keywords: edit, review, voice check, structural pass, critique, pre-pub

Ingests and indexes the writer's Substack corpus. Watches the substacker inbox/ for new material (markdown notes, transcripts, Claude conversation exports, Readwise highlights), normalizes format, tags by topic and intuition density, dedupes against existing corpus, maintains the topic-ledger, and sweeps stale seeds. Use at session start, when the user drops raw material into inbox/, when asking "what have I written about X", or when user mentions ingest, library, corpus, seeds, indexing, topic

Two-mode synthesis worker for paper digests. The orchestrator picks the mode per invocation; you do not know whether other invocations have run before or after you. **Mode A** reads one paper's extraction notes and writes a reader-facing per-paper summary (headline + summary + specifics, with all hedging preserved) to a markdown file. **Mode B** reads a folder of per-paper summaries, clusters them by theme, writes the final digest as a reader-facing document (headline + themes with per-paper bul

An orchestrating agent for scientific writing that routes requests to specialized skills for manuscripts, grants, letters, emails, career documents, and cross-cutting clarity review. Provides multi-pass editing following structured workflows with document-type-specific frameworks. Use when user needs help with scientific or academic writing.

Orchestrates the end-to-end transformation of a methodology document (PDF, markdown, book chapter, research paper, framework guide) into a properly structured Claude Code skill - SKILL.md plus optional resource files plus an evaluation rubric. Runs Adler's six-step reading-and-construction methodology - inspectional reading, structural analysis, component extraction, synthesis-application, skill construction, validation - by sequentially invoking the standalone skills that own each step. Each st

Pre-publish ML/systems claim check for substacker drafts. Extracts atomic technical claims from prose, classifies each as simplified-correct / simplified-boundary / wrong / contested / overclaim, cross-references primary sources (arXiv, RFC, textbooks — never blog posts), flags boundary-breaks as teaching opportunities to fold into the post. Never rewrites the draft. 48h research cap per draft. Use after Editor approves voice and before the writer publishes a post that makes technical claims (es

Turn uploaded VoiceDrop voice memos (the jianshuo.dev/files R2 inbox) into WeChat article drafts — pull the unprocessed recordings, transcribe, and mine articles from each.

Prompt-native interactive HTML docs. Open-source community implementation of Jesse Pollak's bdocs idea.

Essential skills for everyday development: beginner-friendly explanations (baby-education), comprehensive README creation (readme-expert), LLM prompt optimization (prompt-engineering), AI-to-human doc transformation (humanize-docs), technical spec creation (quick-spec), pre-deployment QA checklisting (pre-deploy-checklist), and developer progress logging (been-there-done-that).

Corezoid BPM platform skills, MCP server, docs, and samples for Claude Code.

Review markdown documents with an interactive TUI and let Claude address feedback automatically.

Knowledge engineer — architecture docs, ADRs, API specs, system diagrams, onboarding

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".

Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".

Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".

Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".

Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".

Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.

Internal legal controls review — approval workflows, doc governance

Draft compliance policies required by a framework

Contract & Policy Drafter — NDA, MSA, employment agreements, SLAs, vendor contracts

Draft a contract or policy document from a description

Survey existing contracts and policy documents

|