wiki-lint-fix
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
SOP wrapping vault_lint — run batch validation, report issues, optionally auto-fix safe problems.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- yogsoth-ai/wiki-vaultword for word, first seen May 18, 2026
Other versions1 project uses a version of this.
Word for word · 1
- yogsoth-ai/wiki-vault★ 4100% same
Edited · 0
None found.
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, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Run batch validation on the vault and optionally auto-fix safe issues.
- Distinctive: line 15
Always run in report mode first.
- Distinctive: line 16
Never auto-fix without first presenting the issue summary to the calling tactic.
- Very specific: line 31
Call vault_lint with fix: false (report mode)
- Very specific: line 36
If calling tactic approves fix: call vault_lint with fix: true
≈ “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 Lint Fix
Run batch validation on the vault and optionally auto-fix safe issues.
HARD-GATE
<HARD-GATE>
Always run in report mode first. Review the issue list before enabling fix mode.
Never auto-fix without first presenting the issue summary to the calling tactic.
</HARD-GATE>Tool
vault_lint
Parameters
| Param | Required | Description |
| fix | no | Auto-fix safe issues (default false) |
Protocol
- Call
vault_lintwithfix: false(report mode) - Categorize issues:
- Auto-fixable: duplicate edges, stale index entries
- Manual: broken wikilinks, orphan pages, missing frontmatter
- Report issue summary to calling tactic
- If calling tactic approves fix: call
vault_lintwithfix: true - Report what was fixed and what remains
Auto-Fix Scope
Safe to auto-fix:
- Duplicate edges → deduplicate (keep first occurrence)
- Stale index entries → remove from _index.json
Requires manual resolution:
- Broken wikilinks → need to determine correct target or remove link
- Orphan pages → need to find appropriate connections
- Missing frontmatter → need to determine correct values
Yield
Returns: { total_issues: number, errors: number, warnings: number, fixed: 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.