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

wins-logger

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

Updated Apr 21, 2026
Search Tags:#automation#logging#evolve#wins#vibe-test#signal-balance
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill wins-logger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wins-logger
Source: https://github.com/estevanhernandez-stack-ed/vibe-test/tree/main/packages/vibe-test/skills/wins-logger
Command: npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill wins-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The wins-logger solves the problem of signal imbalance in Vibe Test by capturing append-only wins to complement friction signals, ensuring /evolve has a truthful representation of successes.

Core Features & Use Cases

  • Append-only wins capture for Pattern #14: absence-of-friction inferences, explicit success markers, and external validation.
  • Emits structured entries to the local wins log to balance the perception of plugin health and user experience.
  • Use Case: after a successful gate or CI run, log a win with a precise symptom and supporting context.

Quick Start

Record a win after a successful run with a clear symptom and supporting evidence.

Frequently Asked Questions about wins-logger

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

FAQPage Schema
How do I log append-only wins to balance friction signals in Vibe Test?▼

The wins log API requires strict field validation for event, context, symptom, and project. Guardrails are applied to prevent over-reporting and maintain accurate signal balance.

When should I capture absence-of-friction inferences during the /evolve workflow?▼

This append-only capture ensures the /evolve flow receives documented wins alongside any relevant external validation signals, complementing friction data.

Does the wins logger work across the generate, audit, and gate command skills?▼

This integration ensures consistent append-only wins capture across all plugin workflow stages to accurately balance friction signals.

What are the limitations of using an append-only wins log for signal balance?▼

Users must provide precise symptoms and supporting context for each entry to maintain truthful signal balance in the /evolve workflow.

Why does Vibe Test need documented wins to complement friction signals?▼

Capturing explicit success markers and external validation ensures the perception of plugin health accurately reflects both friction and successes.

Related Skills

Explore More Software Engineering Skills→
Abhishekojha38Abhishekojha38
3

Memory

Store structured facts and preferences in MEMORY.md and log events to HISTORY.md.

Community
Intermediate
hohai99hohai99

user-intent-pattern-analyzer

Analyzes user prompts to infer stable intent patterns and preferences, adapting guidance accordingly.

Community
Intermediate
estevanhernandez-stack-edestevanhernandez-stack-ed

evolve

Analyze Vibe Test usage logs to propose SKILL edits for manual review.

Community
Advanced
meimeitoumeimeitou
1

ledger

Log daily income and expense transactions with automatic categorization.

Community
Intermediate