ReddRadar
Agent skill
tooling-discovery
Use when looking for available tools, MCP servers, or CLI utilities for a task. Triggers: 'what tools do I have', 'is there an MCP for this', 'what's available', 'find a tool for', 'discover tooling', 'what CLI tools exist'. NOT for: documenting existing tools (use documenting-tools).
Install this agent skill to your Project
npx add-skill https://github.com/axiomantic/spellbook/tree/main/skills/tooling-discovery
SKILL.md
Tooling Discovery
Invariant Principles
- Registry is source of truth. Only recommend tools that exist in the curated YAML registry. Never fabricate tool entries.
- Trust tiers are non-negotiable. Always present trust classification. Tier 4+ tools require explicit risk warnings before recommendation.
- Detection before recommendation. Always run the tooling_discover MCP tool to check availability. Do not skip detection and guess.
Workflow
Step 1: Determine Domain Keywords
Extract domain keywords from one of:
- User's explicit request (e.g., "what tools exist for Jira integration?")
- Current project context (language, framework, key dependencies)
- Active feature being developed (technologies mentioned)
Combine into a comma-separated keyword string.
Step 2: Call tooling_discover
tooling_discover(
domain_keywords="<comma-separated keywords>",
project_path="<project root or empty for auto-detect>"
)
Step 3: Present Results
Group results by availability and trust:
Available Tools (detected on this system):
- List tools where
available: true, grouped by detection method - For each: name, type, trust tier label, description, how detected
Registry Tools (known but not detected):
- List tools where
available: false - For each: name, type, trust tier label, description, source URL
Trust Warnings (tier 4+):
- For any tool with trust_tier >= 4, prominently display risks and next_steps
Step 4: Suggest Integration
For available but potentially unused tools:
- Suggest how to leverage them in the current workflow
- For MCP servers: note they are already connected
- For CLIs: note they can be called via Bash tool
- For libraries: note they are already in project dependencies
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
axiomantic/spellbook
spellbook-auditing
Meta-audit skill for spellbook development. Spawns parallel subagents to factcheck docs, optimize instructions, find token savings, and identify MCP candidates. Produces actionable report.
axiomantic/spellbook
documentation-updates
Use after modifying library skills, library commands, or agents to ensure CHANGELOG, README, and docs are updated
axiomantic/spellbook
project-encyclopedia
[DEPRECATED] Use project-level AGENTS.md files instead. Previously used for first-session codebase onboarding and persistent glossary creation.
axiomantic/spellbook
reviewing-impl-plans
Use when reviewing implementation plans before execution. Triggers: 'is this plan solid', 'review the plan', 'check before I start building', 'anything missing from this plan', 'will this plan work', 'audit the implementation plan'. NOT for: reviewing design documents (use reviewing-design-docs) or creating plans (use writing-plans).
axiomantic/spellbook
session-resume
Session resume protocol and session repairs handling. Loaded when spellbook_session_init returns resume_available: true, or when session_init returns a repairs array. Triggers: 'resume', 'continue', 'where were we', session resume, session repairs.
axiomantic/spellbook
brainstorming
Use when exploring design approaches, generating ideas, or making architectural decisions. Triggers: 'explore options', 'what are the tradeoffs', 'how should I approach', 'let's think through', 'sketch out an approach', 'I need ideas for', 'how would you structure', 'what are my options'. Also invoked by develop when design decisions are needed.
Didn't find tool you were looking for?