project-skill-audit

You can audit project skills by analyzing past Codex sessions, memory files, and existing local skills to identify gaps. The process reads memory, reviews rollout summaries, and scans local skills to output candidate skill metadata for evaluation.

The best way to find high-value skills is to analyze recurring patterns from your project's memory and rollout summaries. This evidence-based approach prioritizes real workflows over generic brainstorming to propose targeted skill updates or new skills.

To check for stale or duplicate skills, compare your project-local skills against recurring work surfaces. This audit scans existing skill folders and current repo conventions to surface outdated definitions and recommend necessary updates.

Yes, you can analyze memory files and rollout summaries to guide skill investments. The audit maps recurring tasks from project history to prioritize creating or updating skills that deliver the highest impact for your specific workflows.

You should request a skills audit when you need ideas grounded in real project history rather than generic brainstorming. It applies when seeking to identify what skills a project needs by evaluating evidence from past sessions and local configurations.

No external dependencies are required to scan local project files. The audit workflow operates directly on your project's existing memory files, rollout summaries, and local skill folders to identify gaps and propose new skill metadata.