home / skills / sounder25 / google-antigravity-skills-library / 21_skill_gap_identifier

21_skill_gap_identifier skill

safe

This skill analyzes failures or requests to scaffold new capabilities, creating structured skill folders, templates, and metadata for smooth evolution.

npx playbooks add skill sounder25/google-antigravity-skills-library --skill 21_skill_gap_identifier

Review the files below or copy the command above to add this skill to your agents.

Files (5)

SKILL.md

1.8 KB

---
name: Skill Gap Identifier
description: Analyzes failures or user requests to automatically scaffold new skills, ensuring structural evolution.
version: 1.0.0
author: Antigravity Skills Library
created: 2026-01-16
leverage_score: 5/5
---

# SKILL-021: Skill Gap Identifier

## Overview

A **meta-skill** for system evolution. It transforms "I wish I could do X" into a concrete plan for "Method X" by scaffolding the directory structure, metadata, and templates for a new skill. This ensures the system evolves structurally rather than relying on ad-hoc scripts.

## Trigger Phrases

- `create skill`
- `new capability`
- `missing tool`
- `scaffold skill`

## Inputs

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| `--Name` | string | Yes | - | Short name (e.g., `log_parser`) |
| `--Trigger` | string | Yes | - | When should this run? |
| `--Description` | string | Yes | - | What does it do? |

## Outputs

### 1. New Directory Structure

```
skills/
  22_log_parser/
    SKILL.md      (Template)
    scripts/
    examples/
    templates/
```

### 2. JSON Status

```json
{
  "status": "CREATED",
  "id": "SKILL-22",
  "path": "C:\\...\\skills\\22_log_parser"
}
```

## Preconditions

1. `skills` root directory exists and is writable.
2. PowerShell 5.1+ or Core 7+.

## Safety/QA Checks

1. **Collision Detection**: Checks strict naming and ID availability.
2. **Sanitization**: Cleans directory names to be safe.

## Stop Conditions

| Condition | Action |
|-----------|--------|
| Name already exists | Fail or increment ID |

## Implementation

See `scripts/propose_skill.ps1`.

## Integration with Other Skills

1. **SKILL-020 (Postmortem)** identifies a gap.
2. User or Agent calls **SKILL-021** to fill it.
3. Agent then implements the logic in the new folder.

Overview

This skill scaffolds new capability packages when a feature gap is detected. It converts requests like "I wish I could do X" into a concrete directory, metadata, and template layout so the system can evolve structurally. It enforces safe naming, collision checks, and returns a JSON status summary.

How this skill works

Given a name, trigger, and description, the skill creates a numbered skill folder with standardized subfolders and starter templates. It validates the skills root, sanitizes inputs, checks for name/ID collisions, and either creates the artifact or increments the ID. On success it emits a JSON status payload with path and ID, and leaves a predictable scaffold agents can implement.

When to use it

When a postmortem or user request identifies a missing capability
When an agent needs a standardized starting point to implement new logic
During backlog refinement to convert feature ideas into implementable packages
Before manual ad-hoc scripts are committed to avoid structural drift

Best practices

Ensure the skills root directory exists and is writable before invoking
Provide concise Name, Trigger, and Description to generate useful metadata
Use strict, consistent naming conventions to minimize collisions
Run collision detection first in dry-run mode if available
Pair the scaffold step with a follow-up task to implement logic in the new folder

Example use cases

Automated creation of a log parsing skill folder after the monitoring pipeline flagged missing tooling
Agent-detected gap during an integration test triggers scaffold for a new connector
Turning a user feature request into a deterministic skill skeleton for sprint planning
Batch-generating numbered skill directories when mapping an emergent capability roadmap

FAQ

What inputs are required to run this skill?

You must supply a short Name, the Trigger that will invoke the capability, and a Description of what it should do.

How does it handle name collisions?

It checks for existing names and either fails or increments the numeric ID to avoid overwrite, depending on configuration.