Docs & Writing

espennilsen Skill

Monitor open GitHub PRs across all repos in ~/Dev. Checks PR age, flags stale PRs, and optionally alerts via Aivena/Telegram. Uses `gh pr list` for accurate GitHub data. **TRIGGERS - Use this skill when:** - User asks about open PRs, pull requests, or PR status - User says "check PRs", "any stale PRs?", "PR review status" - Cron job `pr-monitor` fires - User asks "what needs review?" or "what's waiting for merge?" - User wants a PR dashboard or PR age report

espennilsen Bundle

Generate and maintain AI-readable markdown documentation for a codebase in docs/. Use this skill whenever the user asks to document their codebase, generate project docs, create architecture docs, update documentation after code changes, build a knowledge base for AI agents, create onboarding docs, map out a codebase, or explain a project structure. Also trigger when users say things like "document this repo", "create docs for my project", "update the docs", "write architecture documentation", "help AI understand my code", "generate a codebase overview", or "maintain docs". This skill is specifically about creating structured markdown files in a docs/ directory that serve as a knowledge base — NOT about writing inline code comments, README files, or API reference docs from docstrings.

espennilsen Skill

Generate comprehensive status reports for git repositories. Analyzes commits, codebase structure, type errors, branch health, dependency status, GitHub PRs/issues/CI, working tree changes, and optionally integrates with `td` (task management CLI) if a `.todos` folder is present. **TRIGGERS - Use this skill when:** - User asks for the status of a git project or repo - User asks "what's going on in [project]" or "give me an overview of [repo]" - User wants a project summary, progress report, or codebase overview - User asks about recent commits, code structure, or project health - User says "check my project" or "project status" **Output:** A rich, structured text report covering overview, branches, commit history, codebase breakdown, GitHub activity, dependency health, issues/errors, working tree changes, task management, and summary.

espennilsen Skill

Write and improve documentation for ComfyUI nodes in per-node JSON files. Use when asked to document nodes, write node descriptions, add tips to nodes, improve node docs, enrich node content, fill in empty node descriptions, or batch-write documentation for new/updated nodes. Also triggers on "write docs for nodes", "document the new nodes", "improve node tips", "fill in node descriptions", "enrich nodes", "node content pass", "update nodes", "sync comfyui nodes", "new comfyui version", or "node enrichment".

espennilsen Skill

Generate and update language-idiomatic doc comments for TypeScript (TSDoc/JSDoc) and Rust (Rustdoc). Use when asked to "add docs", "document this file", "generate docstrings", "add JSDoc", "add Rustdoc", "write TSDoc", or when working with TypeScript or Rust source files that need documentation comments. Supports file-level and selection-level operations. Deterministic and idempotent — safe to run repeatedly on the same code. Does NOT change behavior, rename symbols, or refactor code.

vm0-ai Skill

Analyze conversation history for dev server errors and create a structured GitHub bug report

ww-w-ai Skill

Unified skill for managing the entire PDCA cycle. Supports Plan → Design → Do → Check → Act workflow with automatic phase progression. Use proactively when user mentions PDCA cycle, planning, design documents, gap analysis, iteration, or completion reports. Triggers: pdca, plan, design, analyze, check, report, status, next, iterate, 계획, 설계, 분석, 검증, 보고서, 반복, 개선, 計画, 設計, 分析, 検証, 報告, 反復, 计划, 设计, 分析, 验证, 报告, 迭代, planificar, diseño, analizar, verificar, informe, planifier, conception, analyser, vérifier, rapport, planen, Entwurf, analysieren, überprüfen, Bericht, pianificare, progettazione, analizzare, verificare, rapporto Do NOT use for: simple one-line fixes, non-development tasks

datex Bundle

Use when adding, modifying, or removing toolbar buttons and click flows on a Datex Studio hub configuration. Covers fetching hub config via `dxs configuration get hub`, editing the toolbar[] and flows[] arrays, wiring click flows that launch reports, and pushing the modified config back with `dxs configuration upsert hub`. Trigger for: "add a toolbar button to the X hub", "wire a button that opens the Y report", "modify hub N", "change what the X button does", "launch report Y from a hub button".

datex Skill

Use when modifying EXISTING Datex Studio reports on a branch. Handles label/style changes, field rearrangement, adding/removing columns, datasource modifications, and adding new data sections. Trigger for: "edit a report", "modify a report", "change the label", "add a column", "update the report on branch X", "fix the report layout". For creating NEW reports from scratch, use `report-creator`.

datex Bundle

Use when building NEW Datex Studio reports from scratch. This is the entry point for all new report work — it orchestrates requirements gathering, schema exploration, datasource creation, layout prototyping, and deployment as a single workflow. Trigger for: "create a report", "build a report", "report from work item", "report from requirements". For modifying EXISTING reports, use `report-editor`.

datex Skill

Use when investigating the current state of a Datex Studio codebase with read-only inspection — answers questions about existing components, flow code, type definitions, datasource shapes, and configuration without modifying anything. Carries Datex Studio- specific patterns: extract flow code from `nodes[0].stepConfig.executeCodeConfig.code` (not from the JSON surface), delegate OData schema queries to `schema-explorer`, fetch enum values from `*-customType` configs on the branch via `dxs source explore`, return in `Answer / Sources / Caveats` format. Triggers: "research the codebase", "investigate how X works", "find where Y is defined", "answer questions about current code state". Consumed by impact-analysis, requirements-gathering, report-creator, and any skill needing grounded read-only inspection.

datex Skill

Produces a standardized requirements brief from any source: DevOps work items, mockups, natural language descriptions, existing reports, or documents. This is a utility skill — it gathers and structures requirements but does not build anything. If the goal is to create a report, datasource, or other artifact, use the appropriate creation skill as the entry point; it will invoke this skill when it needs requirements.

matthull Bundle

Convert markdown files to beautifully formatted PDFs with dark mode support. This skill should be used when users want to export markdown documents to PDF format, especially when they need dark themes, proper ASCII diagram rendering, or professional formatting for tables with icons.

microclaw Skill

Define a word or explain a term, with meaning, part of speech, and usage. Uses a free dictionary API for English words (no API key) and explains technical/jargon terms directly. Use when users ask 'what does X mean', 'define X', the meaning of a word, or to clarify jargon/acronyms. Triggers on mentions of define, definition, meaning of, what does mean, synonym, jargon, acronym, 什么意思, 定义, 含义, 解释一下这个词.

microclaw Skill

A systematic method for finding the root cause of a bug, crash, error, or wrong output — reproduce, isolate, hypothesize, test, fix. Use when users report something broken, an exception/stack trace, flaky behavior, or 'why doesn't this work'. Triggers on mentions of bug, error, crash, stack trace, doesn't work, broken, exception, debug, root cause, 报错, 崩溃, 调试, 排查, 为什么不工作, 找原因.

ocean326 Bundle

读取飞书云文档内容（纯文本/富文本块/Markdown）。当用户分享飞书文档链接、要求获取/阅读/抓取/解析飞书云文档时使用。基于飞书开放平台 docx/v1 API，独立于主代码。

googlecloudplatform Bundle

Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation. Use this skill when the user wants to check for breaking changes, missing tests, or missing documentation, or other problems in the downstream providers.

hsigstad Bundle

Pull recent Tactiq meeting transcripts from Google Drive, route each to the right project, and save as raw markdown under docs/meetings/. Use when the user runs /tactiq or asks to 'grab the tactiq notes' / 'sync meeting transcripts' / 'save the recent tactiq transcripts'.

hsigstad Skill

Convert Outlook .eml email exports to clean markdown for project docs. Use when the user wants to save email exchanges to a project's docs/emails/ directory.

imbue-ai Bundle

Run experiments and derive mathematical proofs to support a pre-existing theory idea supplied as a latex/pdf/markdown file or argument.

imbue-ai Bundle

Import a pre-existing theory from a latex/pdf/markdown file and store in the context database.

jimweller Skill

Write documentation based on conversation history and folder contents

jimweller Skill

Format and lint markdown files using prettier and markdownlint-cli2. Always use the skill after writing markdown files (*.md) intended for humans.

jimweller Skill

Writing style when writing readme documentation. Always use when creating or updating README.md files.

jimweller Skill

Guidelines for markdown syntax and formatting rules

trogonstack Skill

Generate a README introduction following the Diataxis 4-paragraph structure for product documentation.

trogonstack Skill

Reorganize documentation into the Diataxis framework structure. Splits existing docs into tutorials, how-to guides, reference, and explanation sections.

xingfanxia Bundle

横纵分析法（Horizontal-Vertical Analysis）深度研究 skill — 叙事型来龙去脉调研。由数字生命卡兹克提出，融合了索绪尔的历时-共时分析、社会科学的纵向-横截面研究设计、商学院案例研究法与竞争战略分析的核心思想。 当用户想要系统性研究一个产品、公司、概念、技术或人物时使用。核心是双轴分析：纵轴追踪从诞生到当下的完整生命历程（以叙事故事呈现），横轴在当下时间截面上与竞品/同类进行系统性横向对比，最后交叉两条轴产出独到洞察。最终产出一份排版精美的 PDF 研究报告。 适用场景：想从零搞懂一个东西的全貌（"帮我研究一下 X"、"X 是什么来头"、"X 的来龙去脉"、"帮我搞懂 X"），需要叙事型万字研究报告 + PDF 产出。 不适用：需要做决策判断的调研（"该选 A 还是 B"、"X 靠不靠谱" → 用 deep-research）、简单名词解释（"XX 是什么"）。 触发词：横纵分析、narrative research、研究一下、帮我搞懂、来龙去脉、什么来头、帮我了解、做个研究、全面了解、帮我摸清楚、horizontal-vertical analysis。

zakariaf Skill

Enforces Effective-Dart documentation on the public surface — a `///` doc on every public class/method/getter/field/typedef, a one-sentence standalone summary that says WHY plus units/ranges/nullability/throws/side-effects (never a restatement of the name), verb-phrase method docs, "Whether…" boolean getters, `[bracket]` cross-links, one `library;` doc per exported barrel, in-body `//` that explains why not what, and the enforced invariant restated at its enforcement point — backed by `public_member_api_docs` and `dangling_library_doc_comments` as analyzer errors. Use when adding or reviewing a public API, a Notifier/provider, a Service interface, a sealed Failure, a value type, or preparing a package's dartdoc.

agent-sh Skill

Use when looking up documentation

karlorz Bundle

Review and verify Claude plan statuses (active/follow_up/review_needed) under ~/.claude/plans by cross-checking GitHub PR state and the latest repository code, then update plan metadata and generate a prioritized status-review report. Use when active/follow_up plans may already be implemented, blocked, or obsolete and you want a recurring review loop.

nixopus Skill

Look up Nixopus platform documentation at runtime. Use when the user asks about Nixopus features, configuration, concepts, self-hosting, API reference, guides, or anything where accurate product information is needed. Prevents hallucination by fetching the latest docs.

paulkinlan Skill

Verify factual claims in a document against available evidence, producing an annotated report

paulkinlan Skill

Produce a formatted metrics report with key indicators, trends, and recommendations

paulkinlan Skill

Write clear technical documentation for a specific audience

paulkinlan Skill

How to report results back to the team after completing work. Use after finishing any task or request.