Audit installed skills and MCP servers

Run one script, read its report, and explain it. This skill changes nothing. It does not delete, disable, or edit any skill or setting. The person decides what to do with each suggestion.

Checklist

Copy this list and tick it in order.

• 1. Run the script from the project the person is working in. If $ARGUMENTS holds a number, pass it as --top.

python3 "${CLAUDE_SKILL_DIR}/scripts/audit.py" --top 10

• 2. Read the whole report. It lists user, project and plugin skills and the configured MCP servers, with size estimates in tokens (four characters per token, so treat them as rough).
• 3. Tell the person the total always-on cost first: every skill's name and description sits in context in every session, and each skill's body loads only when it triggers.
• 4. Walk the ranked list. For each row give the action and the one reason, in plain sentences.
• 5. Say what the script cannot measure: the size of an MCP server's tool descriptions. Point the person to /context for that.
• 6. Offer next steps and wait. Do not run them unasked.