Skills
A useful skill is not a giant all-purpose brain. It captures a high-frequency action with a stable decision path so that you and your team can reuse it.
Project start checks: doctor, channel probe, search provider, pairing status.
Daily ops checks: latest failed tasks, plugin health, permission errors, queued work.
Pre-plugin-launch checks: version, Gateway restart, minimum regression validation.
Chat or ticket triage: repair context first, then decide whether to use tools, a skill, or human escalation.
Keep the core workflow in `SKILL.md` and move long details into `references/`.
Put deterministic logic in `scripts/` instead of natural-language instructions.
One skill should solve one stable scenario. Do not start with a universal controller.
Prepare 2 to 3 real trigger phrases and see whether the skill is invoked consistently.
Require a stable output shape such as a checklist, issue summary, or next-step plan.
If outputs vary wildly, the skill is still too broad and should be narrowed.
Starter Template
The project already includes a reusable `SKILL.md` starter and a bootstrap checklist. Start with a simple project bootstrap skill before you optimize further.