Docs & Writing

kazdenc Skill

Set up environment variables across local, staging, and production with validation and documentation. Use when user says "set up env vars", "environment variables", "configure secrets", ".env setup", "env validation", or needs to manage configuration across environments.

meyverick Skill

Enforces strict, standardized Markdown formatting. Use when writing documentation, generating reports, formatting code blocks, or creating wikis.

meyverick Skill

Guides agents through project documentation architecture. Use when creating, reviewing, or updating a project's README or Wiki documentation.

meyverick Skill

Validates testing, logging, and observability standards. Use when writing tests, setting up logging systems, reviewing API schemas, or compiling system documentation.

modiqo Bundle

Use for structured representation of a multi-file PDF skill with references, code snippets, artifacts, and an ordered form-filling recipe. Preserves evidence with SkillSpec routes, forbids, dependencies, traces, and token-savings reports

modiqo Bundle

A skill whose guidance shows example code. Use for testing documentation-example qualification.

modiqo Bundle

Read a repository, map what exists, and produce neutral architecture documentation without changing code.

modiqo Skill

Format Markdown tables in the current project so columns align.

modiqo Skill

Summarize open pull requests for a repository and write a local report.

modiqo Bundle

Upload the generated report to the configured reporting endpoint.

apolo-81 Bundle

Crea presentaciones profesionales de alto impacto (keynotes, pitch decks, propuestas comerciales). Usar cuando: "presentacion profesional", "pitch deck", "crear slides", "deck para cliente", "investor deck", "presentacion para auditorio", "consulting deck", "TED-style", "propuesta visual", "slide deck", "presentacion impactante".

bsene Skill

Write, review, debug, or explain PHP code. Use whenever the user mentions PHP, .php files, Composer, PSR standards, or PHP frameworks (Laravel, Symfony, etc.), or asks about PHP language features, functions, or syntax. For anything beyond common knowledge — exact function signatures, parameter order, return types, edge-case behavior, deprecations, or version differences — verify against the official documentation at https://www.php.net/ (e.g. function pages like https://www.php.net/manual/en/function.array-filter.php) rather than relying on memory.

bsene Skill

Recognize and apply the monoid abstraction (binary associative operation + neutral element) in Clojure/ClojureScript code. Use whenever the user is combining, aggregating, merging, or reducing data — metrics and counters, event logs, config objects, or any `reduce`/`fold`/`merge-with` over a collection — even if they don't use the word "monoid". Also use when reviewing code that special-cases empty lists/collections, when discussing Map-Reduce or parallel aggregation (including `pmap`-based reduction), or when designing a generic `combine`/`merge`/`empty` API instead of ad hoc merge logic. Trigger this for "how do I merge these two X" or "what's a clean way to aggregate Y" style questions, not just explicit monoid/algebra questions. For TypeScript idioms, route to the `typescript` skill instead.

bsene Bundle

Use this skill when the user wants to investigate a bug, defect, incident, or quality issue and find its root cause — including requests to run a "5 whys" analysis, write a postmortem, do a root-cause analysis (RCA), figure out why a bug reached production or slipped past code review/QA, set up a recurring defect-analysis routine, or run a daily/weekly quality-improvement (Kaizen) triage. Also known as the Dantotsu method (Sadao Nomura's Toyota-derived defect-analysis approach, adapted for software). Trigger even if the user doesn't name the method explicitly — e.g. "why did this bug get through code review", "a client reported a bug, help me analyze it", "I want to understand why this keeps happening", "write up a root cause report for this defect", or "help me prioritize which fixes to actually ship this week".

bsene Bundle

GitHub Flavored Markdown (GFM) syntax reference — tables, alerts, footnotes, task lists, links, images, mentions, anchors, escaping, and common pitfalls. TRIGGER when: user asks about GFM, github flavored markdown, markdown syntax, md syntax, github markdown formatting, markdown table, markdown heading, markdown link, markdown image, task list syntax, markdown alert, GitHub callout, footnote markdown, markdown line break, markdown emoji shortcode, escape markdown special chars, section anchor, autolink. DO NOT USE when: user is composing prose content in markdown and needs no syntax help — only invoke when the question is about rendering, syntax correctness, or feature availability.

bsene Bundle

Write, review, debug, and configure ClojureScript code and projects. Use this whenever the user mentions ClojureScript, .cljs/.cljc files, shadow-cljs, figwheel, the CLJS compiler, JS interop from Clojure, Reagent/re-frame/Reagent-style UI code, or asks to convert JS/TS logic into ClojureScript. Also use it for questions about CLJS compiler options (:optimizations, :main, :npm-deps, :externs, etc.), consuming JS/npm libraries from CLJS, source maps, Google Closure Library usage, or the newer ^:async/await function support. Also trigger for CLJS recursion/stack-overflow/trampoline questions. Trigger even if the user just pastes CLJS code with an error and asks "what's wrong here" or asks to set up a new CLJS project. Do NOT use for nbb (babashka/nbb) scripts, `nbb.edn` projects, or anything meant to run via `nbb script.cljs`/`npx nbb` — those have a different (SCI-interpreted, no-Closure-Compiler) language surface; those are out of scope for this skill — consult nbb's own documentation.

bsene Bundle

Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.

krzysztofsurdy Bundle

Systematic debugging methodology for finding and fixing bugs through root cause analysis. Use when the user encounters a bug, test failure, flaky behavior, production error, performance degradation, or integration failure. Covers the reproduce-investigate-hypothesize-fix-prevent workflow, evidence-based diagnosis, bug category strategies (logic errors, race conditions, memory leaks, integration failures), and post-mortem documentation.

krzysztofsurdy Bundle

Write comprehensive pull request messages with structured technical documentation, testing instructions, and verification queries. Framework-agnostic with customizable templates. Use when writing or generating a PR description, preparing a pull request for review, or documenting code changes for teammates.

jqaisystems Bundle

Capture a raw idea as a dated, tagged markdown file in an ideas folder and keep an index up to date. Cleans filler words from the dump while preserving the substance, so capture stays fast and retrieval stays possible. Use when the user says "idea:", "capture this idea", "save this idea", or "add to my ideas".

jqaisystems Bundle

Scan a folder tree for accumulated junk (dependency folders, build caches, stray backups, log files, OS litter, duplicate copies) and produce a sized, grouped cleanup report. Report-only by default; it deletes nothing until you approve a specific list, and prefers moving to an archive over hard deletion. Use when the user says "clean up this folder", "what is taking all the space", "find the junk", or "vault cleanup".

jqaisystems Bundle

Lint copy against a brand voice guide. Scans files for em dashes, buzzword clusters, hedge language, vague superlatives, passive voice, exclamation marks, and AI-tell phrases, then reports every violation with a suggested rewrite. Report-only by default, applies fixes on request. Use when the user says "lint this copy", "check this against our voice", "does this sound like us", "voice check", or "clean the AI tells out of this".

jqaisystems Bundle

Curate public-source links, saved notes, newsletters, documentation updates, release notes, market signals, and research snippets into safe daily or weekly briefs with source tracking, public/private visibility labels, archive decisions, and human review. Use when the user asks to make a research brief, summarize saved links, build an AI news digest, organize reading notes, create a public-safe source roundup, prepare a weekly intelligence brief, or separate public-ready notes from private research without exposing credentials, raw prompts, logs, local paths, account data, client material, or private source lists.

nimbusxr Bundle

Create spot report markers with military categorization

mchittineni Bundle

Performance engineering with k6 and Locust: load, stress, spike and soak profiles, virtual users (VUs), latency percentiles (p95/p99), threshold-gated tests in CI, and bottleneck profiling. Use when writing a k6 or Locust script, deciding whether an API can handle a peak traffic event, capacity planning before launch, or investigating why average latency looks fine while users report slowness.

navanithans Bundle

PDF text extraction, form filling, and merging using pypdf and pdfplumber.

navanithans Bundle

Token optimizer subagent. Summarizes large text into dense JSON or minimal Markdown.

alti3 Bundle

Configure Litestar OpenAPI schema generation and documentation UX with `OpenAPIConfig`, route-level schema metadata, schema generation controls, operation customization, UI render plugins, and documentation endpoint strategy. Use when API contract and docs quality must be implemented or corrected, especially for request, auth, and metrics surfaces. Do not use for runtime business logic changes unrelated to schema or documentation.

phazurlabs Bundle

Client-facing design deliverables: proposals, SOWs, case studies, pitch decks, pricing calculators, project briefs, and handoff documentation. Use when packaging design work for a client, an executive, or a portfolio — the artifact that leaves the team, not the interface itself.

popup-studio-ai Skill

Unified PDCA cycle management — plan, design, do, analyze, iterate, report. PDCA runs per-feature (9-phase: pm→plan→design→do→check→act→qa→report→archive); for multi-feature scope/budget grouping use /sprint (v2.1.13, 8-phase container that may host PDCA cycles inside). Triggers: pdca, plan, design, analyze, report, status, next, iterate

popup-studio-ai Bundle

Sprint Management — generic sprint capability for ANY bkit user. 16 sub-actions: init, start, status, watch, phase, iterate, qa, report, archive, list, feature, pause, resume, fork, help, master-plan. Triggers: sprint, sprint start, sprint init, sprint status, sprint list, master plan, multi-sprint plan, sprint master plan

popup-studio-ai Skill

CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis

rikilamadrid Skill

Report a compact read-only snapshot of the current Pathfinder work session.

rikilamadrid Skill

Choose the canonical ticket store when it is not local Markdown.

vchelaru Skill

Tweening / interpolation in FlatRedBall2. Use when animating a float over time with an easing curve — position, scale, alpha, rotation, UI slide-in, hit-flash, juice. Covers Entity.Tween vs Screen.Tween, lifetime rules, and the required usings.

vchelaru Skill

Animation Editor — Documentation Screenshots