tooling-floor

Identify project tooling gaps and prioritize missing tools.

Updated May 2, 2026
One-click install
npx skills add https://github.com/robigewii/tooling-floor --skill tooling-floor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tooling-floor
Source: https://github.com/robigewii/tooling-floor/tree/main
Command: npx skills add https://github.com/robigewii/tooling-floor --skill tooling-floor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tooling Floor surfaces the tooling gaps in your project — before they become 38-commit cleanup chains.

Core Features & Use Cases

  • Two entry-paths (Inception and Retroactive) share a common toolbelt matrix and a 4-tier prioritization framework.
  • Inventory, mapping, and classification: for each tech, wire it to the canonical tools and categorize missing items as CRITICAL/HIGH/MEDIUM/LOWER.
  • Sequencing and hand-off: deploy those tools as multi-version drain chains and deliver concrete artifact outputs, including CI gates, calibrated configs, and a sequenced backlog.
  • Per-task gauntlet templates in templates/ enabling multiple surfaces (MVE, slash command, and pre-commit hook) to catch issues early.
  • Output documentation: produces a single survey document capturing state, plan, and metrics so teams can start first adoption chain.

Quick Start

Run npx tooling-floor install to copy the skill into ~/.claude/skills/tooling-floor and then invoke /tooling-floor in Claude Code to begin.

Frequently Asked Questions about tooling-floor

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

FAQPage Schema
How do I audit missing linters and CI gates in my project before they cause massive cleanup chains?

Surfacing tooling gaps early requires mapping your tech stack to canonical tools and categorizing missing items. This skill inventories your project to classify missing linters and CI gates, preventing costly multi-commit cleanup chains later.

What is the best way to prioritize adding missing workflow tooling to a new codebase?

Prioritizing workflow tooling uses a 4-tier framework that classifies gaps as CRITICAL, HIGH, MEDIUM, or LOWER. This approach enforces day-1 CRITICAL gates and sequences retroactive tooling additions to ensure foundational stability before lower-priority items.

How do I deploy a prioritized tooling backlog as multi-version drain chains?

Deploying a prioritized backlog involves sequencing tooling gaps into multi-version drain chains. This skill generates concrete artifacts including CI gates, calibrated configurations, and a sequenced backlog to guide progressive adoption across project versions.

Can I use Claude Code to enforce a per-task gauntlet workflow with pre-commit hooks?

Claude Code can enforce a per-task gauntlet workflow using portable templates shipped in the templates directory. These templates enable multiple surfaces including MVE, slash commands, and pre-commit hooks to catch tooling issues early.

Does this tooling survey approach support both new project inception and retroactive gap analysis?

This tooling survey supports both inception and retroactive scenarios. Both entry-paths share a common toolbelt matrix and 4-tier prioritization framework, allowing teams to map missing tools whether starting fresh or cleaning up an existing project.

What limitations exist when generating a tooling survey document for a complex tech stack?

Generating a tooling survey document relies on mapping each technology to canonical tools within its shared toolbelt matrix. Complex tech stacks may require careful manual classification to ensure the resulting state, plan, and metrics accurately reflect all CRITICAL and HIGH priority tooling gaps.