Docs & Writing

harshanandak Bundle

Report where the project stands and what work is in flight -- the Forge status snapshot. Reach for this at session start or whenever the user says "/status", "where am I", "what's in progress", "catch me up", "resume work", or "what changed recently". It surfaces the workflow stage, your active/claimed issues, all issues ranked by composite score with conflict-risk flags, stale already-merged issues (which it closes), and recent commits. Use it to ORIENT and decide the next move -- it reports state; it does not plan, develop, or claim issues. Not for: routing to a stage skill or documenting the full issue-verb surface (kernel); ranking and EXPLAINING a single next-ready or blocked issue to hand off (triage-ready); everyday create/update/list/close/comment/search issue ops (issue-basics); the Hermes harness's token-bounded orient/recap contract (hermes-forge); or the post-merge CI health check that closes issues after a merge lands (verify).

harshanandak Bundle

Runs the Forge verify stage — the post-merge health check performed AFTER a PR is merged: switch to master and pull, confirm the merge landed, check CI is green on master, confirm deployments are up, remove the merged worktree, safe-delete the branch, and close the kernel issues the PR resolved. Use when asked to verify a merge went cleanly, confirm post-merge CI health on master, check deployments after merging, clean up a merged branch or worktree, or close the issue now that its PR is merged — and whenever `/verify` is invoked. Strictly the POST-merge stage: use shepherd instead to monitor a still-open PR toward merge, review to fix and resolve PR feedback before merge, ship to push the branch and open the PR, rollback to undo an already-shipped change, status to merely report the current stage without acting, and issue-basics to close an issue unrelated to a just-merged PR.

harshanandak Bundle

Hermes⇄Forge boundary: Hermes CONSUMES Forge state, never a second source of truth. Use whenever a Hermes session runs on a Forge repo: at session start, before acting on an issue, or when you need CURRENT state. Read state ONLY via `forge orient` / `forge recap <issue-id>` (bounded JSON envelope), citing each source's `path`/`authority`; never reconstruct it from raw stores or kernel internals. Writeback ONLY via `forge comment`/`update`/`create`; NEVER leak Hermes profile or session memory into Forge state. Triggers: "orient me / current project state", "where did this fact come from, cite it", "orient came back truncated", "persist a decision into Forge", "safe to store in kernel state?". NOT the Forge session router over stage skills (kernel), NOT the human "what stage am I in" report (status), NOT everyday issue create/update/close/search CRUD (issue-basics), NOT ranking the next ready issue (triage-ready), NOT live PR monitoring (shepherd—outside Hermes, unseen by orient).

bogheorghiu Skill

"Who is most affected here, and what did the text do to them?" - Re-read primary material from the position of the most-affected, least-powerful party, and re-rank what matters by harm-to-the-many instead of offense-to-the-powerful. Use when (1) analyzing a speech, document, policy, or transcript whose salience was inherited from coverage (famous lines, viral clips), (2) a report ranks findings by scandal value, (3) closing any investigation whose subjects hold more power than the people affected, (4) an external correction showed the importance-ranking was tilted. Does NOT trigger for: technical/product analysis with no affected-party dimension, or pure verification of quotes and facts (use iterative-verification).

bogheorghiu Skill

What do practitioners actually DO (not just document)? Methodology for extracting practitioner knowledge from YouTube video transcripts. Use when (1) researching how people actually use a technology, (2) seeking practitioner insights beyond documentation, (3) looking for tips, patterns, or workflows from creators, (4) building a research corpus from video content.

buildgreatproducts Skill

Use when the user has filled out their Product Offer and wants to develop a sharp, evidence-backed Customer Persona. Triggers on phrases like "build a customer persona", "define my customer", "fill in the customer persona", "who is my ideal customer", "create an ICP", "target customer profile", "persona for my product", or any request to translate a product offer into a customer persona document. Reads the user's Product Offer, researches the target market online, then walks them section by section through the Customer Persona framework — proposing hypotheses, critiquing vague answers, and producing a filled-in customer persona document. Especially appropriate inside a ProductOS-style "Define" workflow where a Product Offer markdown file already exists and a Customer Persona template is waiting to be filled in.

chefroger Bundle

工程图纸分析（实验性） — 从 PDF 图纸提取结构化信息，结果仅供初步参考，不可直接用于生产报价

chienchuanw Bundle

Write a new README.md or improve an existing one. Use when the user asks to create, update, or improve a README, or wants to document a project and no other documentation skill is more specific.

chienchuanw Skill

Capture the current state of a project by updating documentation at the end of a development session. Invokes the readme skill to refresh README.md and the planning-with-files skill to record project status in a doc/ or docs/ directory. Use after merging a PR, finishing a feature, wrapping up a coding session, or any time the user wants to snapshot where the project stands — even implicit phrases like "archive this", "wrap up the session", "document current status", "update project docs", "snapshot this repo", or "I'm done for today". Also use when the user says "end of session" or asks to prepare documentation before stepping away from a project.

chienchuanw Bundle

Generates a branch-vs-default comparison report with plain-language explanations and senior dev review. Use when the user asks to summarize, compare, review, or explain branch changes, or wants a PR summary before merging. Read-only: it produces a report to read — it does not push the branch or open/update the PR (for that use gh-pr).

chienchuanw Skill

Read-only thinking check for the Obsidian portfolio at Personal/Finance/Portfolio/. Reads every open ticker file, compares the original opening thesis against later thesis-log entries and the most recent price action, and surfaces drift (you bought for reason A but are now justifying with reason B), anchoring (you keep restating the same thesis without re-examining it), and stale theses (no new entry in months despite price/news moves). Produces a markdown review the user can paste into their Journal — it challenges your *reasoning* and never tells you to buy or sell. Use this whenever the user wants to sanity-test their investing *thinking* rather than get moves — "is my thesis still right", "challenge my thinking on X", "am I anchoring", "are my reasons still valid", "thesis check", "portfolio retrospective", "重新檢視持股的理由", "我的持股邏輯還成立嗎". For actionable buy/sell/rebalance suggestions and directional calls — "what should I do", "any moves to make", "should I trim X", "投資建議" — use portfolio-advisor instead, whic

dobroslavradosavljevic Bundle

Build, review, debug, configure, migrate, teach, or plan Anhur typed content (@anhur/core, @anhur/vite, @anhur/mdx, @anhur/markdown, @anhur/assets, @anhur/orama). Use when integrating Anhur into an app, writing or changing anhur.config.ts, the cms/ module tree (collections, singletons, enums, objects, views, content.ts, content files), views (defineView / defineIndex / defineGroup / createDerivedHelpers), processors, integrations (orama / defineIntegration), Zod content schemas, folder i18n / localization, anhur/generated imports, localized getters/lists (_meta.locale), the Vite plugin, CLI build/watch, drafts/hooks, MDX/Markdown bodies, assets, CDN/object storage upload (assets storage + files-sdk), or full-text search — or when the user mentions Anhur, .anhur, cms/, folder i18n, or local MD/MDX/YAML/JSON content pipelines.

dobroslavradosavljevic Bundle

Enforces purposeful JSDoc on complex or non-obvious TypeScript code—algorithms, invariants, side effects, edge cases, and public contracts—without restating types or narrating simple code. Use when writing or reviewing TypeScript, adding documentation comments, cleaning noisy JSDoc, documenting public APIs, or when the user says jsdoc, JSDoc, document this, or add docs comments.

managedcode Bundle

Apply MCAF feature-spec guidance to create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.

winstonkoh87 Skill

A non-destructive, decoupled analysis protocol for refactoring code. Generates a "Bill of Materials" report before any code is touched.

quay Skill

Create comprehensive documentation for a Quay bug fix: JIRA ticket update, release notes, changelog entry, PR description, and team communication.

poorgramer-zack Skill

Declarative animation patterns using flutter_animate v4.5.x with composable effects (fade, scale, slide, shimmer, shake, blur), GLSL fragment shaders, and scroll-synchronized animations. Use this skill for adding UI animations and transitions, building staggered or sequenced effects, creating custom animation effects, fixing animation jank or performance issues, implementing shimmer loading states, or adding scroll-driven animations. Supports delays, curves, adaptive effects, and easy extension method chaining (.animate()).

escoffier-labs Bundle

Use when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.

spring-ai-alibaba Skill

Deep codebase initialization with hierarchical AGENTS.md documentation

spring-ai-alibaba Skill

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

spring-ai-alibaba Skill

Invoke parallel document-specialist agents for external web searches and documentation lookup

lukaskellerstein Skill

Update project dependencies to their latest versions, verify nothing breaks, and report what changed. Use this skill when the user says "update dependencies", "upgrade packages", "latest versions", "update deps", "outdated packages", "bump dependencies", or any variation of wanting to bring project dependencies up to date.

lukaskellerstein Skill

Generate or update documentation for the current feature branch. Analyzes all changes (commits, diffs) between the feature branch and base branch, then creates or updates docs/features/<index>_<feature-name>/README.md with incremental indexing based on existing feature docs. Use when documenting a feature branch, creating feature documentation from branch changes, or updating existing feature docs after additional commits. <example> Context: User wants to document their feature branch user: "/update-feature-docs" </example> <example> Context: User wants to document changes user: "document this feature branch" </example> <example> Context: User wants to update existing feature docs user: "update the feature docs with my latest changes" </example> <example> Context: User specifies a base branch user: "/update-feature-docs develop" </example>

matt-bat Bundle

Update existing canonical documentation when an authorized change alters behavior, interfaces, commands, setup, operations, policy, or user-facing usage. Use when documentation would otherwise become inaccurate; do not create unrelated README, tracker, architecture, or runbook artifacts merely because the skill activated.

matt-bat Bundle

Perform source-grounded research before advanced or high-intensity analysis, design, or implementation across any domain. Use when research_intensity is advanced, including niche libraries, unfamiliar APIs, standards-sensitive behavior, consequential recommendations, or work whose correctness depends on current external documentation; do not use for routine tasks fully answered by stable local evidence.

matt-bat Skill

Use for designing and maintaining repository file structure for clarity, modularity, discoverability, and low-duplication across app and documentation surfaces.

phuaky Bundle

Network State presentation template system. Balaji's official slide design with evidence-backed layouts, full-text support, and Network State branding. USE WHEN network state slides, ns-slides, create network state presentation, ns presentation, balaji network state talk.

phuaky Skill

When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." USE WHEN popup, modal, exit intent.

phuaky Bundle

Convert audio files (M4A, WAV, MP3) to Markdown transcripts. USE WHEN transcribe, audio to text, meeting recording, voice memo.

phuaky Skill

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions "referral," "affiliate," "ambassador," "word of mouth," "viral loop," "refer a friend," or "partner program." USE WHEN referral, viral loop, invite program.

phnx-labs Bundle

Write documentation — user-facing, technical, runbooks, onboarding, changelogs. Less is more: only document what code can't tell you.

phnx-labs Skill

Answer a hard research question by fanning it out across DISTINCT search modalities, each blind to the others, then synthesizing one sourced artifact. Codex agents run aggressive web search; Grok agents mine X/Twitter community chatter (its privileged data); Antigravity works Google; Perplexity runs a broad browser-driven Deep Research report; the Claude fleet deep-reads and synthesizes. Multi-modal because no single engine sees everything — a company's funding is in a press release, its reputation is in X replies, its moat is in a founder's blog. Triggers on: /research, /research:research, 'research X across sources', 'deep research on', 'market/competitive/landscape research', 'what's the real story on <company/topic>', 'pull everything on', 'multi-source research'. For a hands-on PRODUCT exploration (drive it, screenshot each journey, prove claims visually) use /research:product.

stephenrogan Bundle

Measures and reports on value delivered to customers including time-to-value tracking, ROI evidence assembly, outcome metrics, and value narratives for QBRs and renewal conversations. Use when asked to measure customer ROI, track time-to-value, build a value report, create an ROI case, quantify outcomes for a customer, or when any workflow needs evidence of value delivered. Also triggers for questions about customer outcomes, value realisation, ROI measurement, business impact quantification, or proving the investment is worth it.

stephenrogan Bundle

Aggregates 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.

stephenrogan Bundle

Generates structured post-call summaries from call transcripts or CSM notes, extracting key discussion points, decisions, action items with owners and deadlines, sentiment signals, and risk or opportunity flags. Routes extracted data to downstream skills for tracking. Use when asked to summarise a call, extract action items from a meeting, generate call notes, create a post-meeting summary, or when any workflow needs structured output from a customer conversation. Also triggers for questions about call documentation, meeting notes, action item extraction, or conversation capture.

stephenrogan Bundle

Produces 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.