skills.rest
estevanhernandez-stack-ed
estevanhernandez-stack-edCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

friction-logger

Log friction signals from user interactions using an append-only schema.

Updated Apr 21, 2026
Search Tags:#logging#plugin#telemetry#non-blocking#friction#self-evolving#orphan-detection
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill friction-logger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: friction-logger
Source: https://github.com/estevanhernandez-stack-ed/vibe-test/tree/main/packages/vibe-test/skills/friction-logger
Command: npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill friction-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Friction signals from user interactions are often difficult to capture without impacting flow; this skill provides an append-only mechanism to silently log those signals for later analysis and evolution.

Core Features & Use Cases

  • Silent, per-event logging of friction with conservative defaults to avoid false positives.
  • Daily orphan-detection to surface abandoned command signals for /evolve.
  • Uses the friction-log state helper to enrich entries with audit fields while preserving safety.

Quick Start

Enable friction logging by recording friction events at trigger points and running the daily orphan detection pass to recover abandoned sessions.

Frequently Asked Questions about friction-logger

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

FAQPage Schema
How do I log user interaction friction without blocking command execution?▼

You can log friction signals non-blockingly using an append-only mechanism that records events silently during command invocations, preserving user flow while capturing data for later analysis.

What is orphan-detection for abandoned command signals in telemetry logging?▼

Orphan-detection is a daily pass that surfaces abandoned command signals from friction logs, enabling systems to recover incomplete sessions and feed actionable data into self-evolving workflows.

How do I capture friction signals for evolving plugin behavior?▼

Capture friction signals by recording events at trigger points during command invocations, using a state helper to fill audit fields with conservative defaults to avoid false positives.

Does non-blocking friction logging require any external dependencies?▼

No external dependencies are required. The friction logging mechanism operates independently, using internal state helpers to enrich append-only log entries with audit fields during every command invocation.

When should I avoid using append-only friction logging?▼

Avoid append-only friction logging when you need real-time blocking feedback on user interactions, since entries are written silently and non-blockingly for deferred analysis rather than immediate response.

What is the best way to surface actionable friction signals for plugin evolution?▼

The best way is combining silent per-event logging during command invocations with a daily orphan-detection pass, surfacing actionable friction signals to drive self-evolving plugin improvements.

Related Skills

Explore More Software Engineering Skills→
estevanhernandez-stack-edestevanhernandez-stack-ed

wins-logger

Logs append-only win events with strict field validation for Vibe's evolve workflow.

Community
Advanced
ybbms777ybbms777
4

behavior-analyzer

Analyze OpenClaw agent session logs to compute health scores and detect anomalies.

Community
Advanced
Danik911Danik911
1

langfuse-extraction

Extracts Langfuse Cloud API traces, observations, and metrics for debugging, telemetry analysis, and audit trails.

Community
Advanced
Totes-MickGOATsTotes-MickGOATs
3

User Test Monitoring

Capture player inputs, game state, performance metrics, and errors during user testing sessions.

Community
Advanced