yuanhaorannnnnn
UserManifest-driven, contract-tested skills for coding agents - one install for Claude Code and Codex. doctor-verified workflows with explicit gates instead of a prompt dump.
Categories
Indexed Skills (18)
acquisition
Load when the user shares a video or article URL and wants to save it into the wiki, or says "把这篇/这个视频消化一下", "提取干货", "整理要点", "ingest this", "summarize into the wiki". Handles X/YouTube/Bilibili/Xiaohongshu videos and article URLs (including public WeChat Official Account links and albums), PDF files, or local Clippings files.
chart
深入学习一个软件、仓库、开发工具、平台或产品，建立可持续更新的 Study Hub， 用官方文档、源码实现和本机运行三类证据回答"它是什么、怎么工作、问题在哪"。 触发于"深入学习 X"、"系统了解 X"、"建立 X 的学习路线"、"study this repo/product"、 "帮我搞懂这个工具"。 不用于单篇文章/论文/课程/知识库摄入（用 acquisition），不用于一次性问题或直接改代码（用 execute）。
after-action
Use only after a concrete defect, failure, or difficult technical problem has been resolved and the useful output is its incident-specific troubleshooting story: symptom, diagnosis, failed attempts, root cause, final fix, and whether it is truly resolved. Trigger on "故障复盘", "debug 复盘", "怎么修好的", "fix log", "写一份修复记录", "post-mortem", or "记录一下这个 bug 的解决过程". Do not use when the user only wants one reusable guardrail; use codify. Do not use for a formal end-to-end report on an entire completed task; use sanitize report mode.
breach
Generate fast single-page HTML artifacts for daily development communication: status pages, HTML slide-like pages, flowcharts, PR writeups, incident pages, and structured discussion digests. Use the discussion-digest mode for email threads, GitHub issues/PRs, chat logs, and forum discussions when the user asks "梳理这个讨论", "这条线程结论是什么", "理一下参与人立场", "digest this thread", or "summarize this email chain". Use the general page mode for "quick HTML page", "快速 HTML 页面", "做个 HTML status page", "画一个 HTML flowchart", "做个 HTML slide page", "生成报告页面", "visualize this as a page", or "把这个做成 HTML". When the task already calls for a general page, support an optional ELI5 content profile for explicit requests such as "ELI5", "像给小孩解释", or "给新手讲". Not for native documents, native slide decks, spreadsheets, or full product visual design.
codify
Use only when the desired output is one compact, reusable guardrail that prevents a mistake from recurring. Trigger on "write this down as a rule", "remember this mistake", "capture a lesson learned", or "add a guardrail for next time". Do not use for a narrative of one incident or debugging journey; use after-action. Do not use for an end-to-end report on a completed task; use sanitize report mode.
conops
基于 conversation 对话记录、planning 文档和代码变更，生成面向产品、测试、 开发同事的技术开发设计方案文档（Markdown）。 触发词："生成开发方案"、"写设计评审文档"、"生成技术方案"、"write design doc"、 "dev design"、"把这个 feature 的方案整理出来"、"写一个 XX 的技术方案"。 注意：这不是需求文档或 PRD，而是技术实现方案，重点回答"怎么做"和"为什么这么做"。 即使用户没有说"开发方案"这四个字，只要场景是"开发前的技术方案编写"—— 比如用户说"整理一下 XX 传感器的设计"、"把 XX feature 的架构写出来"、 "写个文档给评审会看"——都应该触发此 skill。
cover
Generate a customized DESIGN.md (design token specification) for a product or project. Reads the awesome-design-md reference library (71 DESIGN.md files from real products), synthesizes the best-matching references with the project's own content and style intent, and produces a tailored design spec. Trigger on: "visual design", "视觉设计", "DESIGN.md", "design spec", "设计规范", "产品视觉方案", "给我一个设计规范", "match design style", "参考 XX 风格做设计", "generate design tokens".
execute
执行具体任务并在 Canon task page 留下可恢复记录。用户说“执行”“开始做”“开动” “落实”“实施”“修改”“修复”“处理这个任务”“帮我做”“委托执行”“交给其他模型”， 或显式调用 $execute / /execute 时使用。默认自动选择当前 agent 或一层委托；--direct 和 --delegate 强制覆盖。--goal 创建 goal.md；--plan 创建详细计划并隐含 --goal。普通问答、 解释、只读 review、单纯调研不触发；已知需求/缺陷 ID 分别由 tasking/repair 管理。
herdr
Inspect or control Herdr. In a Herdr-managed pane (HERDR_ENV=1), use the local CLI; from ChatGPT Web, Mobile, or Desktop, use the herdr_control MCP Bridge and never fall back to the CLI.
neutralize
Use for nontrivial or recurring defects that need explicit root-cause evidence, symptom reproduction, adjacent-pattern scanning, and a machine-readable fix gate. Strong triggers: repeated regression, build/runtime failure, supplied logs or stack traces, cross-module breakage, "find the root cause", or "check for similar issues nearby". Focus on root cause, apply the smallest safe fix, then scan nearby code for the same pattern. Do not auto-trigger for an obvious, localized routine fix that ordinary implementation plus focused validation can resolve safely.
paperwork
起草技术文档，或进行会改变文档结构、论证、证据、结论或读者理解的重写与审阅时，围绕读者任务、信息关系、证据强度和工程判断组织内容，并识别低信息量的生成式填充。适用于设计、说明、调研、评估、操作、复盘和技术参考；仅做不改变技术含义的拼写语法校对、格式调整、术语替换、局部句子编辑或忠实翻译时不触发。
passdown
Transfer context from another coding agent session into the current session. Auto-detects runtime (Codex/Pi/Claude Code/DSH). Defaults to current directory — no parameters needed for same-repo handoff. Multi-runtime sessions merged by recency with focus filtering and deduplication. Trigger on: "agent handoff", "handoff", "接手上下文", "agent交接", "上下文切换", "attach session", "继续上一个agent的对话", "上次在这个目录做了什么". Also use after starting a fresh conversation to continue a focused thread without resuming the full old transcript.
repair
云效缺陷单修复流程 skill。用于处理已经由共享 Phase 0 拉取到 `/media/yhr/2T/yunxiao/bugs/<bug-id>/` 的缺陷单，四阶段：Intake 读取缺陷单、切输入分支、结合代码分析、生成 root-cause.md、fix_plan.json 和 breach 对齐页、将状态改为 修复中；Fix 按修复方案和 neutralize 工作流修复，按条件 触发 codify 和 after-action；Closeout 改为 集成测试中；Clear 合入主分支打包关闭。 Make sure to use this skill when the user says 处理缺陷、修复缺陷单、 bug 单、云效缺陷、进入修复中、提交回归验证、缺陷误报、缺陷转需求， or invokes `/repair Intake`, `/repair Fix`, `/repair Closeout`, `/repair Clear`. Do NOT use for general code debugging without a Yunxiao bug id; use neutralize for ordinary bugfix/debug requests. repair never changes bug assignee/owner.
sanitize
Two-mode completion workflow. Closeout mode scopes and publishes the current task with git commit/push, updates the Canon task page, and promotes durable decisions/artifacts. Trigger on "开发完成了", "收尾", "wrap up", "完成这部分", "提交并保存", "done with this", or "commit and save". Report mode generates a formal evidence-backed Markdown report for an entire completed task: rationale, implementation, evaluation, outcome, and remaining work. Trigger on "完整任务技术报告", "完成后的技术总结", "成果汇报", or "post-task report". Report mode does not commit or push unless the user also requests closeout. Cross-runtime: Claude Code, Codex, Kimi, and Pi.
tasking
需求开发全流程作战指挥系统。四阶段：Orient(情报分析→方案)、Briefing(上传知识库→评审日程)、 Engage(状态→开发中→execute --plan→启动/goal)、Turnover(交付物→系统测试)。 Make sure to use this skill whenever the user: - mentions a demand/requirement ID (e.g. JHBN-7712, #1234) and wants to process it - says 处理需求、需求开发、写方案、方案评审、开始开发、进入开发、交付、提测 - asks to upload a design doc to knowledge base or schedule a review meeting for a demand - wants to change a demand status to 开发中/系统测试 or post deliverable links - uses /tasking or any of its modes: Orient, Briefing, Engage, Turnover Do NOT use for: checking personal todos, writing weekly reports, code review, creating new skills, general git operations, or translating documents — even if a demand ID is mentioned in passing.
traceback
Evidence-backed three-way delivery alignment gate: approved design/fix plan/ acceptance contract → implementation → mapped and executed tests. Produces a machine-readable alignment record, deterministic Markdown view, and gate result. Use when an explicit design document, fix plan, acceptance checklist, or public contract exists and the user/workflow asks whether delivery is complete: "delivery check", "delivery align", "检查交付一致性", "对齐检查", "gap scan", "追溯检查", "三阶段对齐", "design-implementation gap", "are we missing anything from the spec", "方案和代码一致吗". Run after implementation validation and Review Gate, before sanitize/Turnover. Do not trigger for stack traces, runtime exceptions, or generic line coverage.
x-likes-digest
读取 X/Twitter 账号新增的 Likes，按当周实际内容生成一封偏娱乐的 HTML 周报并发送到 Gmail。触发于“处理本周 X 点赞”“X likes 周报”“把最近点赞发我邮箱”；不摄入 Wiki，不点赞或取消点赞，也不用于单个已给 URL 的普通摄入。
go-nogo
评估用户描述的功能是否需要新建 skill，还是可用现有工具或已有 skills 实现。 当用户描述一段功能、说"我想实现..."、"能不能做..."、"这个要不要封装成 skill"、 "需不需要创建一个 skill"、"帮我评估一下这个功能"、"这个功能用现有工具能做吗"时触发。 也触发于用户询问某个需求的最佳实现方式，或纠结是否值得投入创建 skill 时。 核心目标是防止技能膨胀和重复造轮子，给出客观、可执行的建议。
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.