Receber por email
← Voltar para o catálogo

agentmako

TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.

47estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add drhalto/agentmako

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/agentmako-mrc11kqb/svg)](https://www.skillteca.com.br/skills/agentmako-mrc11kqb)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Mako Neighborhoods

Use this skill when the user needs the surrounding context for one known table, route, or RPC. Neighborhood tools are bounded composed bundles; they are usually better than manually chaining primitives for common entity-centered questions.

Tools

table_neighborhood

Use for table-centered questions.

  • Includes schema, RLS, readers, writers, routes, and RPC context.
  • Best for "what touches this table?", "is this table protected?", and

"what code reads/writes this table?"

  • Pair with preflight_table before implementation when the user needs a more

edit-oriented table preflight.

route_context

Use for route-centered questions.

  • Includes handler, imports, database touchpoints, RPCs, and nearby policy

context.

  • Best for "what does this route do?", "what data does this endpoint touch?",

and "what is downstream of this route?"

  • Pair with auth_path for auth-boundary-specific questions.

rpc_neighborhood

Use for RPC-centered questions.

  • Includes callers, touched tables, RLS context, and nearby implementation

evidence.

  • Best for "who calls this RPC?", "what tables does this function touch?", and

"what policies matter for this RPC?"

  • Pair with trace_rpc when the user needs a narrower evidence trace.

Feedback Logging

Log agent_feedback when a neighborhood bundle here was notably useful, partial, noisy, stale, wrong, or wasted the turn. Skip routine calls.

Required procedure (see /mako-ai:mako-guide for full rules and reason-code vocabulary):

  1. Call recall_tool_runs to get the prior run's requestId. Do not

fabricate one — if no run is recalled, skip feedback.

  1. Call agent_feedback with referencedToolName,

referencedRequestId, grade: "full" | "partial" | "no", reasonCodes from the starter vocabulary in /mako-ai:mako-guide, and a short reason.

See Also

  • Use /mako-ai:mako-trace for narrower route/table/RPC evidence traces.
  • Use /mako-ai:mako-graph for paths between entities or blast radius.
  • Use /mako-ai:mako-database for direct live DB schema/RLS/RPC inspection.
Compartilhar X LinkedIn