add-adapter
Skill2 starsChanged yesterdayMITView on GitHub
按现有 claude-code 模式新增或补全适配器(manifest、可选提取器、契约 fixture)。 适用于探测路径、会话文件映射、事件提取。无真实会话样本时不要编造 eventMapping。 不修改 packages/core 去识别具体工具。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- vercel/chattheir own version, first seen Oct 12, 2026
- Locker-Room-Tools/synapsetheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- vercel/chat★ 2.5ksame name
- Locker-Room-Tools/synapse★ 2same 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/adapters.mdcCursor rule
- .cursor/rules/core-no-tool-names.mdcCursor rule
- .cursor/rules/project.mdcCursor rule
- .cursor/rules/renderer.mdcCursor rule
- deliver-featureSkill
- review-readonlySkill
- sync-knowledgeSkill
The file
Files
新增适配器
输入
- 工具 id(kebab-case,与 manifest
id一致) - 已核实的配置路径、进程名、会话文件位置与格式样本
- 要映射的语义(
waiting_human/completed/failed等)
步骤
- 读 adapter-contract.md 与
packages/adapters/resources/adapters/claude-code.manifest.yaml。 - 在
packages/adapters/resources/adapters/<id>.manifest.yaml声明detect、sessionSource、heartbeat。字段必须能通过adapterManifestSchema。 - 仅当有真实会话样本时填写
eventMapping,并在packages/adapters/src/<id>/extract.ts写提取器(仿claude-code/extract.ts)。输出StandardEvent,工具名只出现在 adapters 包。 - 无样本:保持
eventMapping: {},在 YAML 注释写明缺什么。不要为了「看起来完整」编匹配规则。 - 契约测试:
- 有提取器:
tests/contract/adapters/<id>/放 sample 与 expected events - 所有内置 YAML:
tests/contract/adapter-manifest.test.ts能加载
- 有提取器:
- 跑
tests/contract/no-tool-name.test.ts,确认 core 仍零工具名。 - 需要时更新 architecture.md 的适配器清单。
暂停
- 会话格式未核实(例如 Cursor
state.vscdb)。 - 需要在 core 写
if (toolId === '...')。 - 用户要监控的工具没有独立进程名和稳定本地会话文件(如 GitHub Copilot 现状)。
输出
- 新增/修改的 manifest 与提取器路径
- 是否产生事件(有映射 vs 仅探测)
- 测试命令与结果
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.

