Docs & Writing

pingcap Skill

Review a Chinese TiDB documentation pull request or Markdown diff for factual accuracy, user usefulness, structure, completeness, version fit, links, and repo-style issues in pingcap/docs-cn.

pingcap Skill

Review a TiDB documentation pull request or Markdown diff for factual accuracy, user usefulness, structure, completeness, version fit, links, and repo-style issues in pingcap/docs.

pingcap Bundle

Write new Chinese TiDB documentation or update existing Chinese TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions. Use when PM or R&D engineers need user-facing Chinese docs in pingcap/docs-cn based on code PRs from pingcap/tidb or other TiDB ecosystem repositories, GitHub issues, product specifications, or external reference materials.

pingcap Skill

Use when creating or editing GitHub issues in pingcap/docs-cn so issue templates, required fields, scope boundaries, and labels stay consistent with repository workflow. Trigger on tasks involving issue creation, error reports, change requests, questions, label selection, or searching for existing issues before filing a new one.

pingcap Skill

Produces and merges Related resources cards for TiDB docs pages using the RelatedResources and ResourceCard MDX components. Use when the user asks to add or update a related resource card, resource link, blog card, video card, YouTube card, or TiDB Lab card in English, Simplified Chinese, or Japanese Markdown docs.

pingcap Skill

Writes or updates the front matter `summary` field in pingcap/docs and pingcap/docs-cn Markdown files. The summary targets 115-145 characters, with a 45-character absolute minimum. Use when a document is missing a summary, when a reviewer or CI check flags a low-quality summary, or when an existing summary is outdated, inaccurate, or the wrong length.

pingcap Bundle

Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions. Use when PM or R&D engineers need user-facing docs in pingcap/docs based on code PRs from pingcap/tidb or other TiDB ecosystem repositories, GitHub issues, product specifications, or external reference materials.

pingcap Skill

Use when creating or editing GitHub issues in pingcap/docs so issue templates, required fields, scope boundaries, and labels stay consistent with repository workflow. Trigger on tasks involving issue creation, error reports, change requests, questions, label selection, or searching for existing issues before filing a new one.

pingcap Skill

Create or update a zh translation PR from pingcap/docs to pingcap/docs-cn by using repo-local scripts to prepare change-unit translation inputs, apply minimal edits to the existing Chinese files, and create or update the target PR with the same branch, title, body, and label rules used in gh-util.user.js.

pingcap Bundle

Evaluate whether a change needs a release note. If yes, write, review, revise, or translate TiDB release note entries for the features, compatibility changes, improvements, and bug fixes sections. Use this skill when triaging PRs for release-note relevance, working with release note entries, aligning English and Chinese content, auditing `release-X.X.X.md` files, or editing files under `docs/releases/` or `docs-cn/releases/`.

timdevai Bundle

EU AI Act (Regulation (EU) 2024/1689) operational compliance for compliance teams. Three Article-level decisions: (1) What's the risk tier of this AI system — prohibited (Art. 5), high-risk (Art. 6 + Annex III), limited-risk (Art. 50), or minimal-risk? (2) For high-risk systems, what's the Article 43 conformity assessment route (Module A internal control vs Module H full QMS + notified body) and what goes in the Annex IV technical documentation? (3) Per organizational role (provider / deployer / importer / distributor / authorized representative), what are the active obligations and deadlines? Use during AI system intake review, when planning conformity assessment, or when scoping deployer obligations. Cites Articles + Annexes for every output. NOT executive AI strategy (see chief-ai-officer-advisor). NOT a legal substitute.

waseemnasir2k26 Bundle

Systematically QA test a web application. Use when asked to "qa", "QA", "test this site", "find bugs", "dogfood", or review quality. Four modes: diff-aware (automatic on feature branches — analyzes git diff, identifies affected pages, tests them), full (systematic exploration), quick (30-second smoke test), regression (compare against baseline). Produces structured report with health score, screenshots, and repro steps.

wenyuchiou Bundle

Turn a research area into a go/no-go decision dossier for ONE candidate thesis/proposal topic — a 3-gate verdict (is the gap open? is it a contribution? is it feasible?) with the evidence laid out so the researcher can verify it. Use when the user asks "is this gap worth pursuing", "help me pick a thesis topic", "is this idea already taken", "find me a defensible research gap", "vet this research idea before I commit", or "should I do this". NOT a literature review (use `literature-triage-matrix` for a comparison matrix) and NOT a study design (use `research-design-helper` once a topic is chosen). Produces a `.research/topic_dossier.md`, a `.research/topic_dossier.docx` (Word, colour-coded), a `.bib`, and a `.gaps.yml`.

tenwalk Bundle

Compile, diagnose, and fix IEEEtran LaTeX manuscripts for JSAC, TWC, TCOM, WCL, CL, and related IEEE journals: documentclass options, BibTeX/IEEEtran bibliography, undefined citations/refs, overfull hboxes, figure/table placement, algorithm/equation numbering, Index Terms, EDICS, biographies, and final PDF checks. Use this when the user asks to "compile IEEEtran", "fix LaTeX", "overfull hbox", "undefined references", "BibTeX error", "IEEE LaTeX", "latex编译", "参考文献不显示", or prepare a manuscript PDF for IEEE submission. Use latex-compile when available for raw build execution; this skill adds IEEE-specific diagnosis.

tenwalk Bundle

Produce publication-grade result figures for IEEE communications papers (JSAC, TWC, TC/TCOM, WCL, CL) — correct column widths, embedded fonts, vector output (PDF/EPS), grayscale- and colorblind-safe palettes, readable fonts, and the comms-standard plot types: BER/outage vs SNR on a log y-axis, achievable/sum rate vs SNR or antennas, convergence curves, CDFs, the analysis-line + simulation-marker overlay, learning curves (NMSE vs SNR, training/validation loss), and ISAC plots (rate–CRB tradeoff, beampattern, ROC). Use whenever the user wants to make or fix a figure for a comms paper: "make a result plot", "BER curve", "误码率曲线", "中断概率图", "和速率曲线", "收敛曲线", "仿真图", "NMSE曲线", "训练损失曲线", "CRB折中图", "波束方向图", "IEEE figure", "single/double column figure", "图太小看不清". For deciding which metrics to plot, use ieee-experiments; for captions-as-argument, see ieee-writing.

aatirar Skill

Pull sales and customer calls (transcripts, summaries, participants) from your call recorder into local markdown files. Works with Gong, Fireflies, or any recorder with a transcript API via an adapter. Run this first — every other VoC skill reads what it writes. Trigger on /voc-source-calls, "pull this week's calls", "fetch call transcripts", "sync my call recordings".

aatirar Skill

Turn a folder of call transcripts into a prospect intelligence report. Filters noise, separates prospect calls from customer calls, fans out parallel subagents to read transcripts, and consolidates personas, pain points, objections, competitive mentions, feature requests and verbatim quotes. Trigger on /voc-analyze-calls, "analyze this week's calls", "what are prospects saying", "call intelligence report".

awarexone Skill

Bug triage validation system, Immunefi report format, and 20 real paid bounty examples dissected. Use this when validating a finding before submitting, writing an Immunefi report, checking if a bug is actually valid, or studying real examples of paid vulnerabilities.

canonical Skill

Validates documentation builds successfully. Use when checking Sphinx/RTD build integrity or diagnosing build failures. Reports errors, warnings, and build configuration issues.

canonical Bundle

Enforces project documentation style guide compliance for tone, voice, terminology, punctuation, and formatting. Use when checking documentation style or validating MyST/reST syntax. Cites specific style guide violations.

canonical Bundle

Verifies documentation accuracy by cross-referencing claims, CLI commands, API signatures, and configuration against source code. Use when validating documentation correctness or checking code-docs consistency. Flags unsupported or outdated claims.

canonical Skill

Analyzes documentation against Diataxis framework (Tutorial, How-to, Reference, Explanation). Use when reviewing documentation structure or classifying content type. Identifies misalignments between declared category and actual content.

canonical Skill

Validates documentation structural integrity including heading hierarchy, metadata, file naming, navigation, and cross-references. Use when checking documentation organization or validating toctree structure.

catlog22 Bundle

Four-layer citation verification for academic papers. Scans LaTeX/BibTeX files, verifies every citation via WebSearch and Google Scholar, generates verification report with fix suggestions. Triggers on "verify citations", "check references", "citation verification", "prevent fake citations", "引用验证".

changhochien Skill

Client Report

profsynapse Bundle

Keep Nexus loading on mobile and compliant with the Obsidian plugin store — vet a dependency, import without crashing init, confine a vault path, and prove none of it regressed with the reachability checker. Use before adding an npm package or a Node import, when writing to caller-supplied vault paths, when gating a desktop-only feature, when a PDF or worker-backed feature misbehaves, or when the plugin fails to load on a phone.

saubakirov Skill

Command /tfw-docs updates Trace-First Workflow project documentation after review. Use for /tfw-docs or updates to KNOWLEDGE.md sections 1-3 from RF/REVIEW results.

45ck Skill

bug-report-writer

45ck Skill

evaluation-report-writer

45ck Skill

report-finding-writer

verygoodopensource Bundle

Runs quality review agents on demand — reviews code against VGV standards for architecture, tests, and simplicity, then writes one consolidated, numbered report.

xberg-io Skill

Use when fetching a live URL and converting it to Markdown. Covers --url, custom user agents, preprocessing for noisy pages, and the --json ConversionResult shape.

minghou-lei Skill

Scan codebase architecture and generate/update .omm/ documentation. Use when the user says "omm scan", "scan architecture", "update architecture", "refresh diagrams".

coco-research Skill

Generate a session report with token usage estimates, work summary, and outcomes

conorluddy Bundle

Review code against Conor's style guide — naming, progressive disclosure, function design, error handling, agentic patterns, and token economics. Use this skill whenever the user asks for a code review, says things like "review this", "check my code", "look over this PR", "roast this", asks for feedback on a diff/branch/file, or after finishing an implementation and wants a pass before commit. Also trigger proactively after substantial code changes where a self-review would catch issues. Produces a structured findings report grouped by severity (blocker / major / minor / nit) with file:line references and concrete suggested fixes — not generic platitudes.

jiaxi2 Bundle

Configurable Git, GitHub, documentation, version, tag, release, and firmware-governance workflow for embedded-first and general repositories. Use for branch, commit, push, pull request, merge, README, CHANGELOG, repository initialization, hook installation, version files, Git tags, GitHub Releases, release notes, firmware artifacts, test baselines, production baselines, customer deliveries, or requests such as "ref readme", "ref changelog", "ref release", "ref tag", and "ref branch". First resolve repository needs, then select and apply an appropriate profile instead of forcing one Linux, OpenAI, PX4, Git Flow, or README style.