skills.rest
infraspecdev
infraspecdevOFFICIAL
Explore all skills by this author →
Website𝕏@infraspecdevGitHub

updating-plugin-assets

Manage plugin asset changes with RED to GREEN eval validation.

3|Updated Mar 10, 2026
Search Tags:#claude code#agent prompts#skill updates#red green#eval coverage#plugin assets
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill updating-plugin-assets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: updating-plugin-assets
Source: https://github.com/infraspecdev/tesseract/tree/main/.claude/skills/updating-plugin-assets
Command: npx skills add https://github.com/infraspecdev/tesseract --skill updating-plugin-assets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents plugin asset changes from landing without the eval coverage needed to catch regressions later, making every prompt, agent, command, hook, and eval update traceable and testable.

Core Features & Use Cases

  • Eval-First Workflow: Choose the right eval shape for the change, then move from RED to GREEN with a committed test artifact.
  • Change-Specific Guardrails: Apply different handling for new assets, substantive rewrites, and minor wording fixes so the workflow matches the risk.
  • Repo-Specific Compliance: Keep plugin updates aligned with marketplace versioning, baseline updates, and the required PR paper trail.

Quick Start

Ask me to update a plugin asset and include the required eval coverage, baseline check, and commit-ready guidance.

Frequently Asked Questions about updating-plugin-assets

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

FAQPage Schema
How do I ensure plugin asset changes have eval coverage before committing?▼

Plugin asset changes require eval coverage by moving from RED to GREEN validation, choosing the right eval shape for the change, and committing the test artifact to catch regressions.

What does RED to GREEN validation mean for agent prompts and hook scripts?▼

RED to GREEN validation means writing an eval that fails before the plugin asset change is applied, then making it pass after the update, ensuring every prompt, agent, command, and hook is testable.

Do I need different eval workflows for minor wording fixes versus new plugin assets?▼

Yes, change-specific guardrails apply different handling for new assets, substantive rewrites, and minor wording fixes so the eval workflow matches the risk level of the plugin update.

How do I handle baseline reconciliation when updating MCP prompts in the marketplace?▼

When MCP prompts impact existing baselines, baseline reconciliation is required to keep plugin updates aligned with marketplace versioning and the required PR paper trail.

When should I not use an eval-first workflow for slash command updates?▼

An eval-first workflow applies to all slash command, skill file, and hook script updates in the tesseract marketplace, though minor wording fixes receive lighter change-specific guardrails than substantive rewrites.

Related Skills

Explore More Software Engineering Skills→
GadaaLabsGadaaLabs
67

sculptor

Enforce test-driven development with a failing baseline test before skill implementation.

Community
Advanced
sequenziasequenzia
42

bump-plugin-version

Bump plugin versions in plugin.json and marketplace.json using semantic version rules.

Community
Advanced
OshanKHZOshanKHZ
5

command-development

Design and implement slash commands with YAML frontmatter for Claude Code plugins.

Community
Advanced
miles990miles990

writing-skills

Apply test-driven development cycles to create structured SKILL.md documentation.

Community
Advanced