create-skill

Interactively scaffold new Grok skill directories with SKILL.md files.

Updated May 28, 2026
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill create-skill-changfengpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/create-skill
Command: npx skills add https://github.com/changfengpro/agent-skills --skill create-skill-changfengpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a new Grok skill requires knowing the exact SKILL.md frontmatter format, directory conventions, and naming rules. This Skill guides you through an interactive interview and writes a valid, auto-discoverable skill to disk. ## Core Features & Use Cases - Guided Requirements Gathering: Asks for the skill name, scope (project vs user), and intended behavior one question at a time, with name validation. - Description Drafting: Writes a trigger-rich description frontmatter value so Grok can auto-invoke the new skill, with user approval before saving. - On-Disk Scaffolding: Creates the skill directory, optional scripts/ and references/ folders, writes SKILL.md, and verifies the result. - Use Case: You keep pasting the same deployment checklist prompt. Run /create-skill, describe the workflow, and get a reusable /deploy-k8s slash command saved to your repo's .grok/skills/ folder. ## Quick Start Run /create-skill and answer the prompts to scaffold a new skill with a name, scope, and description.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I create a new Grok skill?

Run /create-skill and answer the interactive prompts for skill name, scope, and behavior. The skill writes a SKILL.md file with valid YAML frontmatter to your chosen .grok/skills directory and verifies it on disk.

What is the difference between project and user scope for skills?

Project scope saves the skill to <repo-root>/.grok/skills/<name>/ so it is available only in that repository and shareable with teammates. User scope saves to ~/.grok/skills/<name>/ making it available across all your projects.

What naming rules apply to Grok skill names?

Skill names must use lowercase letters, digits, and hyphens only, start and end with a letter or digit, and be 2-64 characters long. The create-skill workflow validates the name before proceeding.

Why is the description field important in SKILL.md?

The description frontmatter controls auto-invocation, telling Grok when to trigger the skill based on user intent. It should state what the skill does, include trigger phrases and keywords, and mention the slash command name.

How do I use a skill after creating it?

Invoke it via the slash command /<skill-name>, through the TUI menu with /skills <skill-name>, or let Grok auto-invoke it when your request matches the description. Skills auto-reload within seconds of file changes.