mako-guide

Guide Mako MCP skill selection and result interpretation for project investigations.

51|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/drhalto/agentmako --skill mako-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mako-guide
Source: https://github.com/drhalto/agentmako/tree/main/mako-ai-claude-plugin/skills/mako-guide
Command: npx skills add https://github.com/drhalto/agentmako --skill mako-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mako-backed projects can expose many specialized tools, and this Skill helps you choose the right one, interpret results correctly, and decide when to acknowledge static findings versus logging tool feedback.

Core Features & Use Cases

  • Tool Routing: Pick the right Mako skill for discovery, tracing, graph analysis, database inspection, code intelligence, or workflow tasks.
  • Result Interpretation: Read _hints from tool outputs and use them to decide the next best Mako call.
  • Review Policy Guidance: Distinguish between logging agent_feedback for tool quality and using finding_ack for reviewed findings.
  • Use Case: When starting a repository investigation, this Skill helps you orient quickly, avoid unnecessary tool calls, and follow the correct review workflow.

Quick Start

Ask the assistant to use the Mako Guide to determine the best Mako skill for your current investigation and explain whether any tool result should be acknowledged or reviewed for feedback.

Frequently Asked Questions about mako-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right MCP tool for a repository intelligence investigation?

To choose the right MCP tool for a repository intelligence investigation, use a routing guide to match your specific task—like database inspection, graph analysis, or tracing—with the appropriate specialized tool, avoiding unnecessary calls.

What is the difference between agent_feedback and finding_ack in code intelligence workflows?

In code intelligence workflows, agent_feedback logs tool quality, whereas finding_ack acknowledges reviewed static findings, ensuring you correctly distinguish between reporting tool issues and validating evidence-backed results.

How do I interpret tool hints during a code intelligence investigation?

To interpret tool hints during a code intelligence investigation, read the _hints from tool outputs and use them to decide the next best call, ensuring continuous and accurate evidence-backed tracing without inventing schemas.

Can I use a routing guide for database inspection and workflow review tasks?

Yes, you can use a tool routing guide for database inspection and workflow review tasks, as it helps you navigate specialized tools, interpret results correctly, and follow the correct review policy during project investigations.

When should I avoid inventing schemas or request identifiers in MCP investigations?

You should always avoid inventing schemas or request identifiers in MCP investigations to maintain result integrity, relying instead on evidence-backed tracing and actual tool hints to guide your subsequent code intelligence queries.