extract-skill

To deduplicate and merge pending skill candidates, review the candidate-queue.md file to identify similar entries, consolidate them, flag duplicates, and prompt for approval before formal creation. This consolidates recurring patterns into a single candidate for review.

The best way to formalize recurring patterns is to identify pending skill candidates from your candidate-queue.md, apply deduplication and merging, and approve them for creation. This automates the process of turning recurring patterns into formal skills for the catalog.

After approving a deduplicated candidate, the skill-creation flow invokes the skill-creator to encode the SKILL.md body and metadata. This generates the formal skill description and registers it with statuses like duplicate, rejected, or created.

Yes, you can review both project-level and user-level candidate queues simultaneously. The process identifies pending skills from both queue levels, consolidates similar candidates, and flags duplicates before prompting for user approval.

When reviewing a candidate queue, the supported statuses include duplicate, rejected, and created. These statuses track the review workflow as you deduplicate, merge, or approve candidates for formal skill creation via the skill-creator.

Yes, you need a candidate-queue.md file to start reviewing skill candidates. The review workflow identifies pending skills directly from this file, then applies deduplication and merging before prompting for approval to invoke the skill-creation flow.