Docs & writing
16,621 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
vipincode/exr-agent-skills/.claude/skills/backend-module-builder Skill
no license0★ repoBuild a backend feature/module from an approved FEATURE_PLAN, enforcing reuse so no duplicate utils, middleware, types, or helpers get created. Use this whenever the user wants to implement, build, or generate a planned feature — "build the auth module", "implement FEATURE_PLAN_products.md", "now build it", "code up the orders feature". It reads ARCHITECTURE.md + MODULE_REGISTRY.md + the feature plan, searches for existing reusable code BEFORE creating anything, builds the module in the project's paradigm, then updates the registry. It does NOT plan features (that is backend-feature-planner) and does NOT write tests (that is backend-test-writer). Works in any project in the Express/TS convention family with the contract files.
vipincode/exr-agent-skills/.claude/skills/backend-test-writer Skill
no license0★ repoAgent Skills for building production-grade Express + TypeScript + Mongoose backends with Claude Code
vipincode/exr-agent-skills/.claude/skills/express-ts-bootstrap Skill
no license0★ repoScaffold a new production-grade Express.js + TypeScript + Mongoose + JOSE backend from scratch. Use this whenever the user wants to start a new Node/Express API project, bootstrap a backend, set up an Express + TypeScript starter, or initialize a server-side project — even if they only say "new API", "Express starter", "backend boilerplate", or name the stack loosely. This skill scaffolds the infrastructure ONCE per project and generates the two source-of-truth files (ARCHITECTURE.md and MODULE_REGISTRY.md) that the backend-feature-planner, backend-module-builder, and backend-test-writer skills depend on. Do NOT use this to add a feature to an existing project (that is backend-feature-planner + backend-module-builder) or to write tests (backend-test-writer). This scaffolds an Express/Node + TypeScript backend specifically — do NOT use it to bootstrap projects in other stacks or languages (Django/Python, Rails, Spring, Go, Next.js, etc.); those are out of scope.
vipincode/exr-agent-skills/.claude/skills/frontend-module-builder Skill
no license0★ repoBuild the API binding for an already-designed Next.js/React feature from an approved FEATURE_PLAN — wiring the existing design to a real backend endpoint and making it functional, while enforcing reuse so no duplicate components, hooks, schemas, or utils get created. Use this whenever the user wants to implement/build/execute a planned frontend binding — "build the products binding", "implement FEATURE_PLAN_products.md", "now make this design functional", "wire up the orders screen", "bind it to the API". It reads the frontend ARCHITECTURE.md + MODULE_REGISTRY.md + the feature plan, searches for existing reusable code BEFORE creating anything, writes the feature-module binding layer (types/schema/api/hooks) and edits the built design to consume it (dropping hardcoded samples), unwraps the response envelope + validates with Zod, uses TanStack Query for server state, then updates the registry. It does NOT plan the binding (that is frontend-feature-planner), does NOT build/redesign components from Figma or HTML (that is figma-to-component / html-to-component), and does NOT write tests (that is frontend-test-writer). It is NOT for backend/server code (that is backend-module-builder). Frontend / Next.js / React / API-binding scope only.
vipincode/exr-agent-skills/.claude/skills/frontend-test-writer Skill
no license0★ repoWrite tests for frontend Next.js/React code on demand — components, hooks (incl. TanStack Query hooks), Zod schemas, and API-binding behavior. Use this ONLY when the user explicitly asks to test frontend code — "write tests for the products grid", "test the useProductsQuery hook", "add component tests for product-card.tsx", "cover the create-product form", "test this binding". It is a standalone utility, run manually whenever the user wants — never auto-chained from frontend-feature-planner or frontend-module-builder. It reads ARCHITECTURE.md (conventions), MODULE_REGISTRY.md (what to mock vs use), the target file(s), and the FEATURE_PLAN's testing checklist if present, detects the test framework + RTL setup from package.json, and writes matching test files. It never modifies source files and never touches the registry. It is NOT for backend tests (that is backend-test-writer). Frontend / Next.js / React / Vitest+RTL scope only.
vipincode/exr-agent-skills/.claude/skills/prd-creator Skill
no license0★ repoTurn an app idea into a production-grade PRD, then shard it into per-module briefs that feed module-planner. Use this whenever the user wants to plan a whole app or product — "I want to build a blog / e-commerce app / SaaS", "create a PRD", "help me plan this app", "scope my product idea", "divide the PRD into modules", "shard the PRD" — or describes a product vision spanning multiple features, even if they never say "PRD". It takes the user's points, suggests improvements and standard production features they missed (auth, payments, admin, SEO — the user keeps or rejects each), writes _docs/prd/PRD.md, and on approval shards it into _docs/features/<module>/<module>-module.md briefs tagged backend/frontend/fullstack. Also use it to MODIFY an existing PRD (change scope, add features, re-shard). It does NOT do technical feature planning (that is module-planner), does NOT write code, and does NOT scaffold projects — product scope only, upstream of the whole toolkit.
scoobydrew83/skills/plugins/coordinated-skills/skills/drift-check Skill
0★ repoAudit a set of related project documents for internal contradictions and drift from their stated mission, with a skeptical eye that distrusts suspiciously clean alignment. Use whenever the user points at multiple docs (spec, PLANNING.md, README, CLAUDE.md, .cursorrules, system prompt, TASK tracker, ADRs) and asks "are these consistent", "do my docs agree", "has my spec drifted", "check alignment", "is my README in sync", "audit my project for consistency", or shares a self-alignment/audit report. Especially trigger when documents should agree on the same facts (tech stack, metrics, feature lists, naming, architecture, tone) and the task is finding where they silently diverge, or where identical copy-pasted claims masquerade as validation. Lead with the real state of alignment and the biggest contradiction, never a vanity score. For cross-document consistency and mission-drift within a project's own materials, not verifying external claims (use reality-check) or choosing between options (use a council skill).
scoobydrew83/skills/plugins/coordinated-skills/skills/goal-builder Skill
0★ repoTurn a vague intent into a correct, transcript-verifiable Claude Code /goal condition through a short question-and-answer interview, then (when the pattern recurs) crystallize it into a reusable .claude/commands/ slash command. Use whenever the user wants to write, fix, or improve a /goal command, set a completion condition, "keep Claude working until X", run an unattended/until-it-passes Claude Code session, or says their /goal "just keeps looping" or "stops too early". Trigger even if they don't say "goal" but describe wanting Claude Code to loop on its own until a measurable end state holds. The point is to stop them writing a PROMPT ("clean up my code") when /goal needs a CONDITION ("npm test exits 0, without editing the test file"), and to refuse any goal whose finish line a transcript-reading evaluator can't check. For crafting the single /goal line; to build a full builder/verifier loop package (spec, prompts, harness, CI) use loop-creator.
scoobydrew83/skills/plugins/coordinated-skills/skills/repo-troubleshooting-guide Skill
0★ repoGenerate a clean, professional troubleshooting guide (a TROUBLESHOOTING.md) by analyzing a code repository — detecting its tech stack and mining real evidence (raised exceptions, error strings, env vars, ports, Docker services, CI) to document common failure modes with step-by-step fixes. Use this whenever the user wants to create, build, or generate a troubleshooting doc, guide, runbook, or ops reference for a repo, codebase, or project; wants to document common errors, setup problems, failure modes, or "how to fix X"; or points Claude at a repository and asks for a debugging/operations reference. Trigger even if the user doesn't say the exact word "troubleshooting" — e.g. "document the common errors in this repo", "make a debugging runbook", "build a setup-issues guide", "write an ops doc for this project".
BryceEWatson/claude-global-skills/pattern-retrospective Skill
0★ repoApply rigorous pattern-retrospective analysis to Claude transcripts. Triggers on writing studies, blog posts, handoff docs, retrospectives, specs, or improvement proposals that draw conclusions from past Claude sessions — phrasings like "handoff to X", "lessons from session Y", "pattern Z over time", "spec for X", "improvements to X", "audit my use of W" all match. Enforces target-system audit BEFORE specifying its requirements, streaming JSONL parsing (never load whole files), 5-tuple extraction with provenance tags, self-falsification of every cited claim including system-state claims, Bayesian confidence smoothing, and correlation-not-causation discipline. Designed to prevent the credulous-handoff failure mode where ~60% of proposed requirements turn out to already exist in the target system.
BryceEWatson/claude-global-skills/weekly-work-log Skill
0★ repoBuild and refresh the brycewatson.com "Weekly Work Log" report page (/weekly-report, archived under /log) for the last completed week. Discovers the week's work from session-end handoffs + git, distils it into honest public-voice items, re-derives and verifies every number, and (unattended, every Sunday night via a Claude scheduled task) opens a judgment-assisted review PR. Never publishes unattended.
search-atlas-group/amm-founding-circle/skills/agent-runbook Skill
0★ repoRouting runbook for engineering tasks across the agent stack (ao spawn, GSD, OMC, /goal, /loop, /schedule, inline, codex, gemini, Claude Flow swarm). Use when uncertain which execution mode to choose, before any non-trivial action. Outputs a composed pipeline, not just one mode. Hard rules and gates live in global CLAUDE.md; this skill is the HOW for routing.
search-atlas-group/amm-founding-circle/skills/html-reports Skill
0★ repoSelf-contained HTML report archetypes. Pick the right shape for the document — Folio (book), Stage (slides), Atlas (dashboard), Field (editorial long-read), Ledger (comparison matrix), Timeline (chronological story). Single-file, date-stamped outputs, no external deps, light-mode by default.
search-atlas-group/amm-founding-circle/skills/report-writer Skill
0★ repoCreate a standalone HTML report, decision memo, audit, comparison, or analysis for a stakeholder audience.
search-atlas-group/amm-founding-circle/skills/serp-intent-decoder Skill
0★ repoAnalyze 1-15 keywords to decode true search intent from the live SERP — not the keyword text alone. For each keyword, returns intent classification (informational, commercial-investigation, transactional, navigational, local), SERP feature profile (AI Overview, PAA, local pack, shopping, forums, featured snippet), the content format Google is actually rewarding, recommended word count, recommended angle, and explicit "don't bother" warnings when the SERP is unwinnable. Use this skill whenever a user provides a keyword or list of keywords and wants to know what to write, whether it's worth writing at all, what format to use, what SERP features are present, what intent the keyword really has, "should I target this keyword," "what format works for X," "what's ranking for Y," or any variant of "SERP analysis." Trigger before a content brief run when the user is still deciding which keywords are worth investing in. When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.
Sandy-zippy/claude-code-seo-stack/skills/fix Skill
0★ repoExecute the diagnosis - write the JSON-LD schema, the llms.txt, the copy changes and the answer content, then push live via a CMS MCP if one is connected (WordPress/Shopify/Webflow/Sanity). Use when asked to "fix it", "run the fix skill", or implement the diagnosis report.
lroolle/skills/skills/htmlize Skill
0★ repoNine opinionated agent skills for Claude Code & Codex — UX design, motion, HTML artifacts, decision spread, goal contracts, and the craft of making skills. Every protocol opens with a gate that can say no.
MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-docs Skill
0★ repoDocumentation engineer for the Karvey method. Generates Diataxis docs (tutorial/how-to/reference/explanation) from code, updates stale project docs to match what shipped, and exports markdown to publication-quality PDF. Triggers include "karvey docs", "documentación", "documentation", "diataxis", "actualizar docs", "update docs", "generar documentación", "generate documentation", "exportar PDF", "export PDF", "README".
onyx679/automotive-ve-ai-skills-kit/skills/ve-manual-writer Skill
0★ repoConvert value-engineering workflow notes, SOP drafts, meeting decisions, templates, or best-practice examples into concise operating manuals, checklists, FAQs, and training materials for value engineering teams.
SkillMedev/startup-fundraising/skills/investor-update-writer Skill
0★ repoDrafts a monthly or quarterly investor update - TL;DR, consistent metric block (revenue, growth rate, burn, runway), highlights, honest lowlights, a specific ask, and next-period priorities - in a repeatable one-screen format. Use when someone asks "write my investor update", "what should go in my monthly update", "how do I tell investors about a bad month", or when a founder is due to report to their cap table. Do NOT use for updates to internal teams, executives, or non-investor stakeholders - use stakeholder-update instead. Do NOT use for crafting the fundraising story for new investors - use fundraising-narrative instead.
The same file is in 2 other repositories
SkillMedev/startup-fundraising/skills/vc-pitch-email Skill
0★ repoWrites cold investor outreach under 100 words - a subject line built on the company's strongest verifiable metric, a personalized why-them opening line, traction before the ask, and a low-friction meeting request - delivered as three subject options, the email body with word count, and a follow-up line for five days later. Use when a founder asks "write a cold email to this VC", "how do I get an investor meeting", "pitch my seed round over email", or is starting investor outreach. Do NOT use for choosing which investors to contact - use investor-targeting instead - or for post-investment monthly updates - use investor-update-writer instead - or for non-investor sales outreach - use cold-email-craft instead.
The same file is in 2 other repositories
SkillMedev/job-search-kit/skills/job-application Skill
0★ repoTailors a resume and writes a cover letter for one specific job description - mirroring JD keywords for ATS parsing, reordering bullets by relevance, quantifying impact, and reporting which JD keywords matched and which are missing. Use when someone asks "tailor my resume to this job", "write a cover letter for this posting", "will my resume pass the ATS", or shares a job description alongside their resume. Do NOT use for writing or restructuring a resume without a target job - use resume-writer instead; for critique of an existing resume, use resume-reviewer.
The same file is in 1 other repository
SkillMedev/job-search-kit/skills/linkedin-post-writer Skill
0★ repoWrite LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win into a LinkedIn post". Do NOT use for Twitter/X threads - use tweet-thread-builder instead. Do NOT use for scheduling across a monthly calendar - use social-content-calendar instead.
The same file is in 3 other repositories
SkillMedev/job-search-kit/skills/salary-negotiation Skill
0★ repoPrepares and scripts salary and job-offer negotiations - market research, target/minimum/anchor numbers, BATNA strength, deflection and counter scripts, and total-compensation trades when base is capped. Use when someone asks "how do I negotiate my offer", "they asked my salary expectations, what do I say", "is this offer low", or "how do I counter without losing the offer". Do NOT use for writing resumes, cover letters, or managing the application pipeline - use job-application instead; for declining an offer gracefully, see offer-rejection-writer.
The same file is in 1 other repository
SkillMedev/product-manager-stack/skills/technical-spec Skill
0★ repoWrites engineering design docs and RFCs that align a team before code - TL;DR, background, goals and explicit non-goals, quantified requirements, a concrete end-to-end design with failure modes, alternatives considered, rollout plan, and open questions surfaced at the top for reviewers. Use when an engineer asks "write a design doc for this feature", "turn my approach into an RFC", "reviewers keep asking why didn't you just X", or a project needs alignment before implementation. Do NOT use for designing the API contract itself - use api-design instead; for user-facing product documentation, use help-documentation.
The same file is in 1 other repository
Sidsaladi9/persona-os/plugins/product-manager-os/skills/release-notes Skill
0★ repoTurns a list of shipped changes into audience-tiered release notes — a benefit-led user-facing changelog, a what/why/impact internal log, and a short social announcement cut. Use when you say "write release notes," "draft the changelog," "we just shipped X, announce it," "turn these tickets into release notes," or "summarize this release for customers and the team."
Sidsaladi9/persona-os/plugins/product-manager-os/skills/write-spec Skill
0★ repoTurns a vague feature idea or problem statement into a structured, review-ready feature spec or PRD with goals, non-goals, success metrics, and testable acceptance criteria. Use when a PM says "write a PRD", "spec this feature", "turn this idea into a spec", "scope this", "define success metrics", "write acceptance criteria", or needs to break a big ask into a phased spec.
SkillMedev/lifecycle-marketing/skills/email-newsletter-pro Skill
0★ repoWrite recurring email newsletters - subject lines that earn the open, preview text that extends them, a body structure readers finish, and cadence rules that keep the list healthy. Use when someone asks "write my newsletter", "give me subject line options", "why is my open rate dropping", "should I send weekly or monthly", or "help me structure this issue". Do NOT use for automated onboarding or behavior-triggered sequences - use email-drip-builder instead. Do NOT use for inbox placement and spam-folder problems - use email-deliverability instead.
The same file is in 2 other repositories
alectivism/organization-ai-skills/org-content/skills/content-draft Skill
0★ repoDraft marketing and communications content in your organization's brand voice — blog posts, newsletter articles, thought leadership, web copy, one-pagers. Use for "write a blog post", "draft an article", "write copy for", "create content about".
alectivism/organization-ai-skills/org-ops/skills/document-find Skill
0★ repoFind documents in your organization's document storage — SharePoint, Google Drive, Notion, or other knowledge bases. Use for "find the document", "where is the file", "find on [storage platform]", "look up the [document type]".
alectivism/organization-ai-skills/templates/brand-voice Skill
0★ repoBrand and communications reference — naming rules, colors, fonts, tone, logo usage, and document formatting standards. Use when creating branded content, Word docs, presentations, or any externally-facing materials.
Exekiel179/pingouin-psych-stats/skills/pg-reporting Skill
0★ repoConvert Pingouin results into compact, polished APA-style or Chinese psychology result sections with tables, assumption notes, and uncertainty caveats.
waseemnasir2k26/skynetlabs-all-claude-code/skills/code-quality-and-review/code-audit-fanout Skill
no license0★ repoFive-way parallel code audit. User pastes a Python file / function / diff → orchestrator fans out 5 specialist sub-agents in ONE message, each reviewing a DIFFERENT axis (static analysis, library API correctness, standards/spec compliance, reproducibility, numerical correctness). Every finding MUST cite an exact URL + a quoted passage from the official documentation. Aggregator agent merges, dedupes, ranks by severity. Code returns reviewed 4-5 times before the user touches it. Trigger when user says: "audit this code", "review this diff", "debug this", "check my function", "find bugs", "/audit-code", "/code-audit-fanout", "fanout audit", or pastes a code block and asks for review. Auto-trigger heuristic: user pastes >20 lines of Python and asks for "review", "audit", "debug", "check", or "bug". HARD RULE: zero claims without a source. Every issue cites a URL to the official docs / paper / spec, plus the exact quoted passage. No hallucinated APIs, function signatures, or behaviors. If a specialist cannot verify a claim against a primary source, it must say "UNVERIFIED" and skip the finding.
waseemnasir2k26/skynetlabs-all-claude-code/skills/content-and-reels/ralph-wiggum-marketer Skill
no license0★ repoUse this skill when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand voice", or mentions content strategy, voice analysis, competitive research, or iterative content improvement.
waseemnasir2k26/skynetlabs-all-claude-code/skills/content-and-reels/ralph-wiggum-marketer/skills/copywriter Skill
no license0★ repoUse this skill when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand voice", or mentions content strategy, voice analysis, competitive research, or iterative content improvement.
waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/n8n-skills/skills/n8n-code-javascript Skill
no license0★ repoWrite JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.
The same file is in 5 other repositories
waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/n8n-skills/skills/n8n-code-python Skill
no license0★ repoWrite Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.
The same file is in 4 other repositories
waseemnasir2k26/skynetlabs-all-claude-code/skills/seo-content-copy/citation-monitor Skill
no license0★ repoTrack brand mention citations across 4 LLMs (Claude, ChatGPT, Perplexity, Gemini) for a configurable list of brand keywords. Daily cron pulls write to local sqlite. Weekly markdown report shows mention counts, position, and citation deltas. Powers citelift.app SaaS upgrade path. Local-first; Supabase + n8n optional later.
waseemnasir2k26/skynetlabs-all-claude-code/skills/seo-content-copy/seo-geo/build/seo-content-writer Skill
no license0★ repoWrite SEO blog posts, articles, landing pages with keyword integration, header optimization, and snippet targeting. SEO文章写作/内容优化
eprouveze/claude-skills/skills/codex-write Skill
0★ repoDelegate heavy code generation to Codex CLI while Claude orchestrates, reviews, and surgically fixes. Use for any task involving 50+ lines of new code, boilerplate generation, test writing, or large refactors. Claude acts as lead engineer; Codex acts as developer. Multi-LLM aware — checks `.claude/llm-mode.json` before delegating and falls back to direct write if Codex is unavailable.
eprouveze/claude-skills/skills/gmail-attachment Skill
0★ repoSend (or draft) a Gmail message with one or more file attachments via the google-workspace MCP. Use whenever the user asks to email a file, attach a document, send a PDF / markdown / spreadsheet by mail. Trigger phrases — "email this file to X", "send by mail with the doc attached", "envoie ce fichier par mail", "joindre en pièce jointe". The MCP's documented `path` field is sandboxed and silently fails on host paths; this skill enforces the only working route (base64 `content` + `filename`) and documents the size envelope.
LaoitdevOpen/laoitdev-skills/skills/frontend/frontend-i18n Skill
0★ repoTranslation and i18n rules for the AMIS admin project. Use this whenever writing any user-visible string, building a form with validation messages, handling API or business errors, or adding new translation keys. Also use when the user asks 'how do I translate X', 'add translation for Y', 'don't hardcode this string', or 'add an error message'. Covers: useTranslation usage, Zod schema factory pattern, validation key structure, API error translation via useAPIErrorTranslator, and adding new error codes to both translation files.
LaoitdevOpen/laoitdev-skills/skills/mobile/flutter-clean-arch-getx Skill
0★ repoFile-by-file conventions and copy-paste patterns for building or modifying features in a Flutter app that uses Clean Architecture (data/domain/presentation layers) with GetX state management and get_it dependency injection. Use this whenever the user is adding or changing a feature, screen, or API integration in a Flutter/GetX project — including entities, models, datasources, repositories, usecases, GetX controllers or bindings, DI registration in injection.dart, routing, or localization/translation keys. Trigger even if they don't say "clean architecture" or "GetX" by name — phrases like "add a screen that calls this API", "wire up this repository", "create a controller for X", "register this in DI", or "add these translation keys" in a Flutter project all mean this skill applies.
Salesforce marketing cloud developer navigator
ayanme/salesforce-navigator-suite/skills/salesforce-marketing-cloud-developer-navigator Skill
0★ repoThis Navigator researches Salesforce Marketing Cloud developer APIs, scripting, and integration documentation from official sources. Use when the user asks how to write code or call APIs for Salesforce Marketing Cloud: REST APIs, SOAP APIs, AMPscript, SSJS, WSProxy, Journey Builder APIs, Transactional Messaging API, package development, authentication, integrations, and Account Engagement/Pardot developer APIs. Does not own MobilePush SDK implementation.
Salesforce release notes navigator
ayanme/salesforce-navigator-suite/skills/salesforce-release-notes-navigator Skill
0★ repoThis Navigator researches Salesforce product releases, new features, and change history from official release notes. Use when the user asks what changed, what's new, or what was released for Salesforce products: new features, GA, Beta, Pilot, deprecations, breaking changes, upgrade guidance, Agentforce, Data Cloud, Marketing Cloud, Marketing Cloud Personalization, CRM Analytics, and MuleSoft. Does not own developer API or SDK changelogs.
SkillMedev/incident-response-command/skills/oncall-handoff Skill
0★ repoProduces a complete on-call shift handoff note - shift summary, open incidents, watch items with paging thresholds, silenced alerts, in-flight changes, and escalation contacts - checked against a completeness checklist. Use when someone asks "write my on-call handoff", "what should I tell the next on-call", "my shift ends in an hour, help me hand over", or "make a handoff template for our rotation". Do NOT use for writing the incident postmortem after resolution - use postmortem-writer instead. For live severity assessment during an incident, use sev-triage; for external customer-facing incident comms, use status-page-update.
The same file is in 1 other repository
SkillMedev/incident-response-command/skills/postmortem-writer Skill
0★ repoWrites blameless incident postmortems with a log-reconstructed timeline, multi-causal contributing factors, and owned, dated action items. Use when someone asks "write the postmortem for yesterday's outage", "run a blameless retro on this incident", "turn these incident notes into a postmortem doc", or after any SEV1 or SEV2 event. Do NOT use for customer-facing incident updates while the incident is live - use status-page-update instead; for transferring context at a shift change, use oncall-handoff; for classifying and running a live incident, use sev-triage.
The same file is in 1 other repository
SkillMedev/incident-response-command/skills/runbook-writer Skill
0★ repoWrites an operational runbook for a service covering symptoms, diagnostic checks, mitigations, and escalation paths. Use when shipping a new service or when an existing service lacks incident procedures.
The same file is in 1 other repository
SkillMedev/incident-response-command/skills/status-page-update Skill
0★ repoWrites customer-facing incident status updates for each lifecycle stage - investigating, identified, monitoring, resolved - with cadence rules and plain-language templates. Use when someone asks "write a status page update", "what do we tell customers about this outage", "draft the resolved notice", or during an active incident needing customer communication. Do NOT use for the internal post-incident analysis - use postmortem-writer once the incident is closed; for deciding severity and internal escalation flow use sev-triage; for summarizing an incident upward to executives use escalation-summary.
The same file is in 1 other repository
mohitkhandelwal242/ai-pm-operator/.claude/skills/monthly-board-prep Skill
no license0★ repoMonthly Analysis — leadership-deck format month-over-month (MoM) comparison driven by business.json. Pulls two consecutive months of your product's metrics, computes deltas, and renders a leadership-style markdown deck with sections derived from your revenue_model and key_metrics, then optionally auto-publishes to Confluence. Use when asked for 'monthly analysis', 'month over month', 'MoM report', 'leadership monthly', 'board prep', or '/monthly-analysis'.
mohitkhandelwal242/ai-pm-operator/.claude/skills/prd-generator Skill
no license0★ repoProduct Requirement Document (PRD) generator. Transforms brief feature ideas into complete, structured specs with user stories, acceptance criteria, metrics, and edge cases. Use when asked to generate a PRD, write a spec, or '/prd-generator'.
mohitkhandelwal242/ai-pm-operator/.claude/skills/release-notes-writer Skill
no license0★ repoGenerate slide content for the Product section of a leadership weekly / release-notes deck. Aggregates user-visible product ships from the last 4 weeks across all of the business's repos (the current git repo + every repo in business.json → stack.code_repos[]) plus Jira Done items in ${PROJECT_KEY}, groups them by theme, and produces per-experiment slides with measured impact tables. Use when asked for 'leadership product slides', 'product week deck', 'release notes deck', 'what shipped to production', '/leadership-product-weekly', or '/product-weekly'.
mohitkhandelwal242/ai-pm-operator/.claude/skills/weekly-metrics-analyst Skill
no license0★ repoGoogle Analytics weekly report for ${PROJECT_DOMAIN} — traffic sources, user behavior, bounce rates, conversions, and anomaly detection. Use when asked about 'google analytics', 'GA report', 'website traffic', 'traffic sources', 'bounce rate', or '/ga-report'.
mehdiforoozandeh/skills/skills/latex-vscode Skill
0★ repoSet up, compile, preview, and troubleshoot LaTeX in VS Code with the LaTeX Workshop extension — an Overleaf-equivalent local/remote workflow (build-on-save, PDF preview, SyncTeX, latexmk, bibtex citations, LTeX grammar, Live Share). Use whenever working with .tex/.bib files, building a PDF, fixing a LaTeX/latexmk compile error, wiring citations/bibliography, or configuring the LaTeX Workshop / LTeX / Live Share setup. Triggers: latex, .tex, latexmk, pdflatex, lualatex, bibtex, \cite, build the pdf, compile my paper, SyncTeX, Overleaf, LaTeX Workshop. NOT for writing prose (use scientific-writing) or generating BibTeX entries (use citation-management).
SkillMedev/skill-builder-studio/skills/skill-description-writer Skill
0★ repoWrites the description field that makes a skill fire reliably - WHAT it does, WHEN to invoke it with quoted user phrasing, and what it is NOT for. Use when drafting or improving only the description or trigger of a SKILL.md or catalog entry - "this skill never fires", "fix this description", "write the frontmatter description". Do NOT use to author a whole skill (use skill-creator) or to grade/audit one (use skill-auditor).
The same file is in 1 other repository
Manuscript prose immersion audit
dinaf2026-web/manuscript-editorial-suite/manuscript-prose-immersion-audit Skill
0★ repoLine-level prose and scene-immersion auditor for any narrative manuscript — the deep craft pass beneath the publisher's read. Diagnoses scenes for the failures that keep prose at draft level: information dialogue, talking-heads, filter words, furniture-inventory description, missing micro-reactions, weak environmental presence, and emotion stated instead of threaded. Use when the author says "line audit", "prose immersion audit", "prose pass", "diagnose this scene", "is this immersive", "does this read like a draft", "craft pass", or "kill the info-dumping". It diagnoses at the line level — it does NOT rewrite prose, grade marketability, check canon, or judge mystery logic. For rewritten prose, route to the author's writing/voice skill.
The same file is in 1 other repository
dinaf2026-web/manuscript-editorial-suite/manuscript-publisher-critique Skill
0★ repoThe publisher's read for any manuscript — an acquisitions verdict plus a developmental craft breakdown, delivered as a scored report card graded against the markers of a great book in its genre (set by the project profile). Use for a single craft/acquisitions read of a scene, chapter, outline, full manuscript, or query: "publisher's read", "acquisitions verdict", "critique this", "score this", "grade this", "editor's letter", "would a publisher take this", "what's weak here", "read this like an editor". For a broad "review my book / full editorial pass" that may need several checks, use manuscript-editorial-router. NOT for canon checking (continuity-audit), mystery-fairness logic (fair-play-audit), line-level immersion (prose-immersion-audit), or blurb/listing copy (listing-critique). Diagnoses and scores; does not rewrite prose.
The same file is in 1 other repository
Drvivek34/Skill-Bazaar/data-analysis/xlsx Skill
no license0★ 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
Drvivek34/Skill-Bazaar/documentation/api-documentation Skill
no license0★ repoUse when generating OpenAPI / Swagger specs, writing API references, or formatting markdown developer portals.
Drvivek34/Skill-Bazaar/writing-content/doc-coauthoring Skill
no license0★ repoGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
The same file is in 39 other repositories