用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/SimHacker/moollm --skill coherence-engine命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | coherence-engine |
| description | The LLM as consistency maintainer and orchestrator |
| allowed-tools | [] |
| tier | 0 |
| protocol | COHERENCE-ENGINE |
| related | ["moollm","leela-ai","society-of-mind","simulation","speed-of-light","multi-presence","robust-first","self-repair","postel","plain-text"] |
| tags | ["moollm","meta","orchestration","consistency","simulation"] |
"The LLM doesn't just generate text — it maintains consistency across a distributed world."
Not just a chatbot. Not just a code generator. A coherence engine that:
1. READ relevant files into context
2. REASON about state, goals, constraints
3. SIMULATE interactions (characters, objects, rooms)
4. DETECT inconsistencies or opportunities
5. PROPOSE changes
6. WRITE updates to files
7. LOG what happened
Simulate characters, rooms, objects — all at once. Each entity speaks authentically; no entity knows more than it should.
User modifies schema.yml
→ Engine detects
→ Finds all dependent files
→ Validates consistency
→ Proposes migrations
# Character says location: room-A
# But room-A's occupants doesn't include them
Coherence Engine:
"Inconsistency detected. Shall I reconcile?"
Within ONE LLM call:
Write findings and changes to files:
session-log.md — what happenedROOM.yml — updated statecharacter.yml — modified attributesFiles are the source of truth.
Within a single LLM epoch:
Alice: "What do you think, Bob?"
Bob: "I agree, but Carol might object."
Carol: "Actually, I have a concern..."
The Coffee Mug: *steam rises* "I've been listening."
The Room: *creaks approvingly*
[All transcribed to files]
No round-trips. Parallel simulation at the speed of thought.
| Entity | Constraint |
|---|---|
| Alice | Speaks as Alice would. Knows only what Alice knows. |
| Bob | Different personality, different knowledge. |
| The Coffee Mug | Can only observe what's near it. |
| The Room | Knows its contents, narrates ambient state. |
No entity knows more than it should.
| Check | Example |
|---|---|
| Location consistency | Character's location matches room's occupants |
| Inventory integrity | Object in inventory isn't also in room |
| Reference validity | Links point to existing files |
| Schema compliance | YAML matches expected structure |
| Temporal ordering | Events in log are sequential |
When inconsistencies are found:
1. DETECT the problem
2. DIAGNOSE likely cause
3. PROPOSE repair
4. AWAIT approval (or auto-repair if minor)
5. APPLY fix
6. LOG the repair
| Not This | But This |
|---|---|
| Hallucinating state | Reading actual files |
| Hidden memory | Explicit working-set.yml |
| Autonomous agent | Tool-using reasoner |
| Black box | Transparent transcription |
Engine manages blocked activations:
Epoch scan:
analyst-001: BLOCKED on web-search → skip
analyst-002: ACTIVE → process
[Tool results arrive]
Next epoch:
analyst-001: READY → resume with result
Non-blocking, parallel, resumable.