consensus-loop:tools

Orchestrate nine consensus-loop analysis tools through a single CLI entry point.

15|4|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/berrzebb/consensus-loop --skill consensus-loop-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consensus-loop:tools
Source: https://github.com/berrzebb/consensus-loop/tree/main/skills/consensus-tools
Command: npx skills add https://github.com/berrzebb/consensus-loop --skill consensus-loop-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides a CLI interface to run nine deterministic analysis tools for consensus-loop workflows, simplifying access to codebase analysis, RTM operations, and FVM checks without requiring the MCP server.

Core Features & Use Cases

  • Provides CLI access to code_map, dependency_graph, audit_scan, coverage_map, rtm_parse, rtm_merge, audit_history, fvm_generate, and fvm_validate.
  • Enables quick generation of symbol indexes, dependency graphs, pattern scans, coverage maps, RTM parsing/merging, and FVM verification against a live server.
  • Use case: a software engineer wants to verify code health by listing symbols, checking dependencies, and validating the functional verification matrix in a single step.

Quick Start

Invoke the tool-runner script with a tool name and parameters to execute a specific analysis, for example code_map --path src/.

Frequently Asked Questions about consensus-loop:tools

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

FAQPage Schema
How do I run codebase analysis tools like code_map and dependency_graph without an MCP server?

You can run codebase analysis tools like code_map and dependency_graph without an MCP server by using a CLI wrapper that maps MCP-like tool calls to node tool-runner commands. This allows direct execution of deterministic analysis from the command line.

What is a consensus-loop workflow for software engineering code health checks?

A consensus-loop workflow for software engineering code health checks orchestrates deterministic analysis tools to perform symbol indexing, dependency analysis, pattern scanning, and test coverage mapping. It verifies code health by validating functional verification matrices in a single step.

Can I generate symbol indexes and dependency graphs for a specific source path via CLI?

Yes, you can generate symbol indexes and dependency graphs for a specific source path via CLI by invoking the tool-runner script with a tool name and parameters, such as code_map --path src/. This directly executes the requested analysis.

How do I parse and merge Requirements Traceability Matrix data from the command line?

To parse and merge Requirements Traceability Matrix data from the command line, use the rtm_parse and rtm_merge CLI tools. These deterministic tools extract and consolidate traceability data without requiring an active server connection.

Do I need an active MCP server to perform audit scans and coverage mapping?

No, you do not need an active MCP server to perform audit scans and coverage mapping. The CLI wrapper satisfies the MCP-to-CLI bridge requirement by mapping tool calls directly to node tool-runner commands, bypassing the server requirement.

What are the limitations of using a CLI wrapper for functional verification matrix generation?

The CLI wrapper for functional verification matrix generation operates deterministically and requires specific node tool-runner commands. It maps MCP-like calls to CLI execution, meaning it lacks the interactive session management capabilities of a live server.