insight-skill-gap

Analyze recent work to identify missing or outdated skills in a skill library.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill insight-skill-gap-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insight-skill-gap
Source: https://github.com/allemaar/open-skills/tree/main/skills/insight-skill-gap
Command: npx skills add https://github.com/allemaar/open-skills --skill insight-skill-gap-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reusable patterns discovered during implementation often stay buried in code and conversation history instead of being captured as skills. This Skill scans recent work, cross-references it against the existing skill index, and proposes new skills or updates so the library keeps pace with actual practice. ## Core Features & Use Cases - Recent Work Scan: Gathers conversation history, changed files, and newly introduced patterns to summarize what was built and which frameworks were used. - Gap Classification: Classifies each detected pattern as already covered, needing an update to an existing skill, or requiring a new skill, with explicit reuse criteria. - Skill Proposals: Drafts skill specifications with domain-prefix naming, prerequisites, complexity estimates, and key sections, then hands approved proposals to the new-skill-creator workflow. - Use Case: After finishing a project that introduced a new ORM integration pattern, run the gap analysis to check whether a skill already covers it, and get a ready-to-approve proposal for a new skill if none exists. ## Quick Start Ask the agent to check for skill gaps based on the recent implementation work and propose any new skills worth creating.

Frequently Asked Questions about insight-skill-gap

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

FAQPage Schema
How do I check which skills are missing from my skill library?

Run the skill-gap analysis after recent implementation work. It scans conversation history and changed files, compares detected patterns against the current skill index, and proposes new skills or updates for anything not yet covered.

How to decide if a code pattern deserves its own skill?

A pattern qualifies when it is reusable (used at least twice or clearly will be), involves non-obvious decisions or gotchas, and spans multiple files or concepts. One-off patterns with no reuse potential are explicitly excluded.

When should I run a skill gap analysis versus a retrospective?

Run the gap analysis when you want to capture reusable patterns as skills after implementation work. Use a broader retrospective skill when you want to review overall outcomes, decisions, and process lessons beyond skill coverage.

Does the skill gap analysis create new skills automatically?

No. It drafts skill proposals with naming, prerequisites, and key sections, then waits for explicit user approval. Approved proposals are executed through the separate new-skill-creator workflow.

What naming convention do proposed skills follow?

Proposed skills must follow a domain-prefix convention, such as drizzle-* or nextjs16-*, grouping skills into families by their technology domain. The analysis verifies no existing skill covers the same domain before proposing a new one.