Project Skill Audit

Overview

A skill earns its place when it captures a procedure that people in this repository perform again and again, that takes several steps, and that goes wrong without project-specific knowledge. An audit therefore starts from evidence of what actually happens in the project, not from a list of skills that sound useful. This skill tells an agent where each coding agent keeps its skills, instructions, transcripts and memory, how to turn that material into counted observations, how to judge each candidate, and what the final report looks like.

Instructions

1. Agree the scope

Ask the user:

• Which agents the team uses. That decides which folders and histories matter.
• Whether session transcripts on this machine may be read. They are plaintext records of everything that passed through tools, including file contents and command output, so get a yes first and never copy secrets from them into the report.
• The time window (30 or 90 days is typical) and whether personal skills under the home directory are in scope or only the repository's.

2. Inventory what exists