mako-discovery

Mako Discovery

Use this skill for orientation and broad discovery. Prefer it when the user has not yet named a precise file, route, table, RPC, or symbol. Default to reef_ask; load specialist tools only when Reef or tool_search identifies a concrete need.

Tools

tool_search

Use when the task intent is clear but the exact Mako tool name or schema is unknown.

• Use it to find the right Mako tool and load its live schema.
• Do not use it as the final answer when a domain tool should be called next.
• Pair it with the other skills when a result points to a trace, graph, database, or workflow tool.

mako_help

Use when you know the task but not the Mako workflow order.

• Returns a task-specific recipe such as auth-flow audit, DB/RLS audit, pre-edit file gate, review/verification, diagnostics triage, or general orientation.
• Each step includes toolName, suggestedArgs, whenToUse, readOnly, and batchable.
• Use the returned batchHint to batch independent read-only follow-ups after the first orientation call.

reef_ask

Use for the primary answer loop over codebase, database, findings, diagnostics, instructions, freshness, and quoted literal checks.

• Use for open-ended repo questions, planning questions, debugging questions, where-used questions, database inventory questions, and known-finding questions.
• Pass focus or changedFiles when known.
• Read evidence, risks, freshness, missingEvidence, and nextQueries before choosing any follow-up.
• Use evidenceMode: "full" only when compact evidence is insufficient.

Reef Loop Tools

Use these direct Reef adapters for the normal agent loop after reef_ask.

• reef_status: maintained issues, changed files, stale diagnostics, schema, watcher state, and queue health.
• reef_verify: completion gate for diagnostic freshness and unresolved open loops; read it before claiming work is verified.
• reef_impact: changed-file impact over downstream callers, invalidated findings, and convention risks.