Sounding

Take a depth reading before choosing a course. Read where the project stands, then return a short plan of which skills are worth running now, which come later, and why the rest can wait.

This skill advises only. Do not run the recommended skills, edit files, file tickets, commit or push. Read-only commands are fine. Keep the survey quick: it's a sounding, not an audit.

Candidates

Consider every installed skill. Read their names and descriptions at run time; never work from a fixed list. Project-wide passes such as audits, reviews, benchmarking and ideation are the usual picks, but a planning, cleanup, docs or design skill can be the right answer.

When several skills overlap, pick the one whose description best fits the evidence, and say in one line why it beats the others.