skill-lifecycle

Automate agent skill lifecycle state transitions with permission checks.

4.9k|780|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/iflytek/skillhub --skill skill-lifecycle-iflytek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-lifecycle
Source: https://github.com/iflytek/skillhub/tree/main/.agents/skills/skill-lifecycle
Command: npx skills add https://github.com/iflytek/skillhub --skill skill-lifecycle-iflytek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill manages the lifecycle state of agent skills, ensuring that states and transitions are valid and governing skill publication and visibility.

Core Features & Use Cases

  • State Management: Manages container states, version states, review workflow states, visibility overlay, and governance actions.
  • Skill Versions: Tracks different versions of skills with states like draft, scanning, uploaded, pending review, published, rejected, and yanked.
  • Review Workflow: Provides a review process where skill versions can be approved or rejected.
  • Visibility Control: Manages skill visibility at different levels: public, namespace only, or private.
  • Governance: Allows for governance actions such as hiding, yanking, archiving, and unarchiving skills.

Quick Start

Use the skill-lifecycle skill to set a skill to 'active' state.

Frequently Asked Questions about skill-lifecycle

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

FAQPage Schema
How do I manage agent skill lifecycle states from draft to published?

Skill lifecycle management automates state transitions from draft to published by tracking version states, enforcing review workflows, and validating permission checks to ensure secure skill publication.

What is the review workflow for approving agent skill versions?

The review workflow for agent skill versions allows pending versions to be systematically approved or rejected, ensuring governance and integrity before a skill transitions to the published state.

How do I control agent skill visibility across public and private namespaces?

Visibility control governs skill accessibility by setting overlay levels to public, namespace only, or private, securing skill distribution across different deployment environments.

What governance actions can I apply to yank or hide published agent skills?

Governance actions allow you to yank, hide, archive, or unarchive agent skills, maintaining operational security and state validity for active and deprecated skill containers.

Can I use skill-lifecycle to automate container state management without manual permission checks?

Yes, skill-lifecycle automates container state management by operating with various state models and executing built-in permission checks to secure lifecycle actions without manual oversight.

Why are my agent skill version state transitions being rejected?

State transitions for agent skill versions are rejected if they violate defined state models or fail permission checks, ensuring that only secure and valid lifecycle actions are executed.