Verify plugin skill claims against Effect v4 source code and runtime behavior.
npx skills add https://github.com/spencerbeggs/effected --skill improve-spencerbeggs
Please help me install this Agent Skill. Skill: improve Source: https://github.com/spencerbeggs/effected/tree/main/.claude/skills/improve Command: npx skills add https://github.com/spencerbeggs/effected --skill improve-spencerbeggs
This skill addresses the drift between documentation and actual library behavior by enforcing a rigorous evidence-based verification process for plugin skills.
Use the improve skill to harvest migration defects into tickets or tune existing skills by verifying them against the vendored source.
High-intent search queries and answers about installing and using this skill.
To verify Effect v4 documentation against runtime behavior, use a structured evidence ladder that cross-references claims against vendored source code and runtime probes to resolve discrepancies. This prevents stale technical knowledge from propagating.
The best way to fix TypeScript migration defects from removed library functions is a harvest and tune workflow that turns migration failures into actionable GitHub tickets and verifies fixes against the vendored Effect v4 source code.
Documentation drift from the actual implementation happens during library migrations when previously documented functions are removed or renamed without updating technical knowledge bases. An evidence-based verification process audits and corrects these discrepancies systematically.
Yes, you can use runtime probes to audit TypeScript plugin skills for accuracy by enforcing strict probe protocols and source-lookup invariants. This ensures claims are factually accurate against actual Effect v4 library behavior.
You need an evidence ladder for TypeScript library migration verification when a migration reveals that previously documented functions have been removed, renamed, or changed, requiring audit and validation against the vendored source.
Without strict source code lookup invariants, verification processes risk propagating incorrect technical knowledge because documentation claims cannot be definitively resolved against the actual Effect v4 implementation behavior.
guillempucheLook up Effect TypeScript library APIs, patterns, and source code.
OneWave-AIScore inbound leads by ICP fit, intent, and urgency, then route them.
congiulucCreate, apply, and roll back EF Core database migrations for .NET applications.
samjhechtDetect design token drift between Figma and code implementations.
