Use ONLY when the user says they do not know which master or which teaching mode to use — 不知道问谁, 该找哪位祖师, 该用哪个模式, 有哪些法师, which master should I ask, help me choose. This is a router, not a teacher: it names a destination and stops. If the user asks an actual doctrinal or practice question, do NOT invoke this — let the matching master skill answer directly.
npx skills add https://github.com/xr843/Master-skill --skill master-help
> 本 skill 只做导航,不讲教义。选定目标后立即交棒,不要代替祖师回答。
用户不知道该用哪位祖师 / 哪个教学模式时,给出目标并停手。
不要在这里解释教理、给修行建议或引用经文——那是各 master skill 的职责,它们各自带着 citation_contract 和 HARD-GATE,本 skill 没有。
路由表在仓库根的 routing.json(mode_rules / topic_pairings / default_pairing),
祖师关键词在各 prebuilt/<slug>/meta.json 的 search_scope.keywords。
两处都是机器可读的单一数据源——不要凭记忆列举祖师或关键词,读文件。
确定性实现同样可用:
master-skill recommend "<用户原话>" --json
能跑就跑它,把结果转述给用户;跑不了再按下面的顺序人工走一遍。
与 routing.json.mode_rules 的 order 一致:
1. 命中「学习计划 / 入门 / 先学什么 / 从哪开始 / 按什么顺序」 → /master-curriculum
2. 命中「辩论 / 谁更对 / 高下 / 之争 / 之辩 / 分判」 → /master-debate
3. 命中「对比 / 比较 / 不同 / 异同 / 各派怎么看」 → /compare-masters
4. 都不命中 → 单位祖师:按 meta.json search_scope.keywords 打分
5. 仍无命中 → routing.json.topic_pairings 主题配对
6. 再无命中 → routing.json.default_pairing
第 4 步打分规则:关键词长度 ≥ 2 才计分(单字 空 戒 定 慧 苦 禅 业
会在日常汉语里误命中,已被 min_keyword_length 排除);命中数高者优先;
平局时优先不同传统,仍平局按 slug 字典序。最多 3 位。
你的问题看起来是 {判断},建议:
/{目标} — {一句话理由}
(其他可选:{备选1}、{备选2})
三行以内说完。用户要的是入口,不是综述。
/compare-masters 的 HARD-GATE 一致由目标 skill 自己的边界规则处理密法内容
| 传统 | 祖师 |
|------|------|
| 印度 | master-nagarjuna |
| 汉传 | master-kumarajiva · master-zhiyi · master-fazang · master-xuanzang · master-huineng · master-yinguang · master-ouyi · master-xuyun |
| 藏传 | master-atisha · master-tsongkhapa · master-milarepa |
| 南传 | master-buddhaghosa · master-mahasi-sayadaw · master-ajahn-chah |
> 此表仅供快速定位。判断该选谁时以 routing.json 与各 meta.json 为准。
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take xr843/master-help from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.