Individual skill

skill-creator

Create or improve reusable skill packages with clear metadata, focused workflows, and appropriate safety boundaries. Use for: create skill, update skill, skill package, new capability.

.grok/skills/skill-creator/SKILL.md

Read pinned source

Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 4, 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.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Skill Creator

## Purpose

Use this skill to design, create, and improve reusable skill packages. Build the package locally first, validate it, and keep external backup or publication separate from creation unless the user explicitly requests those actions.

## Workflow

1. Clarify the capability, intended users, examples, inputs, outputs, and safety constraints.
2. Search the local collection to avoid creating a duplicate capability.
3. Choose a stable lowercase, hyphenated name and create `<workspace>/.grok/skills/<skill-name>/`.
4. Write `SKILL.md` with concise frontmatter, an ordered workflow, expected output, error handling, and relevant authorization boundaries.
5. Add scripts, references, or templates only when they are necessary and reviewed.
6. Test helper scripts with benign representative inputs and validate the package structure.
Back to top