Docs & Writing

b2bforce Bundle

Files-only competitor website monitoring for a shared B2BForce workspace. Use to maintain competitor profiles, monitored page lists, page snapshots, change notes, and weekly report inputs under workspace/intelligence/. Read firm profile first; for firm profile setup, see firm-context.

chann Bundle

Use when a software project needs README, README.ko, ARCHITECTURE, or USAGE documentation created, refreshed, reorganized, translated, or kept in sync without clobbering existing prose, including explicit "/gen-docs" or "$gen-docs"

chann Bundle

Use when the user wants a change summary plus a self-test quiz about a diff, branch, commit, or PR, including "diff 퀴즈 만들어줘", "변경사항 퀴즈", "요약하고 퀴즈로 확인해줘", "이 변경 이해했는지 퀴즈로 확인", "quiz me on this diff", "diff summary with quiz", "test my understanding of this change", "/diff-summary-quiz", or "$diff-summary-quiz". For a summary without a quiz use diff-summary; for a Markdown-only artifact use diff-summary-md; for defects use code-review.

lucking7 Skill

Publish, view, comment on, and edit markdown via Proof (proofeditor.ai) — create a shareable doc, read a shared doc, and make comment/suggestion/block edits over its API. Use when the user says "view this in proof", "share to proof", "publish to proof", or wants a shareable markdown surface for a spec, plan, or draft, including publish handoffs from ce-brainstorm, ce-ideate, or ce-plan. Do not trigger on "proof" meaning evidence, math proofs, proof-of-concept, or "proofread this".

lucking7 Bundle

Generate a time-windowed pulse report on what users experienced and how the product performed - usage, quality, errors, signals worth investigating. Use when the user says 'run a pulse', 'show me the pulse', 'how are we doing', 'weekly recap', 'launch-day check', or passes a time window like '24h' or '7d'. Configures via .compound-engineering/config.local.yaml and saves reports to docs/pulse-reports/.

focus-gts Bundle

Flag stale or outdated content across an AEM Edge Delivery Services site. Uses the query index to identify pages by lastModified date, scans content for staleness indicators (past dates, outdated references, seasonal content), and produces a prioritized freshness report. Use when auditing content currency, planning content refresh cycles, or identifying pages that need updating, archiving, or redirecting.

focus-gts Bundle

Assess and plan a migration from traditional AEM Sites to AEM Edge Delivery Services. Analyzes the source AEM site to inventory components, templates, content types, and integrations, then maps them to EDS equivalents and produces a migration feasibility report with effort estimates, risk areas, and a phased plan.

focus-gts Bundle

Generate a post-launch retrospective report for an AEM Edge Delivery Services project. Analyzes launch execution against the go-live checklist, compares planned vs actual timelines, evaluates performance under real traffic, reviews content migration completeness, and captures wins and improvement areas. Structured for both internal team review and client-facing presentation.

nahisaho Skill

Guide for creating technical documentation including README, user guides, API references, and changelogs. Use this when asked to write documentation, create user manuals, or generate API docs.

makigjuro Skill

Generate or update project documentation from code -- API docs, service docs, architecture docs, or runbooks. Use after adding endpoints, entities, events, or infrastructure changes, or when documentation may be stale.

rheinmir Skill

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

c0x12c Skill

Run deep research on a topic. Web searches, data collection, source checking, and a structured report. Use when the user needs more than a quick answer.

atman-33 Skill

This skill should be used when the user asks about "Zenn記法", "Zenn Markdown", "メッセージブロック", "アコーディオン", "埋め込み", "Zenn特有の記法", or mentions writing Zenn articles with specific formatting needs. Provides comprehensive knowledge of Zenn-specific Markdown syntax and best practices.

atman-33 Skill

Search, read, edit, or reorganize (rename/move/delete/list folders) development documentation and its folder structure stored in Google Drive, by accessing the locally synced folder (Google Drive for desktop) directly through the filesystem. Use when the user asks about design docs, specs, or other development documentation kept in Google Drive rather than in the repo, or wants to rename/move/delete files or folders there.

atman-33 Bundle

Compose a daily or weekly work log from git activity across the user's configured repositories and save it as Markdown (e.g. into an Obsidian vault). Use when the user asks for a work log, daily report, weekly summary, 日報/週報, or "what did I do today/this week".

technickai Bundle

Use when writing a plan, status report, incident summary, or recommendation for someone who does not work in the system being described. Leads with what changed for them, keeps the technical detail underneath, and gives them at most one real decision to make. Prevents the two failures that lose a non-technical reader: a wall of internals, and a list of options with no recommendation.

yuaicode Bundle

把某个 Slack 频道一段时间内的讨论收敛成一份"可落地需求"spec 文档。用户以 `/slack-to-spec <频道> <时间范围>` 调用时触发。读频道+决策密集的 thread+关联 canvas doc,抽取「需求点 / 决策(含撤销轨迹) / 待定问题」,按固定模板产出结构化、可追溯、能直接喂开发的 markdown。Use when the user wants to turn Slack discussion into a landable requirement/spec.

yuaicode Bundle

把 PDF / 飞书文档 / 会议纪要 / 长文本收敛成"可落地需求"spec(与 slack-to-spec 同一套模板)。当用户说"把这份文档/纪要/PDF 整理成需求 / 出个 spec"时触发。抽取需求点、决策(含被推翻方案)、待定问题,产出结构化、可追溯、能直接喂开发的 markdown。

alpoxdev Bundle

[Hyper] Produce a multi-source, source-backed markdown research report for fact-finding, comparisons, market/trend analysis, or evidence-backed recommendations across live web, official docs, GitHub, and local repo sources. Use when synthesis and citations are needed, not for one-source lookups.

alpoxdev Bundle

Use this skill when the user asks to create or refactor a reusable Codex skill folder, including SKILL.md trigger wording, instruction contracts, rules, references, scripts, assets, and validation checks. Do not use for generic documentation that is not a skill.

alpoxdev Bundle

[Hyper] Use when working on Hono projects or adding Hono into a codebase. Enforces Hono architecture rules for app composition, scalable route modules, middleware, validation, database/ORM boundaries, Drizzle integration, migrations, error handling, OpenAPI/Swagger documentation, testing, and typed RPC boundaries before any code change.

aws-samples Bundle

Manage customer-specific context that LLMs cannot know on their own — abbreviations, internal system names, org structures, key contacts, deal history, and relationship notes. Stores context as human-readable Markdown files organized per customer, following XDG Base Directory Specification. Loads the context a task needs, and updates it as new information surfaces. Use this skill when the user asks to look up, register, update, search or review stored customer context, or is preparing material for a specific customer and needs the accumulated background. Trigger keywords: "customer context", "顧客コンテキスト", "お客様情報", "顧客情報", "コンテキスト更新", "context update".

khujta Bundle

Documentation standards + Mermaid diagram library + the suite execution contract. Consulted by other gabe skills; not a user-facing command.

khujta Bundle

House chrome for published Artifacts — left-anchored content, a cog panel top-right, the fixed font roster, three suite skins, iconed section title pills set in a condensed grotesque, a 12px legibility floor, and motion-first visuals with a gated pause contract. Owns the build loop: design pass → kit → render gate → publish → report, plus two gated pattern libraries.

marin-community Bundle

Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.

charly-vibes Bundle

Review Documentation Quality

charly-vibes Bundle

Research Documentation Architecture

charly-vibes Bundle

Implement Documentation Topic

cipradu Bundle

Use when creating, rewriting, validating, or substantially refreshing README.md or repository front-door documentation for a project, package, application, CLI, skill bundle, plugin, template, or monorepo.

cipradu Bundle

Use when creating, revising, validating, or organizing reader-facing technical documentation such as tutorials, how-to guides, reference docs, explanations, API docs, architecture docs, runbooks, troubleshooting guides, docs sites, or docs updates that must stay aligned with source truth.

cipradu Bundle

Use when a rough feature, bug report, compliance request, operational/domain/product note, or existing-system change must become an engineering-facing spec before planning, implementation, migration, or review

cipradu Bundle

Use before acting on any troubleshooting or failure signal or proposed diagnosis/fix, including broken or unexpected behavior, failed tests/builds/commands, runtime errors, performance/flaky/regression issues, review/bug-report/human/AI claims, repeated failed attempts, or drift-prone library/API/runtime behavior. Mandatory before diagnosis or fixes; turn signals into current evidence, hypotheses, impact analysis, and verified resolution.

efoo-team Bundle

Only use when the user explicitly invokes /define (or $define in Codex). Never auto-invoke. 実装前の詳細な要件定義を行うためのスキル。プロジェクトの新機能や改修について、ユーザーと要求・要件の共通認識を確立し、技術的制約・設計方針・実装仕様を定義して実装の方向性を明確化する。ソースコードの実装は行わず、成果物として要件定義書（Markdown）のみを出力する。

efoo-team Bundle

Only use when the user explicitly invokes /skill-memo (or $skill-memo in Codex). Never auto-invoke. エージェントの推論・挙動について気づいた課題や、残しておきたい知見を efoo-team/skills の GitHub issue へ記録するスキル。記録先は efoo-team/skills 固定で、同じ課題の既存 issue があれば再発としてコメント追記する。プロダクトの不具合・要望を各プロジェクトのリポジトリへ起票するのは issue-report-dev / issue-report-user の役割であり、本スキルはスキル・指示ファイルの改善材料の蓄積に限る。

efoo-team Bundle

Only use when the user explicitly invokes /issue-report-dev (or $issue-report-dev in Codex). Never auto-invoke. エンジニア自身が書く GitHub issue の起票スキル。ログ・スタックトレース・失敗テストを取り込み、サブエージェントでファイル/シンボル単位まで根本原因を調査し、原因の仮説・修正方針案・受入条件まで含む issue を起草する。技術的な質問と期待仕様の確認を制限なく行い、想定変更領域の重なりでグルーピングして登録・統合する。非エンジニアからの報告受付は issue-report-user を使う。

efoo-team Bundle

Only use when the user explicitly invokes /issue-report-user (or $issue-report-user in Codex). Never auto-invoke. 非エンジニアの報告者から不具合報告や機能要望を複数まとめて受け付け、ケースごとにサブエージェントで並列調査し、想定変更領域の重なりでグルーピングして GitHub issue を新規登録・既存 issue へ統合するスキル。並列ワークツリー開発でコンフリクトしない単位に issue を編成することを目的とする。平易な言葉だけでヒアリングし、登録計画の承認を得てから gh CLI で書き込む。解決策・実装仕様の決定は行わない。エンジニア自身が起票する場合は issue-report-dev を使う。