improve: distinctive aislop triggers and Tessl conciseness

[heavykenny]

Why

Tessl quality review flagged two issues in the aislop skill:

1. Generic router phrases (review my changes, is this clean) overlap with general code-review skills.
2. False-positive verification, the "don't ask" policy, and anti-patterns restated the same guidance in three places.

What

• Switch description / When to invoke / skill.json triggers to distinctive phrases: any slop, remove slop, review my code, run aislop, aislop, score my code.
• Merge the false-positive checklist into workflow step 4a; drop the standalone section.
• Trim anti-patterns to items not already covered by the workflow.
• Add matching eval prompts.
• Bump skill.json 0.3.0 → 0.3.1 (patch).

Tessl

The skill is already in the Tessl registry from GitHub:
https://tessl.io/registry/skills/github/scanaislop/skills/aislop

Quality review after these edits: 93/100. Security review: pass, no findings. Tessl's auto-fix loop did not beat the baseline, so the conciseness edits were applied by hand.

The Tessl listing still shows the pre-change description until this merges and the registry reindexes.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.