meta-skill-improvement

Maintains agent skill files by routing session learnings into documentation updates.

11|9|Updated May 25, 2026
One-click install
npx skills add https://github.com/projectbluefin/lab --skill meta-skill-improvement-projectbluefin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-skill-improvement
Source: https://github.com/projectbluefin/lab/tree/main/docs/skills/meta-skill-improvement
Command: npx skills add https://github.com/projectbluefin/lab --skill meta-skill-improvement-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent sessions produce work but often lose the lessons learned, forcing the next agent to repeat the same trial-and-error. This Skill enforces a write-back loop so every non-trivial session ends with updated skill files, verified examples, and filed issues for unresolved gaps. ## Core Features & Use Cases - Failure Triage: Checks failed Argo Workflows from the past 7 days at session start and routes each failure pattern to the relevant skill file. - Skill Routing Table: Maps changed areas (Argo Workflows, KubeVirt, ArgoCD, tests, CI) to the specific skill file that must be updated. - Documentation Hygiene: Verifies code examples against Context7 docs, audits skill files against the canonical spec, and removes dated or resolved entries. - Use Case: After debugging a KubeVirt VM provisioning failure, route the discovered pattern into kubevirt-vms/SKILL.md, verify any Argo examples against Context7, and file a GitHub issue for remaining infra gaps before creating the PR. ## Quick Start Run the skill improvement loop to check recent nightly failures and write back any patterns discovered in this session to the appropriate skill files.

Frequently Asked Questions about meta-skill-improvement

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

FAQPage Schema
How do I update agent skill files after a work session?▼

Route the changed area using the skill routing table to find the target SKILL.md file, then write the durable pattern into it. Verify any library examples against Context7 docs and remove dated or resolved entries before committing.

How to check failed Argo Workflows from previous nights?▼

List failed workflows in the argo namespace using the argo-mcp list_workflows tool, then fetch logs for each failure to identify the failing step. Failures are retained for 7 days, so triage must happen at session start.

When should I not update a skill file?▼

Skip updates for read-only research sessions with no output and doc-only passes that create no new pattern. Skill files are evergreen procedures, not logs of one-off tasks or session history.

What sections must a valid skill file contain?▼

A valid skill file needs frontmatter with name and description, plus sections for When to Use, When NOT to Use, Core Process, Common Rationalizations, Red Flags, and Verification. Missing Verification or Red Flags sections are the most common gaps.

Where do unresolved infrastructure gaps get tracked?▼

Unresolved gaps are filed as GitHub issues in the projectbluefin/lab repository using the gh CLI with a bug label. Skill files must not be used as backlogs for open questions or blockers.