toolbelt

Inventory installed Maungs-agentic-toolbelt components and recommend optimal ones for workflow goals.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/Sfzmango/Maungs-agentic-toolbelt --skill toolbelt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: toolbelt
Source: https://github.com/Sfzmango/Maungs-agentic-toolbelt/tree/main/plugins/maungs-agentic-toolbelt/skills/toolbelt
Command: npx skills add https://github.com/Sfzmango/Maungs-agentic-toolbelt --skill toolbelt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

The Maungs-agentic-toolbelt includes 27+ components (agents, skills, hooks) for end-to-end agentic software development, but users often lack visibility into what is installed, which component fits their current goal, or if their environment is properly configured to use the toolbelt. This skill eliminates that guesswork with a single, read-only entry point for discovery, recommendations, and environment validation.

Core Features & Use Cases

  • Stage-Grouped Inventory: Lists all installed agents, skills, and hooks grouped by their place in the software development lifecycle, with exact invocation instructions for each component.
  • Goal-Based Recommendations: Maps your workflow goal (e.g. "find why a test fails", "prep this repo for agentic work") to the best-fit toolbelt component, with a clear explanation of why it is the right choice.
  • Read-Only Environment Check: Runs safe, non-destructive probes to confirm your prompt router, MCP servers, required config files, and git identity are set up correctly, with clear remediation steps for any gaps.
  • Usage Metrics: Summarizes opt-in telemetry to show how often toolbelt suggestions are offered versus actually used, helping you measure the value you get from the toolbelt.
  • Use Case Example: If you are starting work on a new repo and are unsure what the toolbelt can do, invoke this skill with no arguments to see the full inventory. If you have a specific goal like "document this codebase", it will recommend the wiki generator skill with the exact command to run.

Quick Start

Invoke the toolbelt skill with your workflow goal or no arguments to discover available components, get a tailored recommendation for your task, or run a read-only check of your development environment setup.

Frequently Asked Questions about toolbelt

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

FAQPage Schema
How do I find the right agentic workflow component for a specific software engineering task?

To find the right agentic workflow component, you can use a discovery tool that maps your software engineering goal to installed agents, skills, and hooks, providing exact invocation instructions and a clear explanation for the recommendation.

Can I check if my environment is ready for Claude Code or Codex CLI agentic development?

Yes, you can run a read-only environment check that probes your prompt router, MCP servers, required config files, and git identity to confirm readiness for Claude Code or Codex CLI agentic development, offering remediation steps for any gaps.

What is the best way to inventory installed agents and hooks for agentic software development?

The best way to inventory installed agents and hooks is to use a read-only discovery tool that lists all components grouped by their stage in the software development lifecycle alongside their exact invocation commands.

Does the toolbelt environment check modify my project files or configuration?

No, the toolbelt environment check operates with strict guardrails against unintended state changes, running safe non-destructive probes to verify your setup without executing any toolbelt components or modifying your project environment.

Do I need jq installed to discover toolbelt components and run environment checks?

Yes, jq is a required dependency for running the toolbelt skill to discover installed components, match workflow goals to optimal tools, and verify your environment readiness for agentic software development.

How do I measure how often toolbelt suggestions are offered versus actually used?

You can view usage metrics that summarize opt-in telemetry to show how often toolbelt suggestions are offered versus actually used, helping you measure the value you get from the toolbelt components.