wiki-synthesize
Skill4 starsChanged 4 months agoApache-2.0View on GitHub
Scan the full Living Entity Wiki for recurring patterns across Rejected Approaches and Open Questions that no single entity states alone. Produces higher-inference hypotheses for human review and never mutates authoritative or wiki state.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- chobizzy/llm-wikitheir own version, first seen Nov 1, 2026
- Ivy-Chen1999/llm-wiki-kittheir own version, first seen Jun 23, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Ar9av/obsidian-wiki★ 3.7ksame name
- Ivy-Chen1999/llm-wiki-kit★ 21same name
- chobizzy/llm-wiki★ 3same 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 repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-remediationSkill
- attentionSkill
- classify-docSkill
- codebase-designSkill
- codebase-memory-mcpSkill
- codegraphSkill
- coding-standardsSkill
- contract-ledgerSkill
- conventional-commitsSkill
- database-migrationsSkill
- deduplicate-codeSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- format-codeSkill
- github-issue-dependenciesSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implement-ticketSkill
- improve-codebase-architectureSkill
- project-delivery-managementSkill
- project-trackingSkill
- prototypeSkill
- repowiseSkill
- researchSkill
- resolving-merge-conflictsSkill
- review-architectureSkill
- review-specSkill
- setup-matt-pocock-skillsSkill
- spec-contractSkill
- spec-merge-cleanupSkill
- tddSkill
- teachSkill
- to-adr-docSkill
- to-docSkill
- to-specsSkill
- to-ticketsSkill
- triageSkill
- verify-architectureSkill
- verify-codeSkill
- verify-spec-closureSkill
- verify-specSkill
- verify-ticket-closureSkill
- verify-ticket-decompositionSkill
- wayfinderSkill
- wiki-lintSkill
- wiki-syncSkill
- writing-great-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 0 are common, 20 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
20
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Do not invoke it automatically from the $wiki-sync skill or the$wiki-lint skill, routine implementation, document creation, or ADR …
- Distinctive: line 32
Run it when enough durable wiki knowledge has accumulated that cross-entity synthesis may reveal something useful.
- Distinctive: line 34
Do not run it after every session.
- Distinctive: line 52
Use Strict Invariants as contextual evidence where relevant.
- Distinctive: line 54
Use Planned and Boundary Rationale only when they materially clarify the pattern.
- Distinctive: line 56
Do not treat Routing Anchors, Categories, or implementation structure as synthesis evidence by themselves.
- Distinctive: line 62
Prefer cross-entity evidence, but repeated causal evidence within one entity may be reported as an entity-local recurrence.
- Distinctive: line 64
Do not report patterns based only on:
- Distinctive: line 75
Look for Rejected Approaches that appear to fail for the same underlying architectural reason.
- Distinctive: line 85
Do not mark an Open Question resolved merely because another entity provides relevant evidence.
- Distinctive: line 89
If accumulated rejections/questions suggest that an assumption behind a Strict Invariant deserves review, frame it cautiously.
- Distinctive: line 103
Every pattern must identify its supporting entries with:
- Distinctive: line 110
Do not strengthen provenance during synthesis.
- Very specific: line 120
If a supporting entry has an obvious health problem such as a broken citation or unresolved [source-conflict], note the limitation.
- Very specific: line 154
consider the $to-adr-doc skill if a real architectural decision is needed.
- Distinctive: line 155
consider a topology review if several entities may represent one boundary.
- Distinctive: line 157
Do not perform the action automatically.
- Distinctive: line 183
Add a Caveat when evidence quality or source health materially limits the conclusion.
- Distinctive: line 185
If no meaningful pattern exists, report:
- Distinctive: line 191
Do not lower the evidence threshold merely to produce output.
- Distinctive: line 208
If the owner confirms a finding, use the appropriate normal lifecycle afterward:
- Distinctive: line 216
Do not log the synthesis run itself.
- Distinctive: line 227
create documents or ADRs;
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wiki Synthesize
$wiki-synthesize performs deliberate, higher-inference analysis across the full Living Entity Wiki.
It looks for:
- recurring causes behind Rejected Approaches;
- related Open Questions across entities;
- repeated constraints that may indicate a broader architectural concern;
- accumulated evidence that an assumption deserves review.
Its output is a signal for human judgment, never architectural authority.
Invocation
$wiki-synthesize is manual-only.
Retain:
disable-model-invocation: truefor Claude Code;- the existing
agents/openai.yamlmanual invocation configuration for Codex.
Do not invoke it automatically from the $wiki-sync skill or the$wiki-lint skill, routine implementation, document creation, or ADR lifecycle.
Run it when enough durable wiki knowledge has accumulated that cross-entity synthesis may reveal something useful.
Do not run it after every session.
1. Load the Active Wiki
Read:
wiki/index.md
wiki/entities/*Load every active entity page.
Primary synthesis inputs are:
- Rejected Approaches;
- Open Questions.
Use Strict Invariants as contextual evidence where relevant.
Use Planned and Boundary Rationale only when they materially clarify the pattern.
Do not treat Routing Anchors, Categories, or implementation structure as synthesis evidence by themselves.
2. Find Meaningful Patterns
A pattern requires at least two distinct supporting entries.
Prefer cross-entity evidence, but repeated causal evidence within one entity may be reported as an entity-local recurrence.
Do not report patterns based only on:
- similar wording;
- shared technologies;
- two unrelated failures;
- an abstraction the agent can merely imagine.
The causal reasoning must meaningfully overlap.
Recurring Rejections
Look for Rejected Approaches that appear to fail for the same underlying architectural reason.
Open-Question Relationships
Look for:
- reinforcement — multiple entries independently raise the same concern;
- partial answer — another entity contains relevant evidence;
- tension — an unresolved question challenges an assumption elsewhere.
Do not mark an Open Question resolved merely because another entity provides relevant evidence.
Invariant Tension
If accumulated rejections/questions suggest that an assumption behind a Strict Invariant deserves review, frame it cautiously.
Valid:
Several entries suggest that the assumption behind invariant X may deserve review.
Invalid:
Invariant X is obsolete.
Direct contradictions belong to the $wiki-lint skill, not synthesis.
3. Preserve Provenance
Every pattern must identify its supporting entries with:
- Entity ID/name;
- section;
- concise entry;
- existing provenance.
Do not strengthen provenance during synthesis.
For example:
source: agent-observed during session, unresolvedmust never become an owner decision merely because the pattern looks persuasive.
If a supporting entry has an obvious health problem such as a broken citation or unresolved [source-conflict], note the limitation.
Recommend the $wiki-lint skill when systematic source-health evaluation is required rather than duplicating lint behavior here.
4. Assign Confidence
Use:
Confidence: low | medium | highConfidence means strength of synthesis evidence, not architectural authority.
- Low — plausible but indirect or assumption-heavy.
- Medium — multiple entries share a clear causal theme.
- High — several independent entries strongly reinforce the same pattern with little interpretive stretching.
Even high means:
high confidence that the pattern deserves review.
It does not mean a decision has been established.
5. Suggest the Smallest Next Step
For each pattern, recommend only the smallest useful follow-up.
Examples:
- review an Open Question;
- reconsider a condition-dependent rejection;
- inspect a Strict Invariant;
- invoke the
$wiki-lintskill if a direct conflict may exist; - consider the
$to-adr-docskill if a real architectural decision is needed; - consider a topology review if several entities may represent one boundary.
Do not perform the action automatically.
Report Format
Use:
## Synthesis Report — YYYY-MM-DD
### Pattern: [concise description]
**Confidence:** low | medium | high
**Interpretation:**
[Why the entries may share an underlying cause or concern.]
**Supporting entries:**
- [entity] › [section]: [concise entry]
(source: ...)
- [entity] › [section]: [concise entry]
(source: ...)
**Suggested next step:**
[Smallest appropriate human-reviewed follow-up.]Add a Caveat when evidence quality or source health materially limits the conclusion.
If no meaningful pattern exists, report:
Synthesis: no meaningful recurring patterns found.Do not lower the evidence threshold merely to produce output.
Report-Only Rule
$wiki-synthesize never writes to:
wiki/entities/;wiki/index.md;wiki/log.md;docs/;- ADRs;
- source code.
It never creates a commit.
The synthesis report itself is not an authoritative source.
If the owner confirms a finding, use the appropriate normal lifecycle afterward:
- architectural decision →
$to-adr-doc; - entity/wiki change →
$wiki-sync; - direct conflict →
$wiki-lint/ source resolution; - new non-ADR document →
$to-doc; - existing document reclassification →
$classify-doc.
Do not log the synthesis run itself.
Out of Scope
$wiki-synthesize does not:
- perform ordinary drift or citation auditing;
- resolve
[source-conflict]; - maintain entity pages;
- decide topology;
- establish architectural authority;
- create documents or ADRs;
- convert inference directly into durable wiki knowledge.
Its job is to ask:
What meaningful pattern may be emerging across the knowledge already accumulated?
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.

