wiring-test

Generate YAML metadata verifying feature integration within Loom plans.

53|1|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/cosmix/loom --skill wiring-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiring-test
Source: https://github.com/cosmix/loom/tree/main/skills/wiring-test
Command: npx skills add https://github.com/cosmix/loom --skill wiring-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common failure mode where code compiles and tests pass, but a feature is not actually integrated into the application (e.g., commands not registered, endpoints not mounted).

Core Features & Use Cases

  • Generate Verification YAML: Helps create truths, artifacts, and wiring fields for Loom plan stages.
  • Prove Integration: Ensures features are correctly wired into the system, not just present.
  • Use Case: When developing a new API endpoint, use this skill to generate the YAML that verifies the endpoint is registered in the router, its handler exists, and it's mounted in the application's main routes.

Quick Start

Use the wiring-test skill to generate YAML for verifying a new CLI command integration.

Frequently Asked Questions about wiring-test

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

FAQPage Schema
How do I verify feature integration when tests pass but the feature is not wired in?

To verify feature integration, you can generate YAML metadata defining `truths`, `artifacts`, and `wiring` patterns. This proves features are correctly wired into the system by checking that commands are registered, endpoints are mounted, and modules are exported.

How do I generate YAML to test that a new API endpoint is mounted in the router?

Generate verification YAML for API endpoints by defining specific `truths` and `wiring` fields. This verifies the endpoint handler exists, is registered in the router, and is mounted in the application's main routes within your Loom plan.

What is feature integration verification in Loom plans?

Feature integration verification in Loom plans is the process of proving that commands, endpoints, modules, and UI components are correctly wired into the application. It uses YAML metadata containing `truths`, `artifacts`, and `wiring` patterns to validate system integration.

Can I verify CLI command registration and UI component rendering using YAML?

Yes, you can verify CLI command registration and UI component rendering using YAML. The verification process supports CLI commands and UI components by generating specific `truths`, `artifacts`, and `wiring` patterns to prove they are fully integrated.

What is the best way to prove modules are exported and endpoints are mounted?

The best way to prove modules are exported and endpoints are mounted is generating YAML metadata with specific `wiring` patterns. This validates actual system integration rather than just code compilation, ensuring features are present and correctly wired.