decay

Re-validate and refresh stale decay fields in plugins.vibe-test metadata.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill decay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decay
Source: https://github.com/estevanhernandez-stack-ed/vibe-test/tree/main/packages/vibe-test/skills/decay
Command: npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill decay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the Vibe Test builder profile metadata fresh by gently re-validating and refreshing decay-related fields in the plugins.vibe-test namespace, without silently rewriting user values.

Core Features & Use Cases

  • Fresh-stamp migration for new builders and upgrades.
  • Surface and prompt for renewal of stale fields based on TTL in plugins.vibe-test._meta.
  • Atomic writes to the profile and enforcement that only documented fields are managed.

Quick Start

Run the decay routine to surface the highest-priority stale field and prompt for a gentle confirmation.

Frequently Asked Questions about decay

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

FAQPage Schema
How do I refresh stale builder profile metadata fields using TTL?

TTL-based profile decay re-validates stale fields in the plugins.vibe-test._meta namespace, surfacing the highest-priority expired items and prompting for gentle renewal confirmation without silently overwriting existing user values.

What is profile decay in Vibe Test and when should I run it?

Profile decay is a gentle validation mechanism applied during router runs and profile changes to keep Vibe Test builder metadata fresh. Run it when upgrading builders or needing to surface and prompt for renewal of stale configuration fields.

How do I prevent stale field validation from overwriting my custom profile values?

Profile decay enforces strict handling of known fields and performs atomic writes to ensure safe, auditable changes. It respects the decay_disabled flag and manages only documented fields, preventing silent rewrites of custom user values.

Can I disable TTL decay checks for specific Vibe Test profile configurations?

Yes, you can disable decay checks by setting the decay_disabled flag in the profile. When enabled, the decay routine applies readProfile and writeProfile with strict field handling during router runs to surface stale metadata safely.

What's the best way to migrate fresh-stamp metadata for new Vibe Test builders?

Fresh-stamp migration is handled by running the decay routine, which gently re-validates and refreshes decay-related fields in the plugins.vibe-test namespace to surface stale data and prompt for renewal during builder upgrades.