Docs & Writing

edloidas Bundle

Write Markdown that people actually read — READMEs, docs, PR bodies, issue bodies and comments, release notes, changelogs. Covers GitHub-flavored extras (alerts, collapsible sections, task lists, mermaid), prose that leads with the point instead of burying it, and a README skeleton.

adobe Skill

When writing documentation in a variety of scenarios, follow the Adobe content writing standards.

adobe Skill

Require a thorough deep-read of the relevant codebase before planning or implementing; write findings to a persistent markdown file (e.g. research.md) so the user can review and correct before any work proceeds.

d-o-hub Bundle

GitHub release management, crates.io trusted publishing, npm provenance, and GitHub Pages documentation. Use when creating releases, publishing packages, or deploying docs.

raine Skill

Convert markdown to Slack-ready rich text and copy to clipboard.

sunilgentyala Skill

XML External Entity injection expert methodology. Covers classic XXE, blind OOB XXE, XXE via file upload, XXE to SSRF, and XXE in PDF/DOCX parsers.

sunilgentyala Skill

Red team and penetration test report writing methodology. Covers executive summary, technical findings format, CVSS4 scoring, remediation guidance, and evidence documentation standards.

v0lka Bundle

Analyzes the project codebase, documentation, and memory to identify the single highest-priority task to work on right now. Triggers on phrases like "Hey, what are we going to do today, Brain?", "What should I work on?", "What's next?", or any request for task prioritization.

v0lka Bundle

Conduct thorough, multi-source research using Tree of Thoughts methodology. Produces cited, multi-perspective syntheses with explicit confidence ratings, evidentiary hierarchy, and transparent documentation of pruned branches. Use when the user asks for research, analysis, investigation, deep dive, literature review, or any complex topic requiring structured reasoning.

v0lka Bundle

Initialize a specification system for a project from scratch. Analyzes the codebase to identify architectural layers, domains, boundaries, and key decisions, then generates the initial set of specs (META.md, WORKFLOW.md, INDEX.md, domain specs, contracts, architecture docs, ADR template). Use when bootstrapping specs for a new project, setting up documentation governance, or creating a spec system for an existing codebase that has none.

v0lka Bundle

Execute the synthesis phase of an research project. Analyzes the hypothesis graph, determines report verbosity (simple vs. complex path), generates the final report, creates a prototype inventory, and finalizes the implementation plan in the brief. Use when concluding a research project, writing the final report, or when the research question has been answered or the budget is exhausted.

biggora Bundle

Use this skill whenever the user wants to search, validate, or look up US trademarks, brand names, or keywords in the USPTO trademark database. Triggers include: checking if a brand name or word is trademarked, searching trademark registrations, validating whether a keyword is available for trademark, looking up trademark status or owner, batch-checking multiple brand names, or building any tool/script involving the USPTO trademark database. Also use for requests like "is X trademarked?", "find trademarks for [keyword]", "check trademark availability", "search USPTO for [name]", or "validate these words against USPTO trademarks." Always use this skill for any trademark search or validation task — even simple lookups benefit from the correct API patterns and output formats defined here.

spacezephyr Bundle

从 YouTube、小宇宙、B站、抖音和小红书链接提取字幕或逐字稿；优先读取平台字幕，无字幕时自动提取音频并调用可用 ASR，输出 Markdown 与 SRT。用户发送这些平台链接、要求提取字幕/文案/逐字稿/视频转文字，或在字幕完成后希望下载原视频时使用。字幕成功后必须询问用户是否下载原视频；小宇宙对应下载原音频。

testomatio Skill

Use for any browser work — driving a web app, checking a behaviour, filling a form, reading a page — via npx prima-cli, in preference to npx playwright-cli, which prima runs on top of and falls back to. Covers npx prima-cli check, do, pw, verify, ask, research, go, status, report, browser, config, and session setup. Trigger on "prima", "prima-cli", "npx prima-cli", on a browser task described as behaviour ("confirm the editor saves"), and whenever npx playwright-cli would otherwise be driven step by step.

testomatio Bundle

Analyze and improve existing markdown manual test cases for clarity, structure, and Test Management Tool format compliance.

testomatio Bundle

Map test cases — manual (markdown) and automated e2e (Playwright, Cypress, WebdriverIO, CodeceptJS, Puppeteer, Appium) — to source code files and produce a `coverage.tests.yml` mapping consumed by `@testomatio/reporter --filter "coverage:..."`. Use this skill when the user wants to run only the tests affected by a code change, generate a coverage file (manual, e2e, or both), build a traceability matrix between tests and source code, or set up change-aware regression.

testomatio Bundle

Synchronize test scenarios and cases between a local project and Testomat.io. Use this skill whenever the user wants to pull/export/download tests from Testomat.io; or push/import/sync new or updated test cases back to the TMS in corresponding `*.test.md` format. Supports custom directories, markdown test format and advanced import/export workflows.

testomatio Bundle

This skill converts manual test cases into production-ready automated test scripts. It analyzes the existing automation framework, interprets manual test steps, and generates maintainable tests following automation best practices. Use this skill whenever the user wants to automate manual test cases, expand test coverage, or create end-to-end automated flows from existing test documentation.

testomatio Skill

Create and launch Testomat.io test runs with the `@testomatio/reporter` CLI. Covers manual runs for testers, mixed manual+automated runs, local test execution with reported results, and remote launches through a Testomat.io CI profile (`--remote`). Runs can include the whole suite or be filtered by tag, plan, label, Jira ticket, or changed source files. Use when the user asks to start or create a test run from the command line, run a filtered group of tests, launch tests remotely, or report results into an existing run.

tikalk Bundle

Reverse-engineer architecture from an existing codebase to create ADRs documenting discovered decisions. Use when bootstrapping architecture documentation for brownfield projects.

tkersey Bundle

Create Deckset markdown presentations and speaker notes from conversation context. Use for explicit Deckset requests, markdown slide decks, or edits to an existing Deckset deck. PowerPoint and Google Slides artifacts belong to the presentations skill.

tomimor Skill

Heavyweight PR verification that produces a structured report: code review (delegates to miguel-review), test verification with gap analysis and execution, and upstream assumption validation. Use when the user mentions verify PR, verify my PR, PR verification, test plan for PR, or validate PR changes.

tomimor Skill

Generate a short, copy-paste friendly Slack message listing the user's open PRs in the current repo, split into "Ready for review" (non-draft) and "Drafts" sections, each as bullets with custom emoji and markdown-style links. Use when the user mentions PRs ready to review, Slack PR list, share my PRs on Slack, or wants a short message to ping reviewers.

huguryildiz Skill

Use when a numeric result is about to be reported, compared, or put in a paper — enforcing replication counts, uncertainty intervals, paired comparisons on matched instances, and visible denominators. Also use when designing how many runs a claim needs. Trigger phrases: "is this difference real", "how many replications", "report with confidence intervals", "single run result", "compare method A vs B", "is N=3 enough".

jovd83 Bundle

Requirements-analysis skill for Playwright planning and implementation. Use when Codex needs to extract testable behaviors, acceptance criteria, risks, dependencies, or open questions from tickets, specs, markdown docs, or other requirement sources before writing tests or coverage plans.

jovd83 Bundle

Central entrypoint for broad or ambiguous Playwright requests. Use when Codex needs to classify the user's testing goal, choose the right Playwright subskill, and move from intent to implementation, planning, documentation, execution, or reporting without unnecessary menu-driven back-and-forth.

jovd83 Bundle

Automation-code documentation skill for Playwright suites. Use when Codex needs to add or improve human-readable comments, docblocks, or file-level explanations around existing Playwright tests without drowning the code in redundant commentary.

jovd83 Bundle

Coverage-plan review skill for Playwright work. Use when Codex needs to present a proposed coverage plan, surface assumptions and tradeoffs, collect user feedback, and secure explicit approval before large implementation or documentation work.

jovd83 Bundle

Use when Playwright work must be handed from one operator to another, including at task completion, during mid-task pauses, after a blocker, or before review. Create a structured handover that records what was completed, where execution stopped, what remains, validation status, blockers, and the exact steps to resume safely.

jovd83 Bundle

Coverage-maintenance skill for Playwright planning and documentation. Use when Codex needs to synchronize coverage plans, scenario IDs, traceability links, and summary counts after tests, requirements, or narrative test documents change.

jovd83 Bundle

Failure-analysis skill for Playwright runs. Use when Codex needs to investigate a failing test, distinguish likely product bugs from test issues, and produce a concise developer-focused root-cause report backed by evidence.

jovd83 Bundle

Use when Playwright work spans multiple sessions or operators and a live resume pointer is needed. Maintain a current state file that records the latest completed step, current in-progress step, remaining work, blockers, touched files, resume commands, validation snapshot, and links to the latest handover.

jovd83 Bundle

Legacy Playwright-specific alias for BDD case formatting. Prefer the standalone `test-artifact-export-skill` skill for Gherkin, BDD, and export-ready case rendering, and use this only when Playwright-local conventions must be preserved explicitly.

jovd83 Bundle

Legacy Playwright-specific alias for TDD-style case documentation. Prefer the standalone `test-artifact-export-skill` skill for formatting approved test cases or building export-ready artifacts, and use this only when Playwright-local conventions must be preserved explicitly.

jovd83 Bundle

Legacy Playwright-specific alias for plain-text case formatting. Prefer the standalone `test-artifact-export-skill` skill for lightweight narrative case output, and use this only when Playwright-local conventions must be preserved explicitly.

warpdotdev Bundle

Find and segment top external open-source contributors for relationship-building, weekly reporting, recognition, or contributor strategy. Use this whenever the user asks to identify "top contributors", "best OSS contributors", "contributors to thank", "who should we thank", "who is contributing meaningfully", "weekly top contributors", "contributor report", or asks for a GitHub contributor shortlist. This skill analyzes merged and open PRs, filters out employees/org members/bots and typo-only contributors, inspects open PR status for contributor-actionable concerns, enriches candidates with GitHub profile/repo context, and returns a practical contributor analysis with linked PRs/issues.