harness-report

Tag friction signals with a fixed payload schema for traceable mitigation.

3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hcross/crewrig --skill harness-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-report
Source: https://github.com/hcross/crewrig/tree/main/.gemini/skills/harness-report
Command: npx skills add https://github.com/hcross/crewrig --skill harness-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and standardizes friction signals during real work to enable rapid diagnosis and remediation.

Core Features & Use Cases

  • Friction tagging: Tag recognition signals (user pushback, tool surprises, workflow gaps) with a canonical payload to enable traceability.
  • Routing to curator: Route reports to the harness curator for clustering and issue creation.
  • Auditable governance: Maintain an auditable trail of frictions to improve AI behavior and process reliability.

Quick Start

Tag a friction signal when a recognition event occurs and include the required payload fields.

Frequently Asked Questions about harness-report

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

FAQPage Schema
How do I capture friction signals during engineering workflows?

To capture friction signals, tag recognition events like user pushback or tool surprises using a fixed payload schema. This requires a writer_agent and evidence entry to ensure reports are traceable for mitigation.

What is friction reporting and when do I need it?

Friction reporting standardizes workflow gaps and tool surprises into auditable payloads. You need it when recognition signals fire during real work to enable rapid diagnosis and remediation.

How do I route friction reports to a curator for governance?

Route friction reports to the curator by submitting the standardized payload. The curator then clusters the evidence entries to create traceable issues for governance and mitigation.

What payload fields are required to tag a workflow friction signal?

Tagging a friction signal requires a writer_agent and at least one evidence entry in the payload. Optional fields like subcategory and canonical support precise routing to the curator.

Can I use friction reporting for process gaps without external dependencies?

Yes, friction reporting operates with no external dependencies. It applies whenever recognition signals fire across the workflow, capturing process gaps and tool surprises into an auditable trail.

What types of recognition signals trigger friction tagging?

Friction tagging triggers on user pushback, sibling-skill workaround, tool surprise, process gap, or safeguard friction. These recognition signals are captured to improve AI behavior and process reliability.