Individual skill
skill-creation-enabler
Identify coverage gaps and maintenance opportunities in a skill library, then prepare an approval-gated creation or improvement plan. Use for: skill gap analysis, missing capability, library health check, skill maintenance.
.grok/skills/skill-creation-enabler/SKILL.md
Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- grok Repository topic
- prompt-engineering Repository topic
- workflow-automation Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,159 bytes
Read excerpt
# Skill Creation Enabler
## Purpose
Use this skill to assess whether a collection has meaningful capability gaps, outdated package metadata, duplicated skills, or missing documentation. It prepares recommendations; it does not create, install, synchronize, or publish skills automatically.
## Workflow
1. Inspect the configured workspace skill directory and any user-authorized repository source.
2. Compare available packages with the requested capabilities or a maintained requirements list.
3. Identify missing, duplicated, outdated, or poorly documented areas.
4. Prioritize recommendations by user value, safety impact, and maintenance cost.
5. Hand the selected item to `auto-skill-resolver` or `skill-creator` only after the user approves local changes.
6. Keep external backup, repository publication, and marketplace submission as separate approval-gated steps.