skill-map
Skill0 starsChanged 5 months agoApache-2.0View on GitHub
GEODoctor 工程技能总地图——不知道该读哪份文档、想总览本仓库有哪些规范时使用。若问题已能对号入座(调规则、发版、调试、文案等),直接用对应技能,勿经本图。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- buildwithdesi/skillstheir own version, first seen Nov 8, 2026
- tdfydfy/skill-maptheir own version, first seen Jul 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- buildwithdesi/skills★ 4same name
- tdfydfy/skill-map★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- acceptance-gatesSkill
- architecture-contractsSkill
- bilingual-docs-contractSkill
- debug-audit-pipelineSkill
- debug-site-quirksSkill
- debug-test-failuresSkill
- diagnostic-commandsSkill
- evidence-registry-contractSkill
- failure-archaeologySkill
- release-versioning-controlSkill
- rule-change-controlSkill
- security-boundariesSkill
- showcase-refresh-protocolSkill
The file
Files
文档地图(先读我)
除本地图外的全部工程技能文档按症状路由如下。本文档自身不含任何操作知识——只负责把你送到对的地方。
症状 → 文档
| 你现在的处境 | 去读 |
| 想改某条规则的阈值/权重/文案,或加删规则 | rule-change-control |
| 要发版、发 npm、改版本号 | release-versioning-control |
| 要改任何用户可见的中英文案 | bilingual-docs-contract |
| audit 输出不对,不知道断在哪一层 | debug-audit-pipeline |
| 某个真实网站的审计结果很怪(403/空壳/乱码/超时) | debug-site-quirks |
| 测试挂了,看不懂为什么 | debug-test-failures |
| 想知道这仓库以前踩过什么坑(或要归档新事故) | failure-archaeology |
| 想动核心数据流/接口/退出码/评分公式 | architecture-contracts |
| 要添加/修改/质疑一条证据引用 | evidence-registry-contract |
| 代码要处理来自被审计站点的数据 / 新增 fetch 路径 / 改报告渲染 | security-boundaries |
| 需要一条现成的诊断命令(单规则跑分、抽帧、查 CI) | diagnostic-commands |
| 不确定手头的改动"做到什么程度才算完" | acceptance-gates |
| 要更新 docs/showcase.md 榜单 | showcase-refresh-protocol |
新人建议阅读顺序
- failure-archaeology —— 5 分钟了解这仓库怎么疼过
- architecture-contracts —— 不变量清单
- 其余按需查阅,不必通读
什么时候不该用这份文档
- 想了解项目是什么、怎么安装 → 根目录
README.md - 想了解评分原理和论文依据 →
docs/methodology.md - 想贡献规则的流程性要求 →
CONTRIBUTING.md - 找社区发布文案 →
LAUNCH.local.md(已 gitignore,只在本机存在)
姊妹文档
其余全部技能都是本文档的姊妹。若一个问题同时命中多份,优先级:contracts 类 > control 类 > debug 类(先确认不变量,再走流程,最后调试);不在三类里的四份定位固定——failure-archaeology 是历史馆(事前读)、diagnostic-commands 是工具箱(随取随用)、acceptance-gates 是收尾门禁(合入前)、showcase-refresh-protocol 是打分变更的连带义务(改完必查)。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

