Docs & Writing

warpdotdev Skill

Weekly sentiment summary of <BRAND>'s social mentions with week-over-week comparison using Octolens. Produces a Slack-ready report with sentiment score, highlights, lowlights, notable patterns, and competitor context. Use when the user asks for a weekly sentiment report, weekly social summary, or "how did mentions look this week".

withkynam Bundle

Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.

fearvox Skill

Product design, technical design documents, user-facing copy, specs, diagrams, and handoff documentation.

fearvox Skill

Post-change documentation sync for decisions, synthesis, skill maps, release notes, and durable handoffs.

cfregly Skill

Copy this directory to plugins/profile-and-optimize/skills/<your-skill-name>/ and rewrite this description to be third-person + include WHAT the skill does and WHEN (specific trigger phrases). Max 1024 chars. Do NOT leave the word "template" in the real skill's description.

codeplain-ai Skill

Read a ***plain project — its `.plain` files, `test_scripts/`, `config.yaml`(s), and `resources/` — and determine every command-line tool, runtime, package manager, and external service the project needs on the host machine. Probe the host for each one, then emit a `PASS` / `FAIL` report listing what's installed (with versions), what's missing, and concrete OS-specific install commands for the gaps. Run this any time someone is about to render, test, or onboard onto a ***plain project for the first time.

fullrefit Bundle

Generate structured Standard Operating Procedures (SOPs) from process recordings, transcripts, voice memos, or freeform descriptions. Includes decision trees, error handling, time estimates, tools required, and success criteria. Use when the user wants to document a business process, turn a Loom/Zoom recording transcript into a formal SOP, or create onboarding documentation for team processes. MANDATORY TRIGGERS: SOP, standard operating procedure, document this process, create an SOP, process documentation, write up this process, procedure guide, turn this transcript into an SOP.

midudev Bundle

Use when investigating a bug, error, or regression in a Ruby on Rails codebase. Creates a failing RSpec reproduction test, isolates the broken code path, and produces a minimal fix plan. Trigger words: debug, broken, error, regression, stack trace, failing test, RSpec, bug report, Rails app.

alemtuzlak Bundle

Use when writing, editing, or organizing documentation, when planning what docs a feature needs, and whenever planning or implementing a new feature or change in a repo (docs ship with the code). Also use when tempted to write docs without showing the discovered readers to the user, without asking for tone, or without loading simple-english and i-have-adhd. Triggers on "write docs for X", "document this feature", "add a guide", "update the docs", "reorganize the docs", "plan feature X", "implement X", or /docs.

alemtuzlak Bundle

Use when the user wants to create presentation slides, a slide deck, a technical talk, or a conference talk for a topic or library — built on Slidev. Interviews the user, deep-researches and code-grounds the topic FIRST, applies presentation-craft best practices, generates a Slidev deck, self-verifies it in a headless browser, and ends with the dev server running and the deck open in the browser with zero manual steps. Triggers on "make a presentation", "make slides", "build a deck", "presentation about X", "technical talk", "conference talk", "slidev deck", "build slides for X", "present <library>".

alemtuzlak Bundle

Use when the user wants to turn a raw talking-head / screen-share recording into a finished, edited, annotated video plus a full content package. Removes silences, flags mistakes for the user to cut, transcribes, adds transcript-synced overlays (code, on-screen code highlights, word highlights, lists, comparisons, diagrams, section labels, punch-in zooms), renders with original audio, then generates blog/socials/YouTube content. Triggers on "produce a video", "edit my video", "annotate my recording", "/produce-video".

mia-cx Bundle

Upload a local file, screenshot, or piped output to the i.mia.cx R2 bucket and get back a public URL. Use when the user asks to upload, host, or share a file, wants a link to an image, screenshot, log, diff, or report, or when a result is easier to hand over as a URL than as inline text. Also covers listing and deleting previously uploaded objects, and configuring ShareX or ishare clients.

flagrare Skill

Generate a comprehensive, impact-framed brag-doc entry for a chosen time window (day, week, biweek, month, or custom). Pulls authored PRs, reviews given, commits, deploys, and linked tickets across GitHub, local git, and configured MCPs, then synthesises a themed narrative, leading with outcomes, quantifying impact, owning the work in first-person past tense, separating IC contributions from amplification, and naming the judgment exercised. Output is designed to drop straight into a developer journal, a personal bragging sheet, or a performance-review packet. Accepts a mode argument, `/flagrare:brag-doc resumancer` renders the output as ready-to-paste Resumancer CLI commands (`resumancer impact "..." --branch ...`) instead of markdown. Use whenever the user says "brag doc", "brag sheet", "what did I do this week", "weekly recap", "monthly recap", "performance review prep", "what should I tell my manager", "summarise my impact", "career log entry", "give me my wins", "biweekly recap", or any variant about look

flagrare Skill

Write documentation that reads like a person wrote it for another person. The skill teaches the craft layer first, how to set context, how to calibrate tone, how to escape the curse of knowledge, when prose beats a bullet list, and only then the structural conventions (Diátaxis modes, README landing-page arc). Use whenever you're writing or restructuring a README, a docs tree, a CONTRIBUTING file, a guide, an architecture document, or any other documentation surface.

flagrare Skill

Standup Report

flagrare Bundle

Build a month-by-month career impact timeline across an entire tenure (or any multi-month window), sweeping every available source (GitHub, issue tracker, Slack, Notion, meeting notes like Granola, the company BI/data platform, Datadog, Sentry) one month at a time, then attaching real product/technical/business metrics to every entry in "accomplished X, measured by Y, by doing Z" form. Use this whenever the user wants a tenure retrospective, a departure/offboarding impact record, "everything I did at this company", a promotion or performance-review packet covering many months, a year-in-review, or asks to add metrics/evidence to an existing career document. For a single day/week/month recap, use `/flagrare:standup-report` or `/flagrare:brag-doc` instead; this skill is for the long arc.

flagrare Skill

Generate a daily code review report showing stale PRs, items needing your attention, and active work for your team. Use whenever the user asks for a PR report, code review status, daily standup prep, team PR overview, "what needs review", "what's stale", "show me open PRs", "daily review", "PR check", "review report", "what should I look at today", or any question about tracking pull request activity across a team or pod. Also trigger when the user mentions a specific pod name that matches a saved config.

fernandoartalf Bundle

Standards and guardrails for authoring Business Central reports in AL and RDLC. Use when creating or modifying Report objects (.Report.al), RDLC layouts (.rdlc/.rdl), or request pages. Covers AL report structure, DataItem hierarchy, RDLC layout sizing, SetData/GetData index management, body width validation, and rendering best practices.

fernandoartalf Bundle

Extends the Business Central Report Selection framework with new custom Usage values and wires them into the standard printing workflow. Creates an enumextension on "Report Selection Usage" (global) or on an area-specific enum ("Report Selection Usage Sales", "Report Selection Usage Purchase", "Report Selection Usage Service"), optionally a dedicated Report Selections setup page filtered to the new Usage, an initialisation/install/upgrade codeunit that seeds a default Report ID without overwriting customer configuration, a Report Selection Management codeunit that reads Report Selections in Sequence order and calls Report.RunModal / SaveAsPdf, and page or page-extension actions that trigger the configured report. Use when the user asks to "extend Report Selection Usage", "add a new report selection category", "create a custom print action", "add my report to the Report Selections page", "hardcode replace Report.RunModal with a configured report", "add a Print document action driven by Report Selections", or "

fernandoartalf Bundle

Create well-structured Business Central feasibility analysis documents in the `openspec/analysis/` folder as the AL Analyst's working artefact backing a CCN, following the ANALYSIS-001 template structure. Captures references to the source user story / spec / CCN, change summary, scope & impact (objects added/modified, LoC, ID range usage), phased time estimate (Optimistic / Expected / Pessimistic with contingency and calendar duration), cost estimate at a stated EUR/h rate with assumptions, SWOT analysis (Strengths / Weaknesses / Opportunities / Threats), numbered risk register (`R-NN` with Likelihood / Impact / Mitigation), and a clear GO / NO-GO / CONDITIONAL-GO feasibility recommendation with non-blocking advisories and a handoff statement back to the Architect. Writes the file as `ANALYSIS-NNN-<kebab-title>.analysis.md` with frontmatter linking back to its spec, user story, and CCN. Use whenever the user asks to create, draft, generate, or write a feasibility analysis, ANALYSIS document, cost/time estimat

fernandoartalf Bundle

Convert markdown documents to professionally formatted Word (.docx) files using Python and python-docx. The skill parses the markdown into sections, creates a JSON file with all section values, then substitutes Placeholder tokens in a Word (.docx/.dotx) template with the JSON values. Mermaid diagrams emitted by the `documentation-bc-ccn-generator` skill as DIAGRAM-mermaid marker blocks are rendered to PNG via the Mermaid CLI (mmdc) and inserted inline at the corresponding location in the docx. Use when user requests to convert markdown to Word, create a docx from markdown, generate a release note document, export markdown as Word, or apply template to markdown conversion. Trigger phrases include convert markdown to docx, export md to Word, generate release note from markdown, create Word document from markdown, convert to docx with template, apply template to markdown, or when working with markdown files that need to be delivered as formatted Word documents.

fernandoartalf Bundle

Create well-structured Business Central release notes in the `docs/releasenotesmd/` folder from an approved spec, change-control note (CCN), or set of merged AL changes. Produces a single markdown release note with frontmatter (id, title, version, status, clientName, ccnNumber, issueNumber, releaseDate, releasedBy, module, createdDate, approvedDate), a fixed set of sections (Release Summary, Scope of Change, Change Request Details, Testing Setup, Testing Steps, Known Limitations, Approvals), and a sibling `*.releasenote.json` field map for downstream consumption by the `md-to-docx-converter` skill. No company, client, or publisher values are hardcoded — every identity field is either supplied by the user or read from the workspace `app.json`. Use whenever the user asks to create, draft, generate, or write a release note, RN, deployment note, change-request release document, or anything matching phrases such as "create release note", "draft release note for [client]", "generate RN from spec", "create release n

fernandoartalf Bundle

Create well-structured Business Central technical specifications in the `openspec/specs/` folder from approved user stories, following the SPEC-001 template structure. Decomposes an approved user story into a complete technical design with architecture overview, AL object inventory (tables, enums, pages, page extensions, codeunits, permission sets) with allocated IDs from the workspace `app.json` range and the correct affix, table field definitions, page layout notes, integration points with standard BC, testable technical acceptance criteria mapped back to the user-story ACs, a phased task breakdown, and per-phase implementation plan files under `openspec/plans/`. Verifies standard BC behavior via Microsoft Learn before assuming reuse. Use whenever the user asks to create, draft, generate, or write a technical spec, SPEC, architecture document, implementation plan, or asks to decompose / plan a user story for development, with trigger phrases such as "create a spec for US-NNN", "draft technical spec", "gener

kina2711 Bundle

Translate foreign-language books, documentation, web content and technical material into Vietnamese that reads as a domain expert wrote it, with a fixed glossary, style guide, fidelity review and translation memory. Use for translation or localisation into Vietnamese; route the authoring of new Vietnamese technical content to data-technical-content-and-social.

kina2711 Bundle

Create validated data documentation, ADRs, runbooks, postmortems, ERDs, BPMN, sequence, state, lineage and architecture diagrams. Use when the primary deliverable is a data document or technical diagram.

felixgeelhaar Skill

Senior content strategy and technical writing partner. Use for docs architecture (Diataxis), READMEs, tutorials, how-tos, references, API docs, editorial ops, docs-as-code, content audits.

gannonh Bundle

Capture an idea, task, or issue that surfaces during a Kata session as a structured issue for later work. This skill creates markdown issue files in the .planning/issues/open directory with relevant metadata and content extracted from the conversation. Triggers include "add issue", "capture issue", "new issue", "create issue", "log issue", "file issue", "add todo" (deprecated), "capture todo" (deprecated), "new todo" (deprecated).

gannonh Bundle

Analyze an existing codebase with parallel mapper agents, creating codebase documentation, understanding brownfield projects, or mapping code structure. Triggers include "map codebase", "analyze codebase", "create project context", "document codebase", "understand code", and "codebase map".

gologo13 Skill

Add comprehensive documentation for the current code/feature and format it according to the ...; keywords: api, architecture, error. Use only on explicit request; skip in routine implementation discussions.

gologo13 Skill

Create comprehensive API documentation for the current endpoints formatted as OpenAPI/Swagge...; keywords: api, openapi, swagger, error. Use only on explicit request; skip in routine implementation discussions.

jorgemenadev Skill

Use when a multi-step plan needs durable tracking across a repo: markdown plans, GitHub Issues, Linear, memory, or a mix. Helps decide where work should live, when to promote tasks to issues, and how future agents should find the current state.

jorgemenadev Bundle

Create and resume founder-led product feedback reports for web or mobile software. Use when someone wants to record product problems or ideas over time, continue an unfinished testing report, attach screenshots or short videos, or export a polished PDF for a product team.

allblueuk Skill

基于 output/ 中的产物渲染 Quarto / LaTeX 报告。当用户说"出报告"、"render report"、"compile"、"渲染论文"时调用。

b2bforce Bundle

Scrape a web page to clean markdown or map a site's URLs using the Firecrawl API. Use when another skill needs page content from a URL (company/service extraction, competitor crawl, ICP from URL). Reads FIRECRAWL_API_KEY from .env.

b2bforce Skill

Generate a weekly competitive-intelligence report from monitored competitor page changes within a date range, with an AI business-impact summary and per-page change list. Use when the user wants a weekly digest, monitoring summary, or shareable intel report. Read firm profile and monitoring files first.

b2bforce Skill

Sweep every client folder and report what needs attention — renewals inside 90 days, accounts in their first 90 days, missing success definitions, accounts with no QBR in two quarters, unfilled proof stubs, stale reviews, and referral-ready accounts. Use for portfolio review, retention review, or before starting new prospecting.