Menu
Hygiene pass over active notes, ideas, and projects
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
Maintain canonical concept pages and surface recurring themes
Weekly bounded maintenance loop across ingestion, hygiene, compaction, lifecycle management, and concepts
| name | vault-lint |
| description | Hygiene pass over active notes, ideas, and projects |
Run a focused hygiene pass over active vault surface and propose fixes.
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).
For this pass, order the issue list newest-first: a fresh file's issue outranks an older file's equivalent issue when reporting and when choosing what to apply.
--scope notes|projects|all (default: all)--mode report|apply (default: report)updated date threshold + topic inactivityexternal, or owned
notes incorrectly tagged externaltitle, invalid type, invalid
status, malformed belongs_to, malformed related_tostatus: organized objects without any
relationship when a Project, Responsibility, Operation, or Topic target is
obviousstatus: archived objects still shown in active
index.md viewsvault-tracker for lifecycle changes)report mode: list issues and proposed fixes only.apply mode: fix link issues, flag decisions needing manual review.apply mode: add high-confidence contextual links and backlinks.fleeting/, incubating/, someday/, rejected/raw/processed/YYYY-MM-DD/.externalexternalAdd links to build the knowledge graph when the relationship is concrete and useful for future navigation.
Apply-mode link additions must be contextual: add the wikilink near the relevant
claim, heading, source, or Related section. If no natural location exists,
report the candidate instead of forcing a link.
Prefer linking over merging when notes are related but distinct. Prefer concept links over many point-to-point links when a concept page is the better hub.
High-confidence candidates may be passed to vault-ingest, vault-tracker, or
vault-concepts for apply-mode merging. Medium/low candidates should stay as
separate notes with proposed links.
In apply mode, Portent fixes are limited to mechanical corrections:
title from H1 when exactstatus: organized only when type and relationships are already clearrelated_to links where the object explicitly names the
targetDo not infer broad relationships or change object type in apply mode unless the user explicitly requested that conversion.
Return: