Docs & Writing

bob798 Skill

Generate executable integration-test specs, skeletons, and PR reports for Spring Boot + Spring AI services. Trigger when the user wants to write integration tests, add wire-level ITs, draft an IT spec, or produce a PR test report.

bob798 Bundle

通用周报生成 Skill。4 段结构（总目标 / 本月 / 下周 / 风险）+ 双进度条对比（任务 vs 时间）+ 总目标进度条 + Markdown 文字版（一键复制）。输出单页 PNG（领导面向汇报）。当用户说"做周报"、"出周报"、"本周汇报"、"周五汇报"、"生成周报"、"周会用图"时触发。适用于任意项目的周期性进度汇报。

bob798 Skill

从 Claude 项目记忆和 Git 历史中自动提炼结构化能力画像。 触发词："提炼能力"、"能力画像"、"能力分析"、"mine capabilities"、"生成画像"、"我会什么"。 输出：结构化能力画像（JSON + Markdown），可直接用于简历生成或 Gap 分析。

dailybothq Skill

List, inspect, submit, update, and transition form responses via Dailybot — including forms with workflow states and audience-scoped permissions. Also authors forms — create and configure a form (workflow states, permissions, anonymous/public/approval, ChatOps command) and manage its questions (types, report titles, variations, conditional logic). Use when the developer wants to see available forms, fill out a survey, continue an in-progress response, move a response between states, read prior responses, or create/configure a form. Do not use for daily check-ins — those go through dailybot-checkin.

dailybothq Skill

Give kudos to a teammate or to an entire team via Dailybot to recognize their contributions. Use when the developer wants to thank or recognize one person, or recognize a whole team (e.g. "kudos al equipo Engineering"). Do not use for general progress reports — those go through dailybot-report.

dailybothq Bundle

Report work progress to Dailybot. Activate after completing a discrete task or subtask, or after any batch of edits that modifies 3 or more files. Compose a standup-style update describing what changed and why.

dailybothq Skill

Drive the full check-in lifecycle via Dailybot — list and complete pending check-ins, see pending/completed status for a day, inspect a check-in's questions and schedule, browse response history, edit or reset a submitted response, and backfill or future-date responses. Also authors check-ins — create and configure a check-in (schedule, participants, reminders, privacy, smart/AI) and manage its questions (types, report titles, variations, conditional logic). Works headless with an API key. Use when the developer asks to fill in their standup, answer daily questions, check what check-ins they have, edit or reset a check-in, review past responses, or create/configure a check-in. Do not use for free-text progress reports — those go through dailybot-report.

dailybothq Skill

Discover the report channels (Slack/Teams/Discord/Google Chat) available to you via Dailybot, so their UUIDs can be attached to forms and check-ins with --report-channel. Use when the developer needs a channel UUID for form/check-in authoring.

dailybothq Skill

Open (or idempotently reuse) a private Slack group DM (MPIM) that includes the Dailybot bot, then optionally post a message or report to it. Use when the developer wants to start a Slack group with specific teammates plus the bot — e.g. "open a group DM with Jane and Bob and send them the analysis report". Slack only, org-admin only. Distinct from dailybot-chat (which posts to existing channels/DMs) and dailybot-channels (which discovers report-channel UUIDs).

dailybothq Skill

Report the status of a Deep Work Plan — completed tasks, what's left, and blockers — without executing. Use when the developer asks for plan status or what remains.

davidvujic Skill

[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Detect and report circular imports introduced by the namespace migration.

hummingbot Skill

Run the MM bot status report: running bots, open/hold-mode positions, closed position breakdown (TP/SL/Early/Hold), PnL, volume, and error summary.

leadupofficial Bundle

Find, compare, and recommend free or third-party public APIs for LeadUp projects (websites, SaaS, CRM, hosting tools, Flutter apps, automation) using public API directories (public-apis/public-apis), official documentation, GitHub examples, RapidAPI, ApyHub, and Postman public collections. Always verifies the chosen API against the official docs before recommending, scores candidates on fit / docs / pricing / reliability / auth / CORS / commercial use, and outputs a candidate table, best + backup picks, env placeholders, integration notes, and an implementation + test plan. Use when the user says "find API", "free API", "public API", "API options", "best API for this feature", "API idea", "third party API", "API marketplace", "check public APIs", "use public-apis repo", or "API for my project".

leadupofficial Bundle

Generate professional LeadUp client and business documents — proposals, project briefs, estimates, status reports, developer docs, API-access request emails, and handoff documents — in clean PDF-ready Markdown. Use when the user says "create document", "client proposal", "developer document", "API request email", "project report", or "handoff document".

leek Bundle

Configure this repo for the engineering skills: the markdown tracker layout, triage status vocabulary, and domain doc layout.

leek Bundle

Exercise a change end to end in the running application (hit the route, run the command, click through the page) and report what actually happened. Use after tests pass, when a change needs proving in the real app, or when another skill's build step ends.

leek Bundle

Investigate a question against high-trust primary sources and capture the findings as a cited Markdown file. Use when the user wants a topic researched, docs or package facts gathered, reading legwork delegated, or a wayfinder research ticket resolved.

leek Bundle

Break a spec into tracer-bullet vertical-slice tickets with explicit blocking edges, take one green light on the breakdown, and save one markdown file per ticket beside the spec.

leek Bundle

Turn a decision the user can't fully answer into a Markdown questionnaire for someone else to fill in, async or over a meeting.

leek Bundle

Run a documentation sweep so repo docs match the current implementation.

lichamnesia Skill

Rewrites inline links into reference-style links when the user asks to clean up long markdown docs.

schroneko Bundle

Check Luma event guests against X profile, follow, mutual-follow, affiliation, and recent-account-activity requirements. Use when Codex needs to review a Luma event guest table, extract pending guests and X profile links, identify missing/invalid/deleted/protected X accounts, use X relationship lookup to verify whether guests follow the logged-in organizer account, check whether candidates have posted from their own X account within the last month excluding repost-only activity using read-only internal APIs, prioritize mutual follows before followed-by-only candidates, check whether a specific X handle registered and what current Luma status it has, manage X rate limits without causing 429s, and report decline or approval-support candidates without ever performing approve, decline, or other guest write actions.

scottwater Bundle

Investigate a focused question against high-trust primary sources and capture cited findings as one Markdown note. Use for documentation, API, specification, or local knowledge-base research, including AFK Wayfinder research tickets.

team-attention Bundle

This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists. Phase 1: validate changed files against .hoyeon/rules/ checklists and report PASS/WARN. Phase 2 (conditional): propose rule additions when unmatched patterns are detected. Essential before git push. Trigger phrases: "check", "checklist", "verify changes", "what did I miss", "pre-push check", "cascading changes", "any more changes needed", "update checklist", "update rules", "rules update", "체크", "체크리스트", "변경 확인", "빠뜨린 거 없나", "push 전 확인", "뭐 더 건드려야 해?", "연쇄 변경 확인", "규칙 갱신".

team-attention Skill

Analyze an open-source project from What/Why perspective (not how-it's-implemented). Use when the user says "/analyze-oss", "분석해줘 이 오픈소스", "이 레포 뭐하는거야", "analyze this repo", "what does X do", "이거 왜 쓰는거야", "이 라이브러리 분석", provides a GitHub URL and wants understanding, or asks to deeply understand an OSS project's purpose, value, target users, and usage flow. Clones the repo to ~/opensource-analysis/<repo-name>/ (git pull if already exists), dispatches parallel subagents per analysis lens, then synthesizes a What/Why-focused report in chat. Supports optional user-specific follow-up questions.

team-attention Bundle

Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. Spawns multiple WebSearch research agents AND browser-explorer agents (via chromux for JS-heavy/dynamic sites), plus a Gemini CLI deep research source, then synthesizes everything into a cited report. Uses WebSearch, WebFetch, chromux browser-explorer, and Gemini CLI. Invoke with /deep-research <topic>.

team-attention Skill

Hoyeon deep research workflow for Codex. Use when the user invokes "$hoyeon-deep-research" or wants a multi-channel cited research report using web search, browser extraction, and optional Gemini. This adapter loads the canonical deep-research skill and follows its Codex runtime surface.

trycomp-io Bundle

Chief of Staff conversacional do CHRO. Mantém contexto (stakeholders, cadências, calendário, open loops) e ajuda com pré-meeting briefs, visão semanal, drafts de comunicação (email/Slack/IM em PT-BR ou EN), strategic prompts baseados em cadência, e orquestração com os outros skills da Comp (paygap, attrition, comp-ratio, board-slide, decision-memo, etc.). Dual-mode: works in Claude Code (contexto persistente em ~/.comp-skills/chro-context.json via script) AND Claude Cowork (contexto na conversa ou num Project do Cowork; todo output gerado inline em markdown). Trigger em "brief pra reunião X", "como tá minha semana", "drafta um email pro CEO/CFO/board", "o que devo estar fazendo agora", "minha CoS", "open loops", "adicionar action item". Mantida pela Comp.

evan-daruwalla Bundle

Execution loop for work longer than one sitting or more than ~7 steps: a numbered plan where every step ends in a check, riskiest step first, a one-line state tracker at the top of each turn, an iteration budget, and a progress lock — the same command failing the same way twice means change approach or stop and report NO-PROGRESS (hooks/no-progress.js fires this deterministically on PostToolUseFailure). Invoke: "long-task", "plan this out", "this is a big one", multi-hour or multi-session work. Small work → small-task. Cheaper-tier delegation → opus-workers. Launch risks → pre-mortem.

rubyeyedreaper Bundle

Use when a session must say something to another session rather than to a person — reporting back to a coordinator, messaging a peer or worker, deciding what a delegated session should put in its terminal versus in its report, or asking who is actually reading this output. Also on "tell the coordinator", "report back", "send it to the other session", "cross-session message", "the worker is too chatty", "cut the chatter", "nobody is reading this terminal", and when a message was sent and the reader never acted on it.

rubyeyedreaper Bundle

Use when a human addresses the fleet itself rather than the work — asking what is running, for a status report, to pause or halt everything, to stop and wait a while before resuming, or to stop so they can start a fresh session. Also on "what's running", "how's it going", "hold everything", "freeze the fleet", "pause the workers", "resume in an hour", "wait 20 minutes then continue", "stop so I can pick this up in a new session".

rubyeyedreaper Bundle

Use when a plan, design, claim or requirement must be stress-tested against actual documentation and source material rather than against opinion — a requirements interview over a heavy doc or spec corpus, an unfamiliar API or library whose real behaviour is not yet established, a claim that "the docs say" something nobody has read, or a design whose evidence is asserted but not cited. Also use when an interview must leave a paper trail — ADRs and glossary entries — instead of ending in the conversation.

l3digitalnet Skill

Generate documentation for Home Assistant integrations. Creates README.md, Home Assistant docs pages, and HACS info pages. Use when asked about documentation, README, docs, or making documentation for an integration.

crystian Bundle

Lint the codebase and report style violations.

kehwar Skill

Query the live Frappe database, read private/public .json.gz snapshot files from disk, execute whitelisted Python methods, and run arbitrary scripts with full Frappe context via bench console. Use when debugging Frappe issues in development — checking document field values, inspecting stored report/snapshot files, running live queries, or calling whitelisted server methods from the terminal.

kehwar Skill

Expert guidance for writing the .js controller for a Frappe Standard Script Report. Use when defining report filters, implementing formatter callbacks, adding onload toolbar buttons, setting default filter values, using get_datatable_options, or after_datatable_render hooks.