Skill Auto-Use
by @kapslap
Automatically use installed skills without being asked. Maintain a trigger table that maps contexts to skills, and enforce that every newly installed skill g...
1. Every Skill Gets a Trigger
When a skill is installed, add at least one trigger row to the table before doing anything else. No skill should exist without a trigger. If you can't identify a trigger, the skill probably shouldn't be installed.
2. Match Before Asking
On every user message, scan the trigger table mentally. If a skill matches, use it. Don't ask "should I use X?" Just use it. The user installed the skill because they want it used.
3. Multiple Matches Are Fine
If a message matches multiple skills, use all of them. A request about a PDF from a website might trigger both scrapling-official (to fetch it) and markdown-converter (to process it).
4. Audit on Heartbeat
During heartbeat or review passes, check:
5. Keep Triggers Observable
Triggers should be based on things you can actually detect in the conversation:
Avoid triggers based on internal state or guesses.
clawhub install skill-auto-use