wiki-add-edge
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
SOP wrapping vault_add_edge — create a typed relationship between two vault pages.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- yogsoth-ai/wiki-vaultedited, first seen May 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- yogsoth-ai/wiki-vault★ 498% same
Wrote their own version · 0
None found.
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 repository70 other files it gives its agents.
- alias-resolutionSkill
- argument-mappingSkill
- argument-synthesisSkill
- argument-visualizationSkill
- axis-extractionSkill
- axis-validationSkill
- causal-chain-querySkill
- causal-modelingSkill
- claim-decompositionSkill
- claim-extractionSkill
- claim-page-creationSkill
- combination-enumerationSkill
- combination-mappingSkill
- concept-decompositionSkill
- concept-extractionSkill
- concept-page-creationSkill
- confidence-scoringSkill
- confidence-updateSkill
- consistency-checkingSkill
- contradiction-flaggingSkill
- counterfactual-reasoningSkill
- dimensional-analysisSkill
- dimension-discoverySkill
- dimension-page-creationSkill
- domain-scopingSkill
- edge-batch-creationSkill
- evidence-attachmentSkill
- evidence-collectionSkill
- evidence-linking-argSkill
- evidence-linkingSkill
- evidence-weighingSkill
- feedback-loop-detectionSkill
- gap-detectionSkill
- gap-prioritizationSkill
- hierarchy-constructionSkill
- hierarchy-visualizationSkill
- intervention-analysisSkill
- intervention-page-creationSkill
- knowledge-compilationSkill
- loop-documentationSkill
- matrix-exportSkill
- matrix-generationSkill
- mechanism-edge-creationSkill
- mechanism-mappingSkill
- merge-candidatesSkill
- model-gap-detectionSkill
- model-validationSkill
- novelty-scoringSkill
- ontology-buildingSkill
- ontology-exportSkill
- ontology-refinementSkill
- question-generationSkill
- rebuttal-documentationSkill
- relation-typingSkill
- seed-concept-searchSkill
- source-gatheringSkill
- strength-assessmentSkill
- strength-scoringSkill
- synthesis-reportSkill
- taxonomy-validationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Create a typed edge between two pages in the knowledge graph.
- Distinctive: line 17
Do NOT create edges to non-existent pages.
- Distinctive: line 35
Verify both source and target files exist
- Distinctive: line 38
If duplicate rejected, this is expected — the relationship already exists
- Very specific: line 39
Inline wikilink: Ensure the source page body contains [[dir/slug]] pointing to the target (dir/slug = target path minus .md).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wiki Add Edge
Create a typed edge between two pages in the knowledge graph.
HARD-GATE
<HARD-GATE>
Both source and target paths must reference existing files in the vault.
Edge type must be one of the 10 defined types in _schema.md.
Do NOT create edges to non-existent pages.
</HARD-GATE>Tool
vault_add_edge
Parameters
| Param | Required | Description |
| source | yes | Source page path (e.g., "concepts/transformer.md") |
| target | yes | Target page path (e.g., "concepts/attention.md") |
| edge_type | yes | One of: component_of, instance_of, supported_by, contradicts, supersedes, derived_from, addresses, raises, failed_for, related_to |
| weight | no | Edge weight 0.0-1.0 (default 1.0) |
Protocol
- Verify both source and target files exist
- Select appropriate edge_type based on the semantic relationship
- Call
vault_add_edge - If duplicate rejected, this is expected — the relationship already exists
- Inline wikilink: Ensure the source page body contains
[[dir/slug]]pointing to the target (dir/slug = target path minus.md). Place at a semantically relevant location. If already present, skip. If no suitable location, append a sentence containing the wikilink at end of body. - Return result to calling tactic
Edge Type Selection Guide
| Relationship | Edge Type |
| A is part of B | component_of |
| A is an example of B | instance_of |
| A provides evidence for B | supported_by |
| A conflicts with B | contradicts |
| A replaces B | supersedes |
| A was built from B | derived_from |
| A answers/solves B | addresses |
| A creates/implies B (question) | raises |
| A didn't work for B | failed_for |
| A is related to B (weak) | related_to |
Yield
Returns: { success: boolean, edge_type: string, edge_count: number }
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.