ontology-field-trial
FeaturedMeasure Atlas ontology quality on an unfamiliar repository with a source-hidden handoff and four baseline measurements. Use for changes to meaning-construction rules or MCP read/write behavior that can change vault contents, or an explicit ontology-quality field trial. Skip UI work and wording-only clarifications that preserve the evidence, approval, and write contracts.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- wlsdks
- Repository
- wlsdks/ontology-atlas
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
ontology-bootstrap
Build a trustworthy first ontology from an empty or near-empty ontology-atlas vault using only Atlas MCP evidence. Use when the user asks to analyze a codebase, bootstrap/fill its ontology, extract product meaning from a repository, or when a requested ontology task finds only starter nodes. Separate observed implementation facts from proposed meanings, define and cite every domain/capability, answer competency questions, obtain independent source-hidden qualification and user approval, then write only the exact released plan with batch tools. Route mature vaults with 20+ curated nodes to ontology-sync instead; this is a workflow threshold, never a vault or project node limit.
trial-run
Plan a scored ERC-26 trial run (procedure, pass criteria, pre-run checklist) or log a completed one with the real point breakdown. Use before running a scored trial, or right after one.
vaultwatch
Set up and operate an AUDITED knowledge vault: a plain-markdown second brain whose claims are verified by two instruments — a no-network coherence audit (the vault against itself) and a world audit (the vault against the running reality it describes: HTTP endpoints, served files, git remotes, on-chain state). Use this whenever the user wants a knowledge base, second brain, vault, wiki, HANDOFF, project memory, or documentation system for a repo that OPERATES something — servers, deployments, published content, prices, wallets, APIs — and also whenever they complain that docs drift, lie, go stale, or that "the README is always wrong". Covers bootstrapping a new vault, retrofitting auditors onto an existing docs/ folder, and the session-close ritual (fix what the session made false, re-run the audits, commit). If the knowledge is pure reading notes with no world that can contradict them, a plain wiki is enough and this skill is overkill.