skill-audit
Skill Audit
Overview
Audit installed Codex surfaces before proposing new ones.
Treat the installed surface portfolio as the primary subject by default. Supported target kinds are:
- standalone skill
- plugin package
- bundled plugin skill
Prefer updating, merging, or disabling existing surfaces before recommending new ones. Treat project-local specializations as a last resort.
Default full-scope audits should stay workflow-first and mixed. Start from the current workflow, repo docs, named tasks, and relevant local surfaces, then widen only when the workflow or named target requires it.
More from alemar11/skills
postgres
Connect to Postgres databases, run SQL and diagnostics, inspect schemas and migrations, review query performance, and use common PostGIS or pgvector patterns.
47codex-changelog
Check the installed Codex CLI and Codex App versions, then print separate changelog sections for the CLI from GitHub Releases and the app from the OpenAI Codex changelog page.
28learn
Capture durable corrections or preferences and write confirmed learnings only to AGENTS.md. Use when the user sets lasting guidance.
27ask-questions-if-underspecified
Clarify requirements before implementing when a request is underspecified or the user asks for clarification.
24github
Handle repo-scoped GitHub work plus authenticated-user star and star-list workflows through one repo-owned skill covering triage, reviews, CI, releases, and PR publish or lifecycle flows, with `yeet` reserved for full local-worktree publish.
12commit
Create a well-formed git commit from current changes using session history for rationale and summary; prefer explicit pathspec staging and, in monorepos, default to one subproject per commit unless the user asks for a cross-cutting commit. Use when asked to commit, prepare a commit message, or finalize staged work.
7