Menu
Maintain canonical concept pages and surface recurring themes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | vault-concepts |
| description | Maintain canonical concept pages and surface recurring themes |
Promote recurring themes into canonical concept pages and keep concept navigation coherent.
Portent reference: ../references/portent-knowledge-base-spec.md.
Work the active surface newest-first, ranked by each object's updated
frontmatter date (fall back to file modification time when updated is absent).
Concentrate scrutiny on the freshest material — recently-touched objects are
where active thinking lives and where new mismatches, overlaps, and gaps appear.
Long-untouched objects are assumed settled and rank lower, but are never
excluded: they remain valid link targets, merge destinations, and canonical
homes, and still get a structural check (broken links, orphaning).
Weight theme detection toward recent notes so emerging themes surface early, but keep temporal spread as the high-confidence signal: a concept still needs occurrences across time, not just a recent burst.
Maintain notes/concepts/ as the durable vocabulary of your vault. Surface
cross-domain patterns and decide when transience deserves permanence.
Concept pages are Portent Topic objects. New recurring-theme pages should use
type: Topic, status: organized, and explicit related_to links to the
Projects, Notes, Events, or Responsibilities they help explain.
--topic TOPIC focus on specific theme (optional)--mode report|apply (default: report)Only create new concept pages when ALL are true:
notes/, ideas/, projects/) for recurring
themesindex.md when concept navigation changesMerge concept pages when they name the same principle, mental model, or durable vocabulary item. Do not merge broad neighboring concepts just because they are often linked together.
Return:
Run a marketing/positioning pass on an open source repo's README and public-facing docs so a developer landing on it for the first time immediately understands what it is, why it exists, and how to use it. Use this whenever the user wants to improve a repo's README, write launch copy for an OSS project, sharpen positioning ("does this README explain what the project does"), prep a repo for a Show HN / Hacker News / Product Hunt / Twitter launch, or asks for an "OSS marketing pass," "README audit," or similar. This is about clarity and conversion (visitor → user → star), not contribution mechanics — for CONTRIBUTING.md, issue templates, CODEOWNERS, or governance docs, that's a different concern.
Audit and prepare a GitHub repo for open source release, with a focus on developer experience (DevEx) — the things that determine whether a stranger can go from "found this repo" to "opened a PR" without friction. Use this whenever the user wants to open-source a repo, make a private repo public, do a "pre-launch checklist" or "OSS readiness audit," improve their README/CONTRIBUTING/issue templates, or asks something like "is this repo ready for people to use/contribute to." Also trigger for narrower asks that are really pieces of this — "write a CONTRIBUTING.md," "set up issue templates," "add a CODEOWNERS file" — since those are almost always better done as part of the full readiness pass rather than in isolation.
Design, build, or review command-line interfaces using the Command Line Interface Guidelines from clig.dev. Use this skill whenever the user is creating a new CLI, adding commands/subcommands/flags, designing help text, choosing stdout/stderr/exit-code behavior, adding JSON or plain output modes, improving error messages, making destructive operations safer, or asking whether a CLI feels good, scriptable, discoverable, or Unix-friendly.
Collapse semantically overlapping notes, ideas, and project docs into clearer canonical surfaces while preserving distinct claims, decisions, examples, and source provenance.
Hygiene pass over active notes, ideas, and projects
Weekly bounded maintenance loop across ingestion, hygiene, compaction, lifecycle management, and concepts