Docs & writing
16,632 rows, by stacks then stars
3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid
lossless-group/lossless-agent-skills/open-graph-share-seo-geo Skill
4★ repoHow to make a page unfurl reliably in iMessage, WhatsApp, Slack, Discord, LinkedIn, and X; surface to search engines via sitemap.xml + robots.txt; and stay legible to generative engines (GEO), including the llms.txt standard for LLM corpus ingest. Use when adding or debugging OpenGraph / Twitter Card metadata, picking an OG image format, choosing where to host the image, fixing pages that "won't unfurl", auditing share previews, scaffolding /llms.txt and /llms-full.txt, or adding @astrojs/sitemap + robots.txt to a splash or marketing site. Encodes the JPEG-over-WebP rule, the ImageKit content-negotiation gotcha, the absolute-URL requirement, the og:image:type-must-match-bytes invariant, the cache-busting recipe for forcing a re-unfurl, the prose-in-markdown source-of-truth pattern for llms.txt, and the sitemap filter that keeps non-HTML routes (llms.txt, 404) out of the search-engine index.
emmanuelperu/microcks-skills/skills/microcks-openapi-mocking Skill
4★ repoWrite OpenAPI examples that work with Microcks dispatchers for API mocking. Covers example pairing rules, JSON body dispatching, Groovy script dispatching, and dispatcher configuration via the Microcks API.
Yugpat1835/awesome-copilot-cowork-skills/skills/project-management/project-status-tracker Skill
4★ repoMaintains living project files (project.md, decisions.md, risks.md, links.md) in a per-project OneDrive folder from emails, Teams channels and meeting transcripts, and generates a weekly DRAFT status document in Word. Use when the user asks to set up tracking for a project, update a project's status files, log a decision or risk, or produce a weekly status report for a named project.
The same file is in 1 other repository
Yugpat1835/awesome-copilot-cowork-skills/skills/reporting-analysis/report-attachment-analyzer Skill
4★ repoTracks a recurring emailed report end to end. It finds new report emails in the inbox, extracts data from their attachments, appends each reporting period to a trends spreadsheet, and rewrites a summary document with period-on-period deltas and flagged anomalies. Use when the user asks to update or analyse trends for a report that arrives by email on a schedule, or asks what changed in the latest weekly or monthly report.
The same file is in 1 other repository
Yugpat1835/awesome-copilot-cowork-skills/skills/sales-bd/estimate-to-sow Skill
4★ repoConverts a priced estimate spreadsheet into a populated statement of work document using the user's own SOW template. Validates that line items, hours, rates and totals add up before drafting, flags every discrepancy, and produces a DRAFT-labelled Word document plus a validation report. Use when the user asks to turn an estimate, quote or pricing spreadsheet into an SOW, statement of work, or scope document.
The same file is in 1 other repository
Yugpat1835/awesome-copilot-cowork-skills/skills/writing-communication/write-like-me Skill
4★ repoBuilds a personal voice profile from roughly 90 days of the user's sent email and meeting transcripts, then drafts emails and documents that match how the user actually writes. Use when the user asks to write like me, match my voice or tone, build or refresh my voice profile, or wants an email or document drafted in their own style.
The same file is in 1 other repository
FelixGraeber/claude-aso-audit-skill/skills/aso-localization Skill
4★ repoASO audit skill pack for Claude Code: audit App Store and Google Play listings, keywords, metadata, visuals, reviews, and competitors.
lukedj78/dev-flow/design-md-to-app Skill
4★ repoGenerate or customize a frontend application from a DESIGN.md (Google design.md spec). Reads the YAML tokens + markdown rationale and produces a working React app whose theme, typography, spacing, radii, and components are pre-styled to match. **Canonical target: Next.js 16 + App Router** (Pages Router or pre-16 explicitly refused). Supports four UI libraries: shadcn/ui (Tailwind + copy-pasted source), Base UI (Tailwind + headless library, no CLI overhead), MUI (runtime themed, Material-flavored), and Coss/UI (Cal.com design system on Base UI via the `@coss/*` shadcn registry, hands off to the `coss-ui` skill). Supports two form libraries: **TanStack Form + Zod (default, recommended)** or react-hook-form (opt-in). Integrates with the dev-flow contract: when a `.workflow/` exists, reads `meta.json#stack`, writes the app at the project root (alongside `.workflow/`), and bumps phase to `scaffolded`. Use whenever the user has a DESIGN.md and wants to scaffold an app, set up a theme, customize shadcn/Base UI/MUI from these tokens, or "use this DESIGN.md to start an app". Trigger on "DESIGN.md → app", "scaffold from design.md", "applica il DESIGN.md a shadcn / Base UI / MUI", "crea l'app dal DESIGN.md", "init shadcn con questo DESIGN.md". Always ask shadcn vs Base UI vs MUI (with a suggestion) before generating, unless `meta.json#stack.ui` already specifies one. Always defaults to Next.js 16 + App Router for the framework. Not for: scaffolding mobile apps (use rn-bootstrap for Expo + RN), writing PRDs (use prd-from-idea), or generating individual pages after the scaffold exists (use screenshot-to-page).
lukedj78/dev-flow/eve-registry-porting Skill
4★ repoPort a component (tool, connection, or skill) from a public eve/Flue agent registry — atomeve.dev, evex.sh, agentcn, eveagents.dev, the "shadcn for agents" registries — into a multi-tenant eve app WITHOUT adopting the registry's standalone-agent runtime model. Use when the user wants to "install / use / borrow an agent from atomeve (or evex / agentcn / eveagents)", "add a Stripe/PostHog/Sentry/GitHub tool or connection from a registry", "reuse a skill from a shadcn-for-agents registry", or asks whether a registry agent is usable and how to adapt it. The skill's core is the conformance checklist that makes third-party eve code safe in a multi-tenant app: tenant from the verified session (never model input), companyId in every query, per-tenant encrypted secrets (never global env keys), verified npm deps only, sensitive actions behind tool-grants/approval. For AgentOS specifically it defers to docs/eve-registries.md. Not for: scaffolding a fresh tool/connection/skill slot from scratch (use `eve-agent` for the boilerplate), building the Next.js app or its pages (use design-md-to-app / screenshot-to-page / module-add), or wiring the monorepo (monorepo-bootstrap). This skill governs "what to port from a registry and how to make it tenant-safe", not "how to write an eve primitive".
lukedj78/dev-flow/linear-scrum Skill
4★ repoTake a dev-flow project into Linear and run it with agile scrum. Creates/links a Linear Project under the workspace team, pushes `.workflow/tasks.md` into issues (story-point estimates, `area:web`/`area:agent` labels, milestones), sets up cycles/sprints (2-week cadence), and keeps Linear as the source of truth: sync pushes only new tasks, pulls status/velocity, plans the active sprint up to the velocity target, and reports. Triggers: "porta il progetto in Linear", "crea le issue in Linear", "setup scrum", "pianifica lo sprint", "report di velocity", "adotta questo progetto in Linear", or dev-flow routing from `prd_drafted`/`tasks_split`. Modes: Setup (new project), Adopt (existing Linear project), Sync (ongoing). Not for: writing or estimating the tasks themselves (use `prd-to-tasks`), building the app or agent (use design-md-to-app / eve-agent), or the headless server loop wiring (see docs/loop-engineering.md).
lukedj78/dev-flow/prd-from-idea Skill
4★ repoTurn a raw product idea (a paragraph, a Notion dump, a half-formed thought) into a structured PROJECT.md (high-level brief) and PRD.md (product requirements document) inside a project's `.workflow/` folder, following the dev-flow contract. Use when the user pastes a product idea and says "let's plan this", "draft a PRD", "what would this look like as a project", or starts a new project from scratch. Also use when a `.workflow/` exists at phase `empty` or `idea_captured` and the orchestrator routes here. Not for: writing code, designing UI, or producing task lists (those are downstream skills).
lukedj78/dev-flow/rn-write-tests Skill
4★ repoUse to write tests for an Expo + RN app: Jest + React Native Testing Library for unit/integration (components, hooks, queries, mutations) and Maestro for end-to-end flows (sign-in, navigation, forms). Sets up the testing stack on first call (jest-expo preset, RNTL, jest config) and writes a focused test next to the source file. Triggers on: "write tests for X", "add e2e test", "mock expo-notifications", "test this hook". Not for: choosing what to test (the user decides), running the existing test suite (just `npm test`), or testing pure logic outside an Expo project.
lukedj78/dev-flow/write-tests Skill
4★ repoWrite Vitest unit/integration tests OR Playwright e2e tests for an existing source file (server action, page, component, query). Reads the project's wired test framework from `.workflow/meta.json#stack.test`, follows the mocking patterns already present in `vitest.setup.ts` and any sibling test files. Use when the user says "scrivi i test per X", "test per la server action Y", "e2e per /clienti", "unit test per il componente Z", "add tests for <file>", or after `screenshot-to-page` / `module-add` runs and the user wants coverage. Not for: scaffolding the test infrastructure (`module-add test`), running QA on a deployed site (`qa`), or methodology guidance (`superpowers:test-driven-development`).
khshanovskyi/custom-agent-skills/api_demo/_skills/style-guide Skill
no license4★ repoEnforces brand voice, tone, and writing style rules. Use when the user asks to write, rewrite, edit, proofread, or review any text — blog posts, emails, social media copy, product descriptions, or support replies. Also use when the user asks about tone, style, or brand writing guidelines.
sandover/agent-skills/skills/strike-valley-docx Skill
no license4★ repoConvert Markdown into polished, branded Strike Valley Studio DOCX documents that remain editable in Pages or Word. Use when the user wants a consultancy-style report, proposal, memo, or assessment from Markdown, especially when cover design, bullet fidelity, TOC layout, page furniture, or Pages compatibility matter.
composite/korean-skills/skills/kordoc-parse-document Skill
4★ repoUse when converting Korean document files into readable text with `npx` and kordoc. Covers HWP, HWPX, and PDF parsing to Markdown or JSON, including metadata, outline, warnings, and page count. Trigger for requests such as reading a government document, extracting document contents, summarizing a Korean office file, or parsing a local .hwp/.hwpx/.pdf with `kordoc:parse_document`.
ntaffzii/Skill-Agents/skills/obsidian/obsidian-markdown Skill
4★ repoCreate and edit Obsidian flavored Markdown notes with wikilinks, embeds, callouts, properties, tags, comments, highlights, footnotes, Mermaid, and Obsidian-specific syntax. Use when working with Obsidian .md notes, vault content, wikilinks, callouts, frontmatter, tags, or embeds.
ntaffzii/Skill-Agents/skills/productivity/automation-design Skill
4★ repoDesign Codex automations, scheduled research jobs, recurring reports, reminders, monitors, thread follow-ups, and workspace jobs. Use when the user asks to set up, improve, schedule, template, audit, or design an automation, monitor, reminder, or recurring Markdown report.
ntaffzii/Skill-Agents/skills/productivity/grill-with-docs Skill
4★ repoPlanning interview skill that asks sharp questions before execution and turns decisions into durable project docs, domain language, PRDs, or ADR notes. Use when the user has an idea, feature, plan, product change, or unclear request that needs alignment before implementation.
ntaffzii/Skill-Agents/skills/productivity/markdown-report Skill
4★ repoCreate clean Markdown reports, summaries, research briefs, project notes, RCA writeups, meeting summaries, decision records, and handoff documents. Use when the user asks to write, format, summarize, document, report, brief, or create a Markdown deliverable.
ntaffzii/Skill-Agents/skills/research/daily-news-report Skill
4★ repoResearch current news and create concise sourced daily briefings, market updates, AI news reports, Thailand news summaries, or scheduled news digests. Use when the user asks for daily news, current events, latest updates, recurring news reports, or news monitoring.
cilidinezy-commits/doc-harness/skill Skill
4★ repoDocument-based project control that lets any AI agent or human resume work from files alone — no external memory needed. Use this skill whenever the user wants to structure a long-running project, track progress across sessions, recover state after context loss, coordinate multiple agents on the same project, audit project documentation health, or stop forgetting what was done last session. Triggers include: '/doc-harness init' and '/doc-harness check' (explicit slash commands); requests like 'help me set up this project', 'I keep losing track', 'my agent forgets between sessions', 'organize my project docs', 'audit this project', 'check the documentation', 'what did we do last time'; multi-week projects (theses, research, analyses, software modules) that span many sessions; cross-project coordination (inbox/outbox for file-based messages between projects).
Adri3l-R3nan/cognify-skills/.github/skills/process-documentation Skill
no license4★ repoCreates clear, maintainable process documentation including standard operating procedures (SOPs), workflow diagrams, decision trees, and runbooks. Use when documenting business processes, creating training materials, or building operational playbooks.
Dragoon0x/dragoon-skills/skills/brief Skill
4★ repoGenerate a structured product brief markdown from a one-line idea, pre-filled with codebase facts (stack, type system, palette, components count) from dragoon.json. Use when the user is starting a new feature, project, or initiative and wants to think through it before coding. Output goes to .dragoon/plans/brief-{slug}-{date}.md. Defaults to dry-run preview; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/brief/scripts/brief.js "<idea>"`.
Dragoon0x/dragoon-skills/skills/docs Skill
4★ repoDetect drift between markdown docs (README, docs/) and the actual codebase. Catches references to npm scripts that don't exist, scoped dependencies not in package.json, file paths in backticks that don't resolve on disk, and undocumented npm scripts. Use to audit documentation hygiene before a release or after a major refactor. Exits non-zero on findings. Run as `node ~/.claude/skills/dragoon/skills/docs/scripts/docs.js`.
Dragoon0x/dragoon-skills/skills/handoff Skill
4★ repoGenerate a markdown dev handoff doc with everything the next engineer needs - stack, design tokens, palette, type scale, spacing grid, motion, existing components, and conventions - all pulled from dragoon.json. Use when handing off work to another engineer or documenting the codebase for new contributors. Output goes to .dragoon/handoff/handoff-{slug}.md. Defaults to dry-run; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/handoff/scripts/handoff.js [feature]`.
Dragoon0x/dragoon-skills/skills/plan-eng Skill
4★ repoGenerate a structured engineering plan markdown for an idea, pre-filled with codebase facts (stack, dependencies, current critique score) from dragoon.json. Forces a test matrix, edge cases, migration plan, and review checklist. Use after /brief or before any non-trivial feature implementation. Output goes to .dragoon/plans/plan-eng-{slug}-{date}.md. Defaults to dry-run; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/plan-eng/scripts/plan-eng.js "<idea>"`.
wicttor/pwrl/pwrl-review-report Skill
no license4★ repoGenerate comprehensive review report and determine final approval status.
AltrinaAI/vibestudio/examples/xlsx Skill
4★ repoUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
The same file is in 29 other repositories
ThanhNguyxnOrg/blendops/skills/intent-to-3d-brief-writer Skill
4★ repoConvert a non-Blender-user's natural-language request into a structured 3D brief (subject, mood, deliverables, constraints, evidence expectations). Use as first step before any planner.
Non blender user response writer
ThanhNguyxnOrg/blendops/skills/non-blender-user-response-writer Skill
4★ repoConvert technical Blender workflow findings into plain-language user-facing responses with honest caveats.
Preview report template writer
ThanhNguyxnOrg/blendops/skills/preview-report-template-writer Skill
4★ repoGenerate the structured preview-report Markdown that glb-web-handoff and non-blender-user-response-writer consume after a render or export run.
ThanhNguyxnOrg/blendops/skills/runtime-attempt-report-writer Skill
4★ repoProduce an evidence-bound runtime attempt report with truth labels and next steps; does not certify upstream stack success.
tbc-servicos/dataagile-agent-kit/protheus/skills/documentation-writer Skill
4★ repoGenerate ProtheusDOC comment blocks for AdvPL and TLPP source code. Use when a user says "document this function", "add ProtheusDOC", "write documentation block", "document this class/method", or needs structured source-code documentation following the Protheus.doc standard for functions, classes, methods
tbc-servicos/dataagile-agent-kit/protheus/skills/entry-point-designer Skill
4★ repoDesign and document Protheus Entry Points (Pontos de Entrada). Always generates TLPP by default; only generates AdvPL (.prw) when the user explicitly requests AdvPL. Covers User Function signatures, PARAMIXB parameter layouts, return value specifications, and ProtheusDOC documentation. Use when user says 'create entry point', 'ponto de entrada', 'PARAMIXB', 'User Function hook', 'ponto de entrada TLPP', 'ponto de entrada ADVPL'.
tbc-servicos/dataagile-agent-kit/protheus/skills/writer Skill
4★ repoGera código ADVPL/TLPP para Protheus seguindo obrigatoriamente: nomenclatura de arquivo R[MOD][TYPE][SEQ].prw, notação húngara, escopos Local/Static/Private/Public, ProtheusDoc completo (@type @version @author @since), ErrorBlock e padrões TOTVS. Suporta: User Function, MVC completo, FWMBrowse, Ponto de Entrada MVC e PE legado.
stephenrogan/augmented-csm/skills/pillar-3-communication-content/cc-internal-brief-writer Skill
4★ repoCreates internal account briefs, escalation write-ups, and executive summaries for internal audiences. Compiles cross-system data into standardised formats for leadership reviews, cross-functional meetings, and escalation documentation. Adapts content and detail level to the specific audience. Use when asked to write an escalation brief, prepare an internal account summary, create a leadership report on an account, or document an escalation. Also triggers for questions about internal documentation, escalation reports, account status summaries for managers, or cross-functional context documents.
stephenrogan/augmented-csm/skills/pillar-3-communication-content/cc-report-generator Skill
4★ repoProduces weekly, monthly, and quarterly reports for CSMs, managers, and leadership by aggregating data from all pillar skills into formatted, distributable reports. Adapts content, detail, and emphasis by audience. Use when asked to generate a CS report, build a weekly summary, create a portfolio report, produce a dashboard update, compile metrics for leadership, or when any recurring reporting need should be automated. Also triggers for questions about CS reporting, metrics compilation, dashboard data generation, performance summaries, or NRR reporting.
stephenrogan/augmented-csm/skills/pillar-4-product-adoption/pa-feedback-aggregator Skill
4★ repoAggregates product feedback from support tickets, call transcripts, surveys, and CSM notes, then clusters into themes for the product team. Produces weighted reports showing which issues affect the most customers and the most revenue. Use when asked to collect customer feedback, aggregate feature requests, theme product feedback, build a voice-of-customer report, identify common product gaps, or when any workflow needs structured feedback data for the product team. Also triggers for questions about customer feedback analysis, feature request patterns, product improvement priorities, or voice of customer reporting.
celigo/ai/skills/writing-handlebars Skill
4★ repoWrite Handlebars template expressions for Celigo integrations -- dynamic values in mappings, HTTP bodies, SQL queries, URIs, and filters. Use when building any resource configuration that needs computed, conditional, or formatted field values.
celigo/ai/skills/writing-mappings Skill
4★ repoWrite field mappings and transforms in Celigo integrations. Covers Mapper 2.0 (imports), Transformation 2.0 (exports), lookups, response mapping, and Mapper 1.0 (NetSuite/Salesforce). Use when editing mappings[], transform{}, responseMapping, or lookup configurations.
celigo/ai/skills/writing-scripts Skill
4★ repoWrite Celigo JavaScript hook scripts -- preSavePage, preMap, postMap, postSubmit, postResponseMap, filter, transform, branching, handleRequest. Use when creating or editing scripts, choosing the right hook point, understanding input/output data shapes, or debugging script behavior.
celigo/ai/skills/writing-sql Skill
4★ repoWrite SQL queries for Celigo RDBMS exports and imports -- SELECT, INSERT, UPDATE, UPSERT, MERGE, delta, once, and bulk operations across Snowflake, Postgres, MySQL, SQL Server, Oracle, BigQuery, and Redshift. Use when editing rdbms.query or troubleshooting SQL errors.
YuanshengClaw/yuansheng-kit/plugins/trace/skills/write-root-cause-blueprint Skill
no license4★ repoProduce and semantically review evidence-grounded Yuansheng Root Cause Blueprint v1-lite candidates from validated perf evidence and a confirmed hardware profile. Use when Yuansheng Trace requests a per-function Blueprint candidate or an independent review of one.
mondaycom/skills/skills/project-status-report Skill
4★ repoGenerates structured project status reports from monday.com - a customizable AI work platform with dedicated products for work management, CRM, dev, service, and campaigns. Surfaces overdue items, blockers, workload distribution, and recent activity across one or more boards. Use when user asks for "project status", "board summary", "what's overdue", "status report", "how's the project going", "weekly update", "board overview", "progress update", or "team workload".
The same file is in 1 other repository
fabienjuif/agentic-skills/plugins/fabien-skills/skills/fix-stale-doc Skill
3★ repoFull-repo documentation sweep. Fans out one sub-agent per module / docs subdir / README cluster to (1) fix stale claims that no longer match the code, (2) remove duplication, and (3) compact verbose prose. Use when the user runs "/fix-stale-doc", asks to "fix stale docs", or "clean up documentation".
JakubKontra/skills/vulniq Skill
3★ repoAutonomous security vulnerability scanner for codebases. Detects secrets, XSS, missing security headers, auth issues, OWASP Top 10 patterns, dependency vulnerabilities, PII exposure, CORS misconfiguration, and more. Aligned to OWASP APTS (Autonomous Penetration Testing Standard) Foundation tier. Outputs SARIF JSON, Markdown report, and APTS Conformance Claim. Use when the user wants a security audit, vulnerability scan, pen-test preparation, or code security review.
lantisprime/claude-sdlc/skills/docs Skill
3★ repoUse this skill at the end of any phase that changed SDLC artifacts to update the SDLC documentation tree — the artifact index, requirements traceability matrix, architecture manifest, changelog, and any user-facing docs affected by the change. Also trigger when the user says "update docs", "refresh the index", "regenerate the traceability matrix", or after a deployment completes.
lantisprime/claude-sdlc/skills/gate-signoff Skill
3★ repoUse this skill to capture a human phase-gate sign-off through chat rather than requiring the user to manually edit the gate markdown file. Prompts the user with the artifact path, collects a work-item URL (REQ / ticket / CR) as the non-trivial acknowledgment, validates the URL shape against the ticket system configured in `config/tools.json`, and writes the signed gate file at `.claude/sdlc/gates/<phase>-<task-slug>.md`. Invoked at the end of `/plan`, `/analyze`, `/design`, `/build`, `/test`, and `/support`. Deliberately NOT invoked by `/deploy` or `/fix-fast` — those still require the human to open and edit the gate file by hand. `/docs` has no dedicated gate file and does not invoke this skill.
lantisprime/claude-sdlc/skills/test Skill
3★ repoUse this skill during Phase 5 to execute functional tests, record results, log defects, and validate UX conformance. Logs defects to Git Issues when available, otherwise to markdown (or JSON, per config) under .claude/sdlc/defects/. Reports code coverage against the configured threshold. Triggered after build is signed off and before deploy. Also trigger when the user says "run tests", "report coverage", "log defects", or "validate UX".
raphaelDkhn/worldbuilder/founder-fit Skill
no license3★ repoAnswer "why YOU." Interviews the user on lived experience, obsessions, unfair advantages, and lived problems in their chosen domain. Produces a Three Proof Points document grounded in specific stories — not credentials. Rejects titles-and-employers positioning. Use when asked to "why should I be the one", "founder-market fit", "why me", "what's my unfair advantage", "founder positioning", "am I the right person", or "why this founder". Proactively invoke this skill (do NOT answer directly) when the user expresses doubt about whether they are the right person to solve a problem, or when they have a North Star but no articulated reason they are uniquely positioned for it. Use after /north-star and before /memo, /hypothesis. (worldbuilder)
raphaelDkhn/worldbuilder/hypothesis Skill
no license3★ repoArticulate one testable core hypothesis. Breaks complex problems into components answerable in weeks, not months. The gatekeeper for the worldbuilding validation phase — /demo, /memo, and /mom-test all refuse to proceed without a live hypothesis.md. Use when asked to "form a hypothesis", "what should I test", "write a hypothesis", "what's my core bet", "I need to validate this", or "how do I know if this is real". Proactively invoke this skill (do NOT answer directly) when the user is trying to run /demo, /memo, or /mom-test but has no articulated hypothesis, OR when they're stuck between "ideas" and "action" and need a single falsifiable claim to test. Use after /kill-darlings and before /demo, /memo, /mom-test. (worldbuilder)
raphaelDkhn/worldbuilder/memo Skill
no license3★ repoDraft top-down artifacts — a written memo articulating how the world changes and why the user is uniquely positioned to catalyze it. Forces TAM analysis, market players comparison, failed-founder research, market-share revenue math. The audience is the user's future self at 5 years, not investors. Refuses to proceed without hypothesis.md. Use when asked to "write a memo", "thesis memo", "worldbuilder memo", "write my thesis", "what's my argument", "draft the top-down", or "articulate my bet". Proactively invoke this skill (do NOT answer directly) when the user has a hypothesis but no written argument for why this bet is worth 5-10 years of their life. Use after /hypothesis, pairs with /demo. (worldbuilder)
broomva/skills/skills/cadence/drift-check Skill
3★ repoCompares stated priorities against where time and effort actually went, and produces a strategy drift report. Uses git log, vault priorities, and project docs to detect misalignment. Use when the user says "drift check", "am I on track", "priority alignment", "where did my time go", "strategy drift", or wants to audit focus vs intention.
broomva/skills/skills/design/tekton Skill
3★ repoTekton — the shared architecture-intent substrate for co-designing systems with the agent. One typed graph across six tiers (system / journey / data / infra / decisions / qualities); views are queries, not separate diagrams. The canonical artifact is a diff-friendly YAML model both human and agent read and write; it renders to Mermaid (agent-legible, GitHub-native) and a self-contained tabbed HTML viewer (human-visual). Cross-tier traceability (`tekton query <from> <to>`) answers "which infra does this user-journey step touch?" as a path query. USE WHEN: designing or thinking deeply about architecture, a system, a data model, user journeys/flows, or a technical plan WITH the agent; when a Category-C HTML doc isn't enough because you need to see AND edit AND traverse the design across tiers; "let's design X", "architect this", "model the system", "draw the flow", "how does this fit together", "diagram this", "/tekton". NOT FOR: a one-off throwaway diagram (use Mermaid inline); prose-only ADRs (write the ADR); implementation itself. Triggers on: design architecture, model the system, user journey, data model, tekton.
broomva/skills/skills/knowledge/kg Skill
3★ repoLoad relevant entities from the bstack knowledge graph (research/entities/) for a given topic. Two-tier scoring: tier-1 (catalog-only, ~5ms — slug + tags + claim + links + sources match against docs/knowledge-index.md) is the fast first pass and the only stage for high-confidence exact-slug/tag queries; tier-2 (body-grep fallback, ~300ms — auto-fires when tier-1 returns < N matches OR its best hit is below the confidence floor, default 18) recovers topics whose vocabulary appears in entity prose but not the dense catalog (hit rate jumps from 70% → 100% on representative queries; this is hit rate ≥1, not true recall@N). Surfaces top-N entity bodies as a single context block the agent reasons over. This is a LOAD skill, not a query DSL — querying is what the agent does once loaded. Implements the LLM-as-index architecture (BRO-1223): substrate canonical, one projection (catalog) routes, agent IS the query engine. Empirical: peak per-query context drops from 29% → 4.6% of 1M (6.3× reduction); cumulative session tokens 23.8× fewer over 10 queries. Default N=10 entities; override with --n. Tier-2 auto-fires on few-OR-weak tier-1 hits (confidence gate, default --tier2-floor 18; BRO-1426 lifts R@5 0.871→0.952, MRR 0.868→0.968 with no flag); force unconditionally with --body-search, disable the gate with --tier2-floor 0. Routing-quality flags (BRO-1422): --terms (query expansion — score agent-supplied synonyms/variants alongside the topic), --expand 1 (graph 1-hop — also load related: neighbours of top hits, capped at --n extra, total ≤ 2x--n), --explain (per-signal score trace); hub-aware tiebreak always on. Output: catalog header + ranked entity blocks with full body. USE WHEN load knowledge graph, kg load, load entities, route to entities, load context for, what do we know about, what entities are relevant to, surface knowledge on, browse the graph for, find entities about, semantic load, topical load, agent-as-index load. NOT FOR PAI session retrieval (use ContextSearch), web research (use Research), Knowledge Archive ingest (use Knowledge), or entity write/edit operations (those are direct Read+Edit + commit per the AGENTS.md §P6 sub-rule on substrate-edit-as-inference-persistence).
broomva/skills/skills/orchestration/governed-autonomy-loop Skill
3★ repoTurn any work-queue + any enforcement pipeline into a self-driving, self-healing, human-minimal autonomy loop with a control-systems safety envelope. A prose-defined governor closes a feedback loop over the queue, drives isolated worktree arcs to Done, is metacognitive (defers when the runtime can't support the act, escalates only when genuinely blocked, self-heals when the block clears), and NEVER performs the irreversible act itself — it delegates every merge/deploy/publish to an isolated arc gated by adversarial review + a policy gate + a server-side aggregate check. The controller is a markdown prompt interpreted fresh each tick; a thin tested shell (tick.sh) only schedules, locks, and logs. The skill SCAFFOLDS + GOVERNS a new loop instance: the invariant spine stays fixed, four adapters (tracker / irreversible-act + enforcement / runtime / partition) are per-instance, the deterministic core (scheduler, in-flight fold, reseed gate, config + denylist validation) is extracted into tested scripts, and the latent decisions stay prose with scenario evals. Generalizes the proven broomva ticket-dispatch governor (BRO-1740 + BRO-1833). USE WHEN setting up an autonomous ticket/PR/deploy loop, standing up a governor that drives a queue unattended, building a self-merging arc pipeline, adding a metacognitive control loop over background agents, or the user says "governed autonomy loop", "autonomy loop", "self-driving loop", "ticket-dispatch governor", "loopcast", "loop-caster", "set up an autonomous governor". NOT FOR a single in-session autonomous task (use /autonomous), a one-shot background watcher (use P9 wait), or a cross-session single-agent restart loop with no queue (use P12 persist) — this is the external-trigger, across-session, queue-driven, irreversible-act-gated quadrant.
broomva/skills/skills/orchestration/handoff Skill
3★ repoFresh-session handoff doc drafting. Produces a stable, single-file human-readable narrative state for the NEXT agent context (fresh session, after `/clear`, after persist iteration, after a tab close). The artifact lives at `docs/handoffs/YYYY-MM-DD-<arc>.md` and follows a stable shape: TL;DR + State-of-the-world (P15 snapshot) + What-was-delivered (PR table with SHAs) + First action + Pickup state. Distinct from P12 persist's `PROMPT.md` (machine-state for cross-context loop) and the P1 Bridge session log (raw transcript) — the handoff is the narrative bridge a human reads in ten seconds and a fresh agent reads in thirty. Use when: (1) ending a substantive session that another agent will continue, (2) preparing a fresh-session pickup point mid-arc, (3) needing to compress a multi-PR arc into a single resumable document, (4) the user says "write a handoff" / "fresh-session handoff" / "let me come back to this tomorrow". Triggers on "handoff", "fresh-session", "fresh session", "pickup", "where we are", "leave off", "for the next session", "resume tomorrow", "stage continuation", "for the next agent".
broomva/skills/skills/publishing/blog-post Skill
3★ repoFull-stack blog post production — turns a topic, idea, or brief into a complete publishing package across written, social, and multimedia surfaces. Generates broomva.tech .mdx posts (or Substack/other long-form), X posts and threads, LinkedIn posts, Instagram posts and reel scripts, plus multimedia asset plans (images, video, audio, GIFs). Outputs a structured content package to /broomva/posts/. Use when: (1) creating a new blog post or article, (2) turning an idea into multi-platform content, (3) producing a content package for a topic, (4) writing and distributing a post across channels, (5) generating social content from a long-form piece. Triggers on: 'blog post', 'new post', 'write a post about', 'content package', 'publish about', 'create post', 'blog-post'.
broomva/skills/skills/publishing/content-creation Skill
3★ repoFull-stack content creation pipeline: idea or reference to published blog post, audio narration, video, and social media distribution. Orchestrates research, reference extraction, storytelling, AI visual assets (Nano Banana, Veo 3.1), TTS audio (Voicebox, kokoro-tts, Edge TTS), Remotion video, and social copy into a complete content package. Use when: (1) creating a blog post, case study, or writing entry, (2) turning an idea or experience into structured narrative, (3) using a reference post/video (X, LinkedIn, YouTube) as inspiration, (4) generating visual content (AI images, clips, screenshots, GIFs), (5) generating audio narration for posts, (6) creating social media content (X threads, Instagram carousels) from long-form writing, (7) packaging and distributing content across platforms. Triggers on 'new post', 'blog post', 'case study', 'content creation', 'write about', 'content pipeline', 'social content from post', 'use this as reference', 'generate audio', 'tts', 'narration'.