agent-plugins

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

Hygiene pass over active notes, ideas, and projects

Weekly bounded maintenance loop across ingestion, hygiene, compaction, lifecycle management, and concepts

Manage PORT object lifecycle through Portent metadata, folder state, and index navigation

{url} address comments left on a GitHub pull request. Use when a user wants review comments and CI failures fixed on an existing GitHub pull request without opening a new PR.

Use when raw vault captures need classification, routing, relocation, and external-source synthesis from the source inbox into the right vault surfaces

Use when a vault note, idea, project, or topic needs external sources, competitor research, discussion evidence, or market signals

Audit, rewrite, and tighten a CLAUDE.md / AGENTS.md file so it actually helps a coding agent instead of bloating its context. Handles repos that use either file name, both names, nested AGENTS.md files, or one file symlinked/aliased to the other. Use this skill whenever the user wants to review, clean up, fix, shrink, restructure, or improve a CLAUDE.md / AGENTS.md file

Use when X bookmarks need to be captured into raw/sources or existing X bookmark source records need relevance triage