Loading ToolBench
A collection of Claude Code plugin skills for software development workflows including intake, planning, code exploration, testing, documentation, and review processes
This server exposes 20 tools via bash scripts with NO visible input schemas, parameter descriptions, or output documentation. Tool names use a namespace prefix (flagrare:) but lack action verbs (e.g., 'flagrare:intake' instead of 'assess_project' or 'run_intake'). Descriptions are generic 1-2 sentence summaries with no guidance on when to use each tool, what parameters they accept, or what they return. No JSON Schema definitions found in source. Hook scripts suggest tool chaining logic but this is not exposed to the MCP client. The server is STDIO-only, making it inaccessible to hosted MCP clients. Tool definitions appear to be inferred from install.sh output rather than explicitly registered with schemas.
Acceptance Test Driven Development planning skill
Codebase exploration skill for understanding project structure and conventions
Figma design matching skill
Five lens review skill for comprehensive code analysis
Implementation review skill for code quality assessment
Intake skill for initial project assessment
Open pull request skill
Pull request review skill
No input schemas visible for any tool. All 20 tools lack JSON Schema definitions with parameter types, constraints, and descriptions.
Tool names lack action verbs. All tools use namespace:noun format (e.g., 'flagrare:intake') instead of verb_noun (e.g., 'assess_project', 'run_intake'). LLMs rely on verb-first names to infer intent before reading descriptions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 14 | 2026-07-28+ | v2 |
Release check skill for determining release readiness and drafting CHANGELOG
Research catalog skill for documenting external research sources
Smoke testing skill
Staleness audit skill for identifying outdated code and dependencies
Test Driven Development writer skill
Ticket creation skill for issue tracking
Uninstall skill for removing the plugin
Update skill for refreshing plugin and marketplace
UX audit skill for user experience assessment
Work preparation skill for setting up development environment
Wrap-up skill for finalizing work and preparing for review
Documentation writing skill
Descriptions are generic and under 20 characters for most tools (e.g., 'Intake skill for initial project assessment'). No guidance on parameters, return values, or when to use each tool.
Tool definitions inferred from install.sh output, not explicitly registered with MCP protocol. No evidence of tool registration via MCP ListTools or explicit schema definitions.
No output schemas documented. No guidance on what fields each tool returns, data types, or structure. LLMs cannot plan downstream tool calls or extract required data without documented return types.