All categories
AI & Agents
LLMs, agent workflows, RAG, MCP, prompting, and AI app patterns
- 307,718
- 12,822
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse ai & agents skills
Showing 3,025–3,048 of 307,718 skills
- Readout写出别人一遍就能读懂的回复和工作汇报：一句话只说一件事，动作放在动词里，不确定性绑在它所属的那条结论上。当用户说 /readout、「你的汇报太难读了」「说人话」「别写得像 AI」，或者需要修正某次运行的汇报风格时使用。下面的正文独立成篇：整段贴进 AGENTS.md 或 CLAUDE.md，就能每轮生效，不必调用。Votes: 0GitHub stars: 12
- Lowband低带宽协作模式：用户注意力或脑力耗尽时的响应协议。当用户调用 /lowband 或 $lowband，或说「低带宽」「省脑」「脑子不够用了」「太累了，简短点」时启用；每轮持续生效，直到用户说「恢复正常」或带 off 参数再次调用。工作能力不降级，只压缩呈现、过滤决策。Votes: 0GitHub stars: 12
- Long Horizon用一次长程自主运行执行一个定稿的目标——数小时的 agent 工作推完整个验收台账，人只出现在两道闸：运行前的 spec、运行后的 review。适用于 /long-horizon、「长程执行这个任务」「跑一个长程目标」，或在已有 `.long-horizon/` 工作区的仓库中恢复工作时。入口交互式反复迭代；运行由 fan-out 驱动、副作用被授权信封约束；进展只认证据；实时 report.html 以 DAG 呈现台账。Votes: 0GitHub stars: 12
- Just Ask一次性「只回答」回合——用户是在问问题，不是在派活。用 /just-ask 加问题调用（如「/just-ask 这个测试为什么会偶发失败」）。仅该回合内：只读调查、给出经过分析的回答；不改文件、不跑会改状态的命令、不写计划、不动手修。下一条消息恢复正常。以显式调用为主；用户说「只问一下，别动手」「你就解释，不用修」时同样适用。Votes: 0GitHub stars: 12
- Handoff当另一个 agent 或 session 要接管任务或继续未完成工作时，生成最小充分交接。触发语：/handoff、「把任务交给下一个 agent」「生成 handoff」「让另一个 session 继续」、session 转移、任务所有权转移，或当前上下文退化时重开一个干净 session（交接给未来的自己）。持久 artifact 用引用不用复制，输出前抹掉 secrets。Votes: 0GitHub stars: 12
- Fan Out把当前任务派发给多个 subagent——但先检查这次拆分到底值不值。适用于 /fan-out，触发语：「用多智能体做」「派发出去」「拆给多个 agent 并行」，或任务能拆成真正独立的子任务时。按上下文耦合度拆解，spawn prompt 用 handoff 的纪律写成任务契约。Votes: 0GitHub stars: 12
- Ctx Research基于项目持久 context 体系的深度调研。适用于 /ctx-research，触发语：「基于 context 调研 X」「结合我们的 contexts 做深度研究」。先读已有 contexts，把问题磨到真正的知识缺口上，再多智能体展开调研，关键论断做对抗验证，结论写回去。Votes: 0GitHub stars: 12
- Ctx Grill用一场带上下文的追问把方案、决策或想法拷问到位。适用于 /ctx-grill、「拷问这个方案」「帮我把方案过一遍问题」「压测一下我的思路」，或用户希望在动手前压测自己思路的场景。先读持久 contexts（已回答的绝不再问），按「答案会不会改变方向」逐个提问并附推荐答案，边际收益递减即停，敲定的决策写回归档。仅限交互场景——CI、循环等无人值守运行中绝不可调用。Votes: 0GitHub stars: 12
- fgiSynthetic focus group (FGI) moderator. Before real research, run a 5-phase simulated focus group on an MVP, mockup, or policy draft with N isolated persona subagents to surface questions, risky assumptions, and edge cases. Every response is labeled as a synthetic persona response, never as user evidence. Use on /fgi, or when the user asks for user feedback, an FGI, or reactions right after writing an MVP, mockup, or policy draft.Votes: 0GitHub stars: 2
- LuxIn-browser visual review and UI editing with lux for local projects, dev servers (localhost/127.0.0.1), and static HTML files where code changes will be applied directly to the user's codebase. Use when the user wants to visually edit or review their own app, or runs /lux. Do NOT use for external third-party websites or online articles (use /lux-web instead).Votes: 0GitHub stars: 3
- Lux WebIn-browser visual inspection, teardown, discussion, and explanation of external, third-party websites, online articles, and competitor designs using lux. Use EXCLUSIVELY for external sources and remote internet pages that are NOT hosted by the user and where there is no local codebase to modify. Do NOT use for user-hosted apps, local dev servers, or local HTML files (use /lux instead).Votes: 0GitHub stars: 3
- MapearGera ou atualiza o mapa de arquitetura de um repo/módulo do workspace atual em `<workspace>/claude/mapas/`, indexado pelo brain MCP. Use quando o usuário pedir "/mapear <repo>", "mapeia o <repo>", ou após mudanças estruturais grandes num repo (novo módulo, pasta reorganizada, integração nova).Votes: 0GitHub stars: 2
- Gm TriageTurn a raw report — a hospital's message, a stack trace, a loose idea — into qualified demand at the door of the team board (the team board declared in the workspace CLAUDE.md). Classifies type/severity/class/module with written criteria, deduplicates against open and closed issues before creating anything, fills the template for the type, records origin and requester, and parks the card in 📥 Triagem. Also routes away what is not demand. Use whenever something arrives from outside the board,...Votes: 0GitHub stars: 2
- Gm Tech SpecDEPRECATED - superseded by gm-spec, which fuses requirements + technical specification into a single document with adversarial critique and a human approval gate. Use /gm-spec instead.Votes: 0GitHub stars: 2
- Gm SpecCreate the single specification (requirements + technical) for a board card — the contract that makes AI implementation safe. Seeded by the card, built through codebase exploration and focused Q&A, hardened by an adversarial critique, and gated by explicit human approval. Publishes the spec as a comment on the card. Replaces the old gm-prd + gm-tech-spec pair as the default path (gm-prd remains only for genuinely new product areas).Votes: 0GitHub stars: 2
- Gm ShipClose the implementation loop - verify every task complete, run the full suite, push, open the PR carrying the acceptance-criteria contract and the dev-validation checklist, referencing the board card, and move the card to code review. Use after the last gm-implement task is approved and committed.Votes: 0GitHub stars: 2
- Gm ReleaseCut the release train from the team board (the team board declared in the workspace CLAUDE.md) — read the validated queue (🚂 Release, plus cards closed while in 🧪 Validação em Dev), reconcile it against what is actually merged in dev, classify the train as trivial or sensitive (migrations / data treatment), open the dev→main PR, tag with calver, publish dual release notes, run the BLOCKING post-deploy verification for sensitive cards, move the cards to ✅ Produção and produce the list of req...Votes: 0GitHub stars: 2
- Gm PrdCreate a Product Requirements Document (PRD) through deep conversational Q&A, seeded by a board card when one exists. Use when a card is picked up for implementation, or when planning any feature that needs clear requirements before coding. Writes planning/<folder>/PRD.md and publishes the PRD as a comment on the card so downstream steps (tech spec, CI review) can find it on GitHub.Votes: 0GitHub stars: 2
- Gm Plan TasksBreak a spec into ordered, independent implementation tasks — each task file is the complete prompt for a fresh agent. Proposes the whole breakdown at once for the user to veto/adjust; enforces the 6-8 task ceiling; mirrors the task list on the card. Use after gm-spec, before /gm-implement.Votes: 0GitHub stars: 2
- Gm ImplementExecute the next pending task of a planned feature - right branch in the right repo (created linked to the card via Development field), task file as the prompt, tests run BEFORE presenting, risk-ranked summary, commit only after explicit approval, deviation protocol when reality contradicts the spec. Use after gm-plan-tasks, once per task, preferably in a fresh session.Votes: 0GitHub stars: 2
- Gm HotfixDrive a real S1 production emergency — faturamento parado or corrupted data — down the expedite rail on the team board (the team board declared in the workspace CLAUDE.md). Proves the S1 criterion and the one-at-a-time limit, opens a minimal card carrying repro + risk + the verification query, branches release/hotfix-* from main (never from dev), implements with tests, opens the PR to main with mandatory AI + human review, runs the BLOCKING post-deploy verification, tags, back-merges into dev...Votes: 0GitHub stars: 2
- Gm ExploreExploratory, read-only investigation of how something currently works in the codebase. Use when the user wants to understand the current state of a behavior, rule, or flow ("how is X today?", "can a user do Y?") before deciding whether it should change. Checks the team board for existing cards on the topic, answers with file:line evidence, never proposes or implements solutions, and — when the question came from a ❓ Dúvida card — publishes the finding on it and closes it as answered knowledge.Votes: 0GitHub stars: 2
- Gm CorrecaoTurn the CI review's parecer on a PR into decisions on the record - every finding verified against the spec, then fixed, refuted, or promoted to a card, with a reply on each inline comment. Use after the review workflow posts its findings on a PR that is already in code review, before handing the PR to a human validator.Votes: 0GitHub stars: 2
- Gm CardQualify demand into a direction card on the team board (the team board declared in the workspace CLAUDE.md) — either creating it from a one-line direction, or promoting an issue that gm-triage left in Triagem. Captures current state with evidence, desired direction, motivation and MANDATORY acceptance criteria (gate G1), using the right template per type (bug vs melhoria vs débito), and suggests the route (completa/curta). Use right after a gm-explore or a gm-triage, or whenever registering d...Votes: 0GitHub stars: 2