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
magnusrodseth/dotfiles/.claude/skills/write-a-skill Skill
no license3★ repoCreate new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
magnusrodseth/dotfiles/.claude/skills/write-in-my-voice Skill
no license3★ repoDraft or rewrite text in Magnus Rødseth's own voice, in Norwegian or English. Use when Magnus asks to write, draft, reply to, or rewrite a message, email, LinkedIn DM, post, outreach, testimonial, or blog post / article "in my voice", "as me", "how I'd say it", "sound like me", or wants AI-drafted text to read as if he wrote it. Auto-selects language and register (casual DM, professional email, or long-form blog post).
magnusrodseth/dotfiles/.config/opencode/skill/opencode-docs Skill
no license3★ repoOpenCode + OhMyOpenCode configuration reference - agents, tools, MCP, skills, commands, hooks, permissions, providers, and Sisyphus orchestration patterns
stempeck/agentfactory/.claude/skills/documentation-update Skill
3★ repoAudits a documentation file line-by-line against the actual codebase, proving every factual claim with source file and line number citations. Produces a structured evidence table, applies corrections for inaccuracies, then verifies corrections are themselves accurate. Use when a user asks to review, audit, refresh, or update a documentation file, or says a doc is outdated.
stempeck/agentfactory/.claude/skills/github-issue Skill
3★ repoCreates well-documented GitHub issues (or comments on existing ones) from problems discussed in conversation. Investigates the codebase to map affected layers, files, and data flow, then writes up findings with acceptance criteria — without prescribing fixes. Use when a conversation has identified a problem that needs a GitHub issue, when the user wants to document a bug or problem for an implementer, or when dispatching work. Triggers on "create a GitHub issue", "write up an issue for this", "file a bug", or "document this problem".
stempeck/agentfactory/internal/cmd/install_skills/architecture-docs Skill
3★ repoGenerate or refresh `/docs/architecture/` — the current-state source of architectural truth for this codebase, grounded in code and git history (NOT in .designs/). Produces an anchor-dense corpus (`invariants.md`, `idioms.md`, `trust-boundaries.md`, `seams.md`, `subsystems/*.md`, `history.md`, `gaps.md`) plus a high-level overview layer (C4 L1/L2 diagrams, sequence flows, Nygard ADRs). Every claim is anchored to a file:line or commit SHA, or labelled literally `"unknown — needs review"`. A bundled `validate.sh` mechanically enforces citation density and phase-completion gates. Used to ground future design reviews so they cannot silently drift away from established idioms.
stempeck/agentfactory/internal/cmd/install_skills/documentation-update Skill
3★ repoAudits a documentation file line-by-line against the actual codebase, proving every factual claim with source file and line number citations. Produces a structured evidence table, applies corrections for inaccuracies, then verifies corrections are themselves accurate. Use when a user asks to review, audit, refresh, or update a documentation file, or says a doc is outdated.
stempeck/agentfactory/internal/cmd/install_skills/github-issue Skill
3★ repoCreates well-documented GitHub issues (or comments on existing ones) from problems discussed in conversation. Investigates the codebase to map affected layers, files, and data flow, then writes up findings with acceptance criteria — without prescribing fixes. Use when a conversation has identified a problem that needs a GitHub issue, when the user wants to document a bug or problem for an implementer, or when dispatching work. Triggers on "create a GitHub issue", "write up an issue for this", "file a bug", or "document this problem".
zacklecon/claude-skills/skills/code-documenter Skill
3★ repoUse when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
jsuvic/agent-profile/fixtures/automation-pack-enabled/expected/.agents/skills/loop-docs-update Skill
3★ repoUse to run a bounded documentation drift scan, update, and re-verify loop that stops when docs match the code, on no diff, or on a repeated identical mismatch.
jsuvic/agent-profile/fixtures/automation-pack-enabled/expected/.claude/skills/loop-docs-update Skill
3★ repoUse to run a bounded documentation drift scan, update, and re-verify loop that stops when docs match the code, on no diff, or on a repeated identical mismatch.
jsuvic/agent-profile/fixtures/mcp-recommendations-enabled/expected/.agents/skills/mcp-fit-check Skill
3★ repoUse to assess whether current documentation through an MCP, docs, or search integration may help with a dependency that may be newer than the client's knowledge.
jsuvic/agent-profile/fixtures/mcp-recommendations-enabled/expected/.claude/skills/mcp-fit-check Skill
3★ repoUse to assess whether current documentation through an MCP, docs, or search integration may help with a dependency that may be newer than the client's knowledge.
jsuvic/agent-profile/fixtures/tabnine-workflow-skills/expected/.agents/skills/loop-docs-update Skill
3★ repoUse to run a bounded documentation drift scan, update, and re-verify loop that stops when docs match the code, on no diff, or on a repeated identical mismatch.
jsuvic/agent-profile/fixtures/tabnine-workflow-skills/expected/.agents/skills/mcp-fit-check Skill
3★ repoUse to assess whether current documentation through an MCP, docs, or search integration may help with a dependency that may be newer than the client's knowledge.
slogsdon/skills-design/skills/design-newsletter-header Skill
3★ repoGenerate a newsletter email header banner — pixel-exact 600×200 HTML canvas (the standard email-client safe-zone width). Self-contained, INLINE styles only (no external <style> blocks beyond <head>) for email-client compat. Intended to be screenshot to PNG and embedded as <img> in email — the rendered image is what readers see, regardless of their email client. Reads ./design/<brand-slug>/DESIGN.md and tokens.css. Triggers include "newsletter header", "email header for X", "email banner", "/newsletter-header".
slogsdon/skills-design/skills/pdf-paginated Skill
3★ repoExports document-flow HTML to a PAGINATED PDF at a real paper size (Letter/A4), with a running folio footer (title · page X / Y). The long-form sibling to pdf-html: where pdf-html renders each .canvas to one tall auto-height page (right for social artifacts and audit reports), this paginates a whole document across pages — right for essays, field guides, specs, and anything meant to be read or printed as pages. Trigger on: "paginated PDF", "print PDF", "PDF with pages", "Letter/A4 PDF", "multi-page PDF", "PDF of this essay/guide/doc". For single-canvas design artifacts (LinkedIn, Instagram, business card, audit report), use pdf-html or screenshot-html instead.
globalize-now/globalize-skills/skills/lovable-i18n Skill
3★ repoSet of skills for globalizing and localizing app
tmuskal/arc-agi-benchmarker/plugins/arc-agi-benchmarker/skills/report Skill
no license3★ repoGenerate and display comprehensive reports from completed ARC-AGI benchmark runs - shows scores, per-game breakdowns, and performance analysis
tmuskal/arc-agi-benchmarker/plugins/longmemeval-benchmarker/skills/report Skill
no license3★ repoGenerate a scorecard from a completed LongMemEval run - computes overall accuracy + per-question-type accuracy and writes scorecard.json
id-andyyy/LabAI/.claude/skills/lab-report Skill
3★ repoГенерация финального документа (DOCX/PDF/MD) с изображениями
ymeiri/voice-layer/packages/codex/skills/calibrate-my-voice Skill
3★ repoBuild or refresh the local voice-layer profile used by write-in-my-voice from user-approved evidence. Use only when the user explicitly asks to calibrate, train, set up, refresh, rebuild, or update their voice-layer profile from sources like git commits, PRs, code reviews, Slack, chat exports, sent email, Google Docs, Confluence, design docs, RFCs, ADRs, issue comments, agent session transcripts, or pasted samples. Do not invoke for ordinary rewrites or drafts.
ymeiri/voice-layer/packages/codex/skills/write-in-my-voice Skill
3★ repoDraft or rewrite user-facing text using the voice-layer model: calibrated personal voice, channel shape, audience adaptation, requested vibe, documentation style, and AI-tell cleanup. Use for Slack, chat, email, PR descriptions, review comments, issues, Confluence, Google Docs, design docs, RFCs, ADRs, release notes, and docs when the user says write in my voice, make this sound like me, rewrite this, polish this, draft a reply, make it corporate-friendly, use a specific vibe, adapt for an audience, de-AI this, or similar. Do not use for code, command output, structured data, verbatim quotes, or voice calibration; use calibrate-my-voice for setup.
matellez/claude-skills/leadership/managing-up Skill
3★ repoAUTO-TRIGGER: Apply this skill when the user is navigating the relationship with their own manager, including a CEO, CRO, VP, or any person they report to directly. Trigger phrases include: "my CEO keeps changing priorities," "my manager is micromanaging," "how do I disagree with my boss," "my CRO doesn't understand marketing," "how do I get more autonomy," "I disagree with this directive," "my manager wants me to do X but I think Y is right," "how do I keep leadership informed without constant check-ins," "my boss is pulling me into every decision," or any situation where the user is trying to manage the dynamics of their upward reporting relationship. Also trigger when the user wants to proactively build trust with a new manager before friction develops, or when they are trying to present a recommendation they expect pushback on. Do NOT trigger for peer relationship issues, sales leader alignment (use sales-leader-alignment), or budget defense conversations (use marketing-budget-defense). This skill is specifically about the relationship with the person the user directly reports to.
The same file is in 1 other repository
matellez/claude-skills/writing/b2b-case-study-writer Skill
3★ repoAUTO-TRIGGER: Apply this skill when the user wants to write, structure, or improve a B2B case study or customer success story. Trigger phrases include: "case study," "customer success story," "write up our results with," "client story," "proof point document," "I want to document what we did for," "we got great results with a client," "turn this into a case study," or any request to document a program result or client outcome in a format that supports sales conversations or credibility building. Also trigger when the user has raw data or interview notes from a client or customer and needs to turn them into a structured asset, or when an existing case study needs to be made more effective. Do NOT trigger for general content writing, blog posts, or LinkedIn posts. This skill is specifically for the structured proof document that supports late-stage sales conversations and demonstrates measurable outcomes to prospects who are evaluating whether to buy.
The same file is in 1 other repository
matellez/claude-skills/writing/b2b-outreach-humanizer Skill
3★ repoAUTO-TRIGGER: Apply this skill automatically whenever Claude is producing, editing, rewriting, or reviewing any written content the user will publish or send. This includes emails, LinkedIn posts, articles, captions, scripts, reports, bios, cover letters, interview responses, proposals, or any other text intended for an external audience. Also apply when the user asks Claude to write, draft, improve, clean up, or rewrite anything. Do not wait to be asked. If writing is being produced or touched, this skill is active. This skill removes AI writing patterns and rewrites output to match the user's established voice: direct, confident, outcome-focused, and free of the filler language and structural tells that mark AI-generated copy.
The same file is in 1 other repository
matellez/claude-skills/writing/linkedin-post Skill
3★ repoAUTO-TRIGGER: Apply this skill when the user asks Claude to write, draft, create, or improve a LinkedIn post, caption, or update. Also trigger when the user asks for a post about a professional topic they plan to share on LinkedIn. Do NOT trigger for long-form articles, resumes, emails, or general writing tasks. This skill is specifically for short-form LinkedIn post content only. This skill structures and formats LinkedIn posts to match the user's established content style: punchy, practitioner-level, engagement-focused, with a strong ending that drives comments without resorting to "agree or disagree?" cliches.
The same file is in 1 other repository
justnau1020/claude-os/skills/development/doc-architecture Skill
3★ repoUpdate architecture documentation after code changes to keep docs in sync with reality. Use when structural changes have been made and documentation needs updating.
justnau1020/claude-os/skills/development/fix-issue Skill
3★ repoFix a GitHub issue end-to-end -- read the issue, implement the fix, write tests, and create a commit. Use when you want to fix a specific GitHub issue, resolve a bug report, or implement a feature request.
dasein108/slope-studio/.agent-instructions/skills/marketing-guru Skill
3★ repoUmbrella orchestrator for a Slope Studio channel's viral-growth loop. Use when the user wants to RUN THE WHOLE ideate→deploy→measure→learn cycle, or doesn't know which step they need, or wants to READ channel state / PICK the next bet / WRITE a growth brief (journal · backlog · report all live here). It composes the per-step lego-block skills (marketing-ideate, marketing-deploy, marketing-measure-learn) and the hands-off driver (marketing-autopilot). For one creative step, invoke that step's skill directly.
f-tiger/zaoqi-blueprints/skills/weekly-report-alchemy Skill
no license3★ repoTransform scattered work records (chat logs, commits, calendar, bullet dumps) into a structured, quantified weekly report tailored to its reader. Use this skill whenever the user mentions weekly or monthly reports, status updates, OKR progress, or says any of these — "周报", "写周报", "写不出周报", "周报写什么", "帮我整理周报", "月报", "工作汇报", "汇报", "怎么汇报工作", "我这周干了啥写不出来", "周报像流水账", "让领导看到我做的事", "status update", "what did I do this week". Also trigger when the user pastes raw work notes asking to organize them, or complains their report reads empty.
u9401066/template-is-all-you-need/.claude/skills/git-doc-updater Skill
3★ repoAuto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布, documentation, 同步文件, 文件檢查, doc check, 發布前, before release, 準備發布.
u9401066/template-is-all-you-need/.claude/skills/git-precommit Skill
3★ repoOrchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送, stage, 暫存, checkin, 簽入, submit, save, 準備發布, ready to commit, 要推了.
u9401066/template-is-all-you-need/.claude/skills/readme-i18n Skill
3★ repoMaintain multilingual README versions (English primary, Chinese translation). Triggers: i18n, 翻譯, translate, 多語言, sync readme, 中英文, bilingual, localization, l10n, 國際化, 本地化, multilingual, 雙語, 語言, language, 英文版, 中文版, translation.
u9401066/template-is-all-you-need/.claude/skills/readme-updater Skill
3★ repoIntelligently update README.md to sync with code changes. Triggers: readme, 說明, 更新說明, update readme, 文檔同步, documentation, doc, 文件, 說明文件, 更新文檔, sync readme, 同步說明, 專案說明.
thoreinstein/obsidian-rag/skills/wiki-ingest Skill
3★ repoUse when the user wants to ingest external sources into the vault — PDFs, markdown files, transcripts, Readwise exports, or any document. Triggers on "ingest", "process document", "import into vault", "distill this", "add to vault", or "extract knowledge from".
Impertio-Studio/n8n-Claude-Skill-Package/skills/source/n8n-syntax/n8n-syntax-code-node Skill
3★ repoUse when writing Code node logic in n8n workflows with JavaScript or Python. Prevents misuse of unavailable variables ($itemIndex, $secrets) or restricted modules (fs, http). Covers runOnceForAllItems vs runOnceForEachItem execution, available variables ($input, $json, items), binary data handling, built-in modules, $() node access, Python _ prefix convention, and restrictions. Keywords: n8n, Code node, JavaScript, Python, $input, $json, items, write code in n8n, JavaScript, Python, custom logic, transform items, Code node example..
jeannesulzer/international-criminal-tribunals-skills/ksc Skill
no license3★ repoKosovo Specialist Chambers (KSC) and Specialist Prosecutor's Office (SPO) research, drafting, and analysis. Use whenever the conversation involves the KSC/KRSJI, the Thaçi et al. case (KSC-BC-2020-06; Thaçi, Veseli, Selimi, Krasniqi), Mustafa (KSC-BC-2020-05), Shala (KSC-BC-2020-04), Gucati and Haradinaj (KSC-BC-2020-07), Law No. 05/L-053, Article 162 of the Kosovo Constitution, the Marty Report (2011), KLA-related crimes 1998-2000, victim participation, the chamber structure, or any KSC document or case identifier. Enforces a verification-first discipline: every case-law, decision, indictment, filing, or judgment citation must be verified against scp-ks.org or legal-tools.org before appearing in any output; appeal registry numbers are cited only once confirmed. Foundational texts (Law No. 05/L-053, Article 162, Rules of Procedure and Evidence) may be cited from project knowledge when present. Trigger on KSC, Kosovo Specialist Chambers, SPO, Thaçi, Veseli, Selimi, Krasniqi, or a KSC case identifier.
The-Artificer-of-Ciphers-LLC/skills-from-the-artificer/trust-but-verify Skill
3★ repoUse when you receive findings, a report, or any factual claims back from a subagent/Task before you act on them — re-validate every claim against a primary source (the code itself, the memory directory, CONTEXT.md, docs/ and docs/adr/, context7 library docs, package/API references, or a language spec) instead of trusting the agent's summary. Trigger automatically after any Task/subagent returns a result you're about to rely on, and whenever the user says "trust but verify", "verify these claims", "double-check what the agent found", "did it actually confirm that", or "where's the source for X". A subagent's report is a lead, not a fact. Nothing is verified until a source was opened and quoted; guessing, inferring, and "that looks right" are not verification.
iwritec0de/app-dev/skills/verification Skill
3★ repoThis skill should be used before claiming any work is complete, before committing, before creating PRs, or before reporting task status. Enforces fresh verification evidence for all completion claims. Provides the verification gate methodology: run commands, read output, then report.
rashidee/co2-skills/skills/modelgen-nosql Skill
3★ repoExtract NoSQL document models from Agile user stories using Domain-Driven Design (DDD) principles. Produces Mermaid class diagrams showing document structure (embedded vs referenced), JSON schema examples per collection, and detailed model documentation per module. Use this skill whenever the user asks to extract a NoSQL module model, NoSQL document model, NoSQL schema, collection design, or document structure from user stories. Also trigger when the user provides user stories grouped by module and asks for NoSQL data modeling, document-oriented design, or embed-vs-reference analysis. Even if the user says "design my NoSQL collections" or "what documents do I need", this skill applies if the input contains structured Agile user stories with module groupings. Do NOT use this skill for RDBMS or relational schema extraction — use the modelgen-relational skill for that. Also trigger when the user says "update the model" or "upgrade the model" to incrementally evolve an existing NoSQL document model based on changes in PRD.md. Accepts an application name (mandatory), version (mandatory), and optional module argument (e.g., `/modelgen-nosql hub_middleware v1.0.3` or `/modelgen-nosql hub_middleware v1.0.3 module:Location Information`).
rashidee/co2-skills/skills/specgen-flutter-riverpod Skill
3★ repoGenerate a detailed specification document for building a Flutter mobile application using Flutter 3.x (Dart 3.x), Riverpod 2.x for state management, Hive 2.x for local storage, Dio 5.x for REST API with smart retry, Firebase Messaging + flutter_local_notifications for push/event notifications, go_router 14.x for navigation, freezed 2.x + json_serializable for immutable models, and build_runner for code generation. The spec also covers cached_network_image, flutter_svg, pull_to_refresh, font_awesome_flutter, material_design_icons_flutter, intl, url_launcher, and flutter_native_splash. Authentication (Keycloak OAuth2/OIDC PKCE via flutter_appauth, local JWT, or none) and optional features (WebSocket, i18n via intl) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new Flutter mobile application. Also trigger when the user says things like "spec out a new Flutter app", "design a Flutter app with Riverpod", "write a technical spec for my new mobile app", "scaffold spec for a Flutter Riverpod app", or any request for a specification document describing a Flutter + Riverpod + Dio + Hive application. Even if the user only mentions a subset of the stack (e.g., "Flutter mobile app" or "Flutter with Firebase notifications"), this skill likely applies — ask and confirm.
rashidee/co2-skills/skills/specgen-react-mui Skill
3★ repoGenerate a detailed specification document for building a React SPA (Single Page Application) using React 19, TypeScript 5, Vite 6, Material UI (MUI) v6, React Router v7, TanStack Query v5, Zustand v5, React Hook Form v7, and Zod v3. Authentication (Keycloak OAuth2/OIDC PKCE, generic OIDC, or none), API integration (REST via Axios), and optional features (WebSocket, i18n, MUI X Data Grid, MUI X Charts) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new React SPA or frontend application. Also trigger when the user says things like "spec out a new React project", "design a React SPA", "write a technical spec for my new frontend app", "scaffold spec for a React MUI app", or any request for a specification document describing a React + MUI + TypeScript application. Even if the user only mentions a subset of the stack (e.g., "React SPA" or "React with Keycloak" or "React MUI dashboard"), this skill likely applies — ask and confirm.
rashidee/co2-skills/skills/specgen-react-tailwind Skill
3★ repoGenerate a detailed specification document for building a React SPA (Single Page Application) using React 19, TypeScript 5, Vite 6, Tailwind CSS v3, Headless UI v2, Heroicons, React Router v7, TanStack Query v5, Zustand v5, React Hook Form v7, and Zod v3. Components are built utility-first with Tailwind and made accessible with Headless UI primitives (no component framework like MUI). Authentication (Keycloak OAuth2/OIDC PKCE, generic OIDC, or none), API integration (REST via Axios), and optional features (WebSocket, i18n, TanStack Table data grids, Recharts charts, react-day-picker date pickers, Tiptap rich text) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new React SPA or frontend application styled with Tailwind CSS. Also trigger when the user says things like "spec out a new React Tailwind project", "design a React SPA with Tailwind", "write a technical spec for my new Tailwind frontend app", "scaffold spec for a React Tailwind app", or any request for a specification document describing a React + Tailwind + TypeScript application. Even if the user only mentions a subset of the stack (e.g., "React SPA with Tailwind" or "React + Headless UI" or "React Tailwind dashboard"), this skill likely applies — ask and confirm.
rashidee/co2-skills/skills/specgen-sdk-java Skill
3★ repoGenerate a detailed specification document for building a distributable Java SDK library packaged as a Multi-Release fat JAR via Maven. Targets JDK 8 baseline with JDK 11+ overlay classes (Multi-Release JAR) so a single artifact runs on every long-term JDK in production. The SDK is a thin client wrapping a remote REST API (and any additional protocols extracted from the PRD's Architecture Principle section). REST communication is implemented with OkHttp; everything else (JSON parsing, models, builders, retry, logging) is implemented with the JDK and in-house code — third-party dependencies are kept to the absolute minimum. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new Java SDK, Java client library, or REST API client wrapper. Also trigger when the user says things like "spec out a new Java SDK", "design a Java client library for my API", "write a technical spec for an SDK that wraps Swagger/OpenAPI", "scaffold spec for a fat-jar Java SDK", or any request describing a Java library that wraps a REST/HTTP API for downstream consumers. Even if the user only mentions a subset (e.g., "Java wrapper around my API", "client library for our microservice", "SDK that supports JDK 8 and 11"), this skill likely applies — ask and confirm.
rashidee/co2-skills/skills/specgen-ts-cli Skill
3★ repoGenerate a detailed specification document for building a distributable Node.js CLI application written in TypeScript. Uses Commander.js for command parsing, tsup for bundling, and @yao-pkg/pkg for cross-platform binary packaging (Windows, macOS, Linux). Interactive prompts (Inquirer.js), persistent user config (conf), project-level config (cosmiconfig), shell execution (execa), HTTP client (got), plugin system, and auto-update checking are configurable based on application needs. Standardized input: application name (mandatory), version (mandatory), command (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new CLI tool, command-line application, terminal tool, or developer tool. Also trigger when the user says things like "spec out a new CLI", "design a TypeScript CLI", "write a technical spec for my CLI tool", "scaffold spec for a Node CLI", or any request describing a command-line application. Even if the user only mentions a subset (e.g., "CLI with config file support" or "distributable Node tool"), this skill likely applies — ask and confirm.
rashidee/co2-skills/skills/util-projectinit Skill
3★ repoInitialize a new CO2 project by validating a hand-authored brainstorm session document and setting up the file-based, turn-based BRAINSTORMING session kit around it. The ONLY valid input is the path to an EXISTING `<topic>.brainstorm.md` file the user authored from the CO2 application-development template (`brainstorm-template-appdev.md`) — free-form prompts, idea text or topic slugs are NOT accepted. The skill strictly validates the session document against the template, rejecting with a report on any deviation — it never creates or edits the session document. On a clean pass it scaffolds the rest of the brainstorm kit in the project folder: the shared `brainstorm-protocol.md`, the `co2-context-generation-guide.md` artifact rules, and the `/brainstorm-loop` slash command. The user then manually runs `/brainstorm-loop` — an iterative, token-efficient loop that converges the root `CLAUDE.md` (Phase A) and every application's `PRD.md` (Phase B) round by round. This skill seeds the project — it is the first skill to run before any `modelgen-*`, `mockgen-*`, `specgen-*`, `testgen-*`, `util-projectsync` or `util-preparek8senv` invocation. Trigger on keywords: "init project", "initialize project", "start project", "bootstrap project", "scaffold project", "new project", "project init", "brainstorm project", "brainstorm app idea", "setup brainstorm", "start brainstorming", "brainstorm session", "generate CLAUDE.md". Accepts one MANDATORY argument: the path to an existing `<topic>.brainstorm.md` session document based on the CO2 template. If the argument is missing, is not a `.brainstorm.md` path, or the file does not exist, the skill stops and instructs the user to copy the template manually.
shwetank/bettersense/plugin/skills/hiring-craft Skill
no license3★ repoUse when designing interview loops, writing interview questions or rubrics, calibrating panel feedback, running hiring debriefs, or making a hire/no-hire call. Trigger phrases include "design an interview loop for [role]", "write interview questions for [signal]", "help me run the debrief", "should we hire X", "I need a rubric for the system design round". Treats hiring as a craft with measurable signals and calibrated decisions, not a vibe-driven exercise.
shwetank/bettersense/plugin/skills/manage-glue-workers Skill
no license3★ repoUse when managing engineers who naturally gravitate toward glue work (onboarding, documentation, unblocking, process improvement) and need protection from burnout, visibility for their impact, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how do I protect my glue person", "glue worker promotion", "coaching someone who's always helping others", "my engineer is drowning in non-promotable work". Provides manager-specific guidance on credit amplification, workload rebalancing, promotion advocacy, and skill development that preserves technical growth.
shwetank/bettersense/plugin/skills/performance-management Skill
no license3★ repoUse when the user is dealing with underperformance, considering a PIP, navigating a brilliant-jerk pattern, documenting concerns, or preparing for a hard performance conversation. Trigger phrases include "I have a report who's underperforming", "should I PIP X", "I need to document this", "how do I have the hard conversation", "I'm worried about [report]'s trajectory". The hardest skill in management — most managers avoid it for too long, then escalate badly. This skill helps the user move through the ladder deliberately: coaching → formal feedback → improvement plan → termination, with documentation and humanity at each stage.
shwetank/bettersense/plugin/skills/product-pulse Skill
no license3★ repoUse to produce a single-page dated pulse report on product health — usage metrics, system performance, AI-feature signals (hallucination, refusal, eval drift), counter-metrics, and follow-up investigation. Trigger phrases include "run a pulse on [area]", "give me a product health snapshot", "weekly product pulse", "what does the data say this week". Reads strategy.md to know what to watch and which counter-metrics matter. Saves to `~/bettersense-work-reflections/pulses/<area-slug>/pulse-YYYY-MM-DD.md` so the folder accumulates into product memory over time. Designed for daily/weekly Desktop scheduled tasks (not cloud routines — those cannot read or write local files). Privacy-first — defaults to aggregated/redacted data; surfaces provenance.
shwetank/bettersense/plugin/skills/promo-case-glue Skill
no license3★ repoUse when an engineer who does significant glue work (onboarding, documentation, unblocking, cross-team alignment, process improvement) needs to build a promotion packet that frames that work as technical leadership. Trigger phrases include "promotion case for glue work", "I do a lot of glue work how do I get promoted", "frame my non-code work for promotion", "my manager says I need more technical accomplishments", "I'm a glue person how do I get senior". Works alongside or as a specialized mode of `report-promo-case`. Produces a promotion-ready narrative that translates glue tasks into ladder-appropriate evidence, with artifact collection guidance and manager talking points.
shwetank/bettersense/plugin/skills/report-career-architect Skill
no license3★ repoUse when designing or revisiting a 12–18 month growth plan for one of the user's direct reports. Trigger phrases include "build a growth plan for [report]", "what should [name]'s next year look like", "I want to architect [report]'s path to senior", "I'm prepping for promo cycle and [report] needs a plan", "let's think about [report]'s development". Distinct from `one-on-one-prep` (per-meeting agenda) and from `coaching-mode` (the conversational layer). This is the *planning* layer — turning observations from `stakeholder-reflect` into a structured arc with concrete experiences, owners, and check-in cadence.
shwetank/bettersense/plugin/skills/report-promo-case Skill
no license3★ repoUse when building a promotion case for a direct report — internal promo packet, panel write-up, or the one-pager that goes to a calibration committee. Trigger phrases include "build the promo case for [report]", "I'm submitting [name] for staff this cycle", "draft [report]'s promo packet", "help me make the case for [name]'s promotion". The mirror image of `wins-curate` — that one is for the user's own brag doc; this is for advocating *upward* for a report. Reads accumulated stakeholder-reflect entries on the report (and any growth plan from `report-career-architect`), produces a panel-ready packet with cited evidence per dimension, surfaces calibration concerns, and flags gaps before submission.
shwetank/bettersense/plugin/skills/strategy-doc Skill
no license3★ repoUse to create or update a product/area strategy document — target problem, approach, personas, key metrics (3-5 SMART), 2-4 multi-month strategic tracks, and an explicit "not working on" section. Trigger phrases include "draft a strategy doc for [product/area]", "I need a strategy.md for the platform team", "interview me about my strategy", "update my strategy doc", "what's in my strategy doc". Lives at `~/bettersense-work-reflections/strategy/<area-slug>.md` and is read as an anchor by `the-spec-writer`, `prioritization-frameworks`, `metrics-design`, `product-pulse`, and `pulse-synthesize`. Inspired by Every.to's `/ce:strategy` pattern but composes more deeply with the rest of the bundle and supports multiple products/areas.
shwetank/bettersense/plugin/skills/tech-strategy-writer Skill
no license3★ repoUse when a senior IC (staff/principal engineer, architect, tech lead) needs to write a technical strategy or direction doc — where a system or domain should go over 12–24 months and why. Trigger phrases include "write a tech strategy for [domain]", "I need a technical direction doc", "our platform needs a north star doc", "help me write the tech vision for [area]". The staff+ artifact: turning engineering judgment into direction others can follow without you in the room. Distinct from strategy-doc (its product/business peer) and the-rfc-reviewer (reviewing one proposal). Saves to strategy/tech-<area>.md.
FutureJJ/claude-skills/skills/documentation-writer Skill
3★ repoTechnical documentation including API docs, ADRs, runbooks, READMEs, and changelogs. Trigger for documentation structure, API documentation, or technical writing guidance.
The same file is in 1 other repository
rampstackco/claude-skills-pm/skills/pm-spec-writing Skill
3★ repoTranslate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.
The same file is in 2 other repositories
rampstackco/claude-skills-pm/skills/stakeholder-communication Skill
3★ repoCommunicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on stakeholder update, status report, executive summary, exec review, manage up, communicate bad news, project comms, status meeting, weekly update. Also triggers when a project is going off track and the team needs to communicate it.
The same file is in 1 other repository
Biraj2004/huashu-skills-english/huashu-data-pro-en Skill
3★ repoAll-in-one data analysis and productivity assistant. Covers end-to-end workflows for data processing, analytical insights, report writing, PPT creation, and data visualisation. Always approaches tasks from an expert perspective — thinks one step ahead for the user. Proactively confirms with the user when uncertain. Supports: Excel data analysis, advertising data review, ROI calculation, data visualisation, report generation, PPT creation, formula generation. Use when the user mentions "analyse data", "create a report", "make a PPT", "Excel", "advertising analysis", "ROI", "retrospective", "weekly report", "monthly report", "data processing", "chart", "visualisation", "presentation", "table", or "formula".