skills.rest
crewrig
crewrigOFFICIAL
Explore all skills by this author →
WebsiteGitHub

harness-report

Capture workflow friction signals into structured reports for downstream triage.

20|4|Updated May 14, 2026
Search Tags:#workflow#reporting#evidence#triage#attribution#friction
One-click install
npx skills add https://github.com/crewrig/crewrig --skill harness-report-crewrig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-report
Source: https://github.com/crewrig/crewrig/tree/main/artifacts/library/skills/harness-report
Command: npx skills add https://github.com/crewrig/crewrig --skill harness-report-crewrig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Harness Report gives you a fast, consistent way to tag workflow friction the moment it appears, so issues are not lost, misattributed, or repeated across sessions.

Core Features & Use Cases

  • Friction detection: Recognizes user pushback, repeated tool surprises, sibling-skill workarounds, process gaps, and safeguard friction.
  • Accurate attribution: Helps trace the real offender behind a problem, whether it is a skill, tool, process step, or document.
  • Structured reporting: Captures the required metadata for downstream triage, clustering, and issue filing.
  • Example use case: A tool behaves unexpectedly twice in one session, and the skill records the friction immediately with evidence and a suggested fix.

Quick Start

Use the harness-report skill to capture this friction event with the right category, evidence, and offender attribution.

Frequently Asked Questions about harness-report

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

FAQPage Schema
How do I log workflow friction during AI-assisted development sessions?▼

To log workflow friction during AI-assisted development sessions, capture signals like user pushback, repeated tool surprises, or process gaps in a structured report with accurate offender attribution and evidence references for downstream triage.

What is workflow friction attribution and why does it matter?▼

Workflow friction attribution traces the real offender behind a development issue, whether a skill, tool, process step, or document, ensuring problems are not lost or repeated across sessions.

How do I record evidence for repeated tool surprises in my development workflow?▼

Record evidence for repeated tool surprises by capturing the friction event immediately with the right category, evidence references, and standardized payload fields to route the issue for downstream triage and clustering.

Can I use structured reporting to triage safeguard conflicts and process gaps?▼

Yes, structured reporting captures safeguard conflicts and process gaps by recording required metadata for issue routing, enabling downstream triage to cluster and resolve workflow friction efficiently.

When should I capture friction events instead of waiting until the session ends?▼

Capture friction events the moment they appear to prevent issues from compounding. Tagging workflow friction immediately ensures accurate evidence collection and stops issues from being lost or misattributed across sessions.

Related Skills

Explore More Software Engineering Skills→
toqoztoqoz

retro-agent-instructions

Identifies friction in AI-assisted sessions and proposes atomic documentation updates.

Community
Intermediate
GenEducationGenEducation

bmad-os-gh-triage

Analyze open GitHub issues and generate a structured markdown triage report.

Official
Advanced
hcrosshcross
3

harness-report

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

Community
Intermediate
JaivishChauhanJaivishChauhan
6

vercel-deployment

Deploy Next.js projects to Vercel and manage domains and environments via MCP commands.

Community
Advanced