Skill Audit

Audit the requested package against its actual repository and validation surface. Evidence beats stylistic preference.

Choose the Mode

• Routine: structure, activation, pruning, or light edits. Run free plugin lint plus the manual scorecard; do not spend cloud credits.
• Formal: explicit publish readiness, Tessl score, or a substantive discovery/workflow rewrite that must reach 100. Run one narrow cloud review only when the repository-owned launcher, authentication, and credits exist.
• Experiential: a recent task exposed wrong activation, missing guidance, excessive ceremony, or a fragile workflow. Reconstruct that failure and make the smallest change that would alter behavior.

Read Tessl policy for exact formal commands, credit boundaries, fallbacks, and optimizer approval.