Receber por email
← Voltar para o catálogo

agentmako

TRIGGER when: user asks about database schema, RLS policies, foreign keys, stored procedures, or table DDL directly. Covers `db_ping`, `db_columns`, `db_fk`, `db_rls`, `db_rpc`, `db_table_schema`.

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-drhalto/svg)](https://www.skillteca.com.br/skills/agentmako-drhalto)

Skills relacionadas

Ver todas de Dados e Análise →

Alerta por categoria

Receba novas skills de Dados e Análise toda segunda

1 email curto, só com as skills novas de Dados e Análise. 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 Database

Use this skill for direct database introspection. These tools require the project to have a live DB binding configured. If the user asks how app code uses database objects, use trace or neighborhood tools instead.

Tools

db_ping

Use to verify database connectivity and project wiring.

  • Best when DB tools seem unavailable or the user asks whether the DB is

connected.

  • Use before deeper DB queries when the binding is uncertain.

db_columns

Use to inspect columns and primary-key details for one or more tables.

  • Best for narrow column questions.
  • Use db_table_schema when indexes, constraints, triggers, or broader table

shape matter.

db_fk

Use to inspect foreign keys and relationships.

  • Best for inbound/outbound relationship questions.
  • Pair with table_neighborhood when code readers/writers also matter.

db_rls

Use to inspect row-level security status and policies.

  • Best for policy and protection questions.
  • Pair with tenant_leak_audit for broader tenant-boundary risk review.

db_rpc

Use to inspect database RPC/function definitions, signatures, args, return shape, language, and security.

  • Pair with rpc_neighborhood or trace_rpc when app-code callers matter.

db_table_schema

Use to inspect the full table shape, including columns, indexes, constraints, foreign keys, RLS, and triggers.

  • Use when column-only output is insufficient.
  • Pair with trace_table or table_neighborhood when code usage matters.

Feedback Logging

Log agent_feedback when a DB introspection result 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-neighborhoods for table/RPC context that combines DB facts

with app-code usage.

  • Use /mako-ai:mako-trace for table/RPC traces through code and schema.
  • Use /mako-ai:mako-workflow for tenant audits and review artifacts.
Compartilhar X LinkedIn