Guidance for a display-only skill-suggestion capability: how a caller should suggest a skill to the operator, how the emitted answer is read, and what must never happen (selection, auto-loading, judgment). The capability gate ships off; this skill carries mechanism and contract ONLY — never the call path; where and how to reach the capability is the catalogue's concern.
64%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/moai-jev-skill-suggestion/SKILL.mdThe capability is gated behind workflow.jev.enabled, and the shipped
default is off. Confirm the gate before anything else. With the gate off, a
caller constructs no request, makes no network call, and proceeds with no
signal: an absent signal is NO SIGNAL — the same as "we did not ask" — never
a negative answer, and never a reason to change course.
Three readiness surfaces exist for the on state: the gate key itself, the
credentials file referenced by convention (~/.moai/.env.typesafe, read by
the credential loader — never inlined, never copied into settings), and the
doctor readiness check (a TCP-only probe that reports gate, credential, and
reachability in three lines without sending any judgment request). A caller
that cannot confirm all three proceeds as if the gate were off.
The reachable surface itself lives in the product catalogue, not here. This skill owns mechanism and contract only; the catalogue owns where the call lives.
A suggestion is a signal a person reads: a labelled model answer that names a skill that might be worth loading and carries a confidence, and it does nothing else. Four things it is not:
Two mechanisms were evaluated and rejected; recording them keeps them from returning quietly:
Every item below is guidance conditioned on a caller existing — it ships no behavior:
The suggestion call is a judgment over a typed question, and typed questions carry their own rules — compute the question in code, always admit a no-match answer, keep the supplied state small, phrase both polarities. Those rules live in the question-design reference skill; this skill does not restate them. The measurement regime above the surface is likewise owned elsewhere: this skill records the contract, never baseline numbers.
This skill is not a capability. It ships no caller, registers no command, adds no hook, and changes no setting. It is not a verdict: suggestion answers never close cards, approve merges, or mutate queues. And it is not an availability promise: the gate ships off, and nothing in this skill makes a suggestion surface exist — the checklist above governs only if a caller is ever built elsewhere, and until then an absent suggestion is just NO SIGNAL.
modu-ai/moai-adk
1176c97
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.