2K skills · sorted by relevance
Show one skill in full — its team record or Library folder, versions, installs, health, and its eval report when it is a team skill — as Markdown boards from the terum-skills CLI. Use when the user names a skill and asks what it is, who installed it, how it scored, or what its receipt says.
The English summary is being prepared. Showing the original description.
List the skills on this machine (your Library) and the skills your team shares (the Marketplace) as Markdown boards from the terum-skills CLI. Use when the user asks what skills they have, what the team shares, what is installed, edited, untracked or missing an eval, or wants an overview of their terum-skills state.
The English summary is being prepared. Showing the original description.
Show a team skill's eval history — committed receipts per version and this machine's local runs — as a Markdown board from the terum-skills CLI, without fetching. Use when the user asks how a shared skill scored, which version passed, or what its receipts say.
The English summary is being prepared. Showing the original description.
Health-check a persistent markdown wiki. Use this when the user wants to find orphan notes, dangling links, missing pages, graph gaps, contradictions to review, or general wiki maintenance opportunities.
The English summary is being prepared. Showing the original description.
Ingest one new source into an existing persistent markdown wiki or established vault workflow. Use this when the user asks to add an article, PDF, note, URL, transcript, or other source into their wiki and wants the source filed, linked, indexed, and logged. If the wiki workflow does not exist yet, use $wiki-bootstrap first. This skill is for the ingest operation only.
The English summary is being prepared. Showing the original description.
Bootstrap a markdown workspace into a durable wiki structure. Use this when the user wants to initialize a wiki from an empty folder or convert an existing pile of notes into a more structured persistent wiki.
The English summary is being prepared. Showing the original description.
Answer questions against a persistent markdown wiki and optionally file the answer back into the wiki. Use this when the user asks what their wiki says about a topic, wants a comparison across notes, or wants citations grounded in the wiki.
The English summary is being prepared. Showing the original description.
知识检索专家（瑞卡 Rika）。使用 RAG 技术处理多格式文档（PDF/Word/Excel/Markdown/HTML），构建向量知识库，进行语义检索并为问答提供带来源引用的上下文增强回答。 触发词：由 copilot-team-lead 主理人调度执行，不直接面向用户。当主理人下发文档检索、知识提取或 Phase 4 知识增强任务时激活。
The English summary is being prepared. Showing the original description.
报告发布员（傅梓铭 Fu）。由 research-chief-editor 主理人在 Phase 5 调度，整合所有部分（标题/日期/目录/引言/章节正文/结论/参考文献/审稿警告）输出最终 Markdown 研究报告。执行终校：格式统一、章节编号连续、分隔线、超链接检查、参考文献去重、术语一致性检查。不修改研究内容本身。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当 Phase 4 完成后，主理人下发 Phase 5 发布任务时激活。
The English summary is being prepared. Showing the original description.
洞察报告撰写师（若溪 Rex）。综合多源数据分析结果、知识检索发现和可视化图表，撰写结构化分析报告。输出包含执行摘要、核心发现、图表和决策建议的 HTML/Markdown 报告。 触发词：由 copilot-team-lead 主理人调度执行，不直接面向用户。当主理人下发 Phase 3 报告撰写任务时激活。也可响应纯报告撰写需求。
The English summary is being prepared. Showing the original description.
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
The English summary is being prepared. Showing the original description.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
The English summary is being prepared. Showing the original description.
Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.
The English summary is being prepared. Showing the original description.
Guides agents and users to create standards-compliant agent definitions using templates in markdown frontmatter format, ensuring context gathering, clarity, and proper metadata. Forces agents to ask clarifying questions when context is insufficient. Token-efficient documentation required. All content must be in English. Trigger: When creating a new agent definition, setting up project agents, or documenting agent workflows.
The English summary is being prepared. Showing the original description.
Best practices for designing Claude Code agent files (.claude/agents/*.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official guidance with battle-tested patterns from agent team usage.
The English summary is being prepared. Showing the original description.
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
The English summary is being prepared. Showing the original description.
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
The English summary is being prepared. Showing the original description.
Search and edit structured markdown knowledgebases with the Hyalo CLI: frontmatter, tags, tasks, links, and document structure.
The English summary is being prepared. Showing the original description.
Maintain Markdown Architecture Decision Records with Hyalo's MADR profile and table-of-contents commands.
The English summary is being prepared. Showing the original description.
Start a new Flywheel planning round for a Forge feature. Writes the initial markdown plan to .flywheel/plans/ and gives instructions for sending it to competing frontier models. Use at the very beginning of a new feature or subsystem.
The English summary is being prepared. Showing the original description.
Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Every bead must be executable without reopening the plan. Use after the plan has converged.
The English summary is being prepared. Showing the original description.
Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Treat this as a distinct translation problem, not task extraction. Use after /plan-synthesize produces a stable hybrid plan.
The English summary is being prepared. Showing the original description.
Start a new Flywheel planning round. Produce initial markdown plan, route to competing frontier models, synthesize hybrid, refine 4–5×. Use before any coding begins on a new feature.
The English summary is being prepared. Showing the original description.
Use for local Granola archive search, sync freshness, notes/transcripts/panels, Markdown export, snapshots, Keychain-safe source debugging, and Graincrawl repo/release work.
The English summary is being prepared. Showing the original description.