Cp skill validate
The theory of LLM wikis, running as one. A framework for agent-operated knowledge: typed, linked, review-gated markdown your agents execute.
npx -y skills add zby/commonplace --skill cp-skill-validateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Run deterministic validation on KB artifacts, collections, and the published redirect map, including schemas, links, required sections, and batch signals.
SKILL.md
1.7 KB, as published. Nobody here has run it
EXECUTE NOW
Run the packaged validation command. For all, invoke each top-level collection separately because the CLI deliberately rejects a repository-wide literal scope:
if [ "$ARGUMENTS" = "all" ]; then
for contract in kb/*/COLLECTION.md; do
commonplace-validate "$(basename "$(dirname "$contract")")" || exit $?
done
if [ -f properdocs.yml ]; then
commonplace-validate redirects || exit $?
fi
else
commonplace-validate "$ARGUMENTS"
fi
Target: $ARGUMENTS
Prefer the narrowest target that covers the user's request. For write/edit workflows, validate the new or edited file paths explicitly; do not validate the whole KB unless the user asked for a full maintenance check.
- Note path or name: validate that specific note
- Multiple note paths: validate those specific notes, one command per path if needed
- Directory path or collection name: validate
.mdfiles under that directory, only when the edited set is directory-scoped - "all": validate each top-level collection in a separate command
- "redirects": validate the live
properdocs.ymlredirect map against its published tree - "notes": validate all
.mdfiles inkb/notes/ - "recent" or "today": validate notes modified today
- Empty: ask which note to validate
Report the script output directly. Do not interpret, supplement, or override its findings.
For judgment-based frontmatter checks, run kb/instructions/run-review-batches.md with the frontmatter bundle.