skill-intake-lifecycle

Govern third-party skill installations from intake through evidence-based review, promotion, retention, or removal.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/skills --skill skill-intake-lifecycle-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-intake-lifecycle
Source: https://github.com/leonardoacosta/skills/tree/main/meta/skills/skill-intake-lifecycle
Command: npx skills add https://github.com/leonardoacosta/skills --skill skill-intake-lifecycle-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Third-party skills installed via npx skills accumulate without accountability, causing context bloat, duplicate domains, and lost local patches. This Skill enforces a governed lifecycle so every installed skill has a rationale, a review date, and an evidence-backed verdict. ## Core Features & Use Cases - Two-source governance: Reads the CLI-owned .skill-lock.json for installation facts while recording lifecycle intent in an append-only skill-journal.jsonl sidecar. - Evidence-based verdicts: Uses session transcript mining and skill-judge scoring (promotion bar of 99/120) to decide retain, promote, or remove outcomes. - Suite-level review: Groups multi-skill sources into one review unit, applying a 20% usage threshold for suite removal with named exceptions. - Use Case: After installing a Firecrawl skill suite, record intake events with a 90-day review date, then at review time count actual invocations, detect a localPatch, and promote the patched skill into an authored package before removing the third-party install. ## Quick Start Review my installed third-party skills in ~/.agents and tell me which ones are due for review, promotion, or removal based on actual usage evidence.

Frequently Asked Questions about skill-intake-lifecycle

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

FAQPage Schema
How do I review third-party skills installed with npx skills?

Review a skill when its review_by or next_review_by date passes, when the lock reports a localPatch, or when duplicate domains appear. Count actual invocations via session transcript mining, then record a review event with a retain, promote, or remove verdict in skill-journal.jsonl.

How do I decide whether to keep or remove an installed agent skill?

Apply the default verdict rules: localPatch triggers promotion, zero invocations by review date triggers removal, used but below the quality bar means retain with a new review date, and suites under 20% member usage default to suite removal with named exceptions.

Can I edit .skill-lock.json to fix skill installation state?

No, .skill-lock.json is owned exclusively by the npx skills CLI and must never be edited, patched, or reformatted. Read it for installation facts like installedAt and localPatch, but record all governance decisions in the separate skill-journal.jsonl sidecar.

What quality score is required to promote a third-party skill?

Promotion requires a skill-judge score of at least 99/120 (grade B) with no unresolved specification, safety, provenance, or reference-closure defects. Invocation count alone never justifies promotion; quality and provenance are separate gates.

What happens if a skill has a localPatch during review?

A localPatch is an automatic promote trigger because reinstalling could erase the only copy of the changed behavior. Preserve and assess the patched content, promote it into an authored package, and only remove the intake install after consumers load the pinned revision.