create-skill

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

2|Updated Mar 29, 2015
One-click install
npx skills add https://github.com/ovisan/dotfiles --skill create-skill-ovisan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/ovisan/dotfiles/tree/main/.grok/skills/create-skill
Command: npx skills add https://github.com/ovisan/dotfiles --skill create-skill-ovisan

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 discovery-optimized description frontmatter value with trigger phrases and slash command references, then lets you approve or edit it. - Scaffolding and Verification: Creates the skill directory (plus optional scripts/ and references/), writes SKILL.md, and verifies the result with cat. - Use Case: You keep pasting the same deployment checklist prompt. Run /create-skill, answer three questions, and get a reusable /deploy-k8s skill saved under .grok/skills/. ## Quick Start Ask the assistant to create a new skill named deploy-k8s that automates your Kubernetes deployment checklist.

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 or ask the assistant to create a skill. It will ask for a name, scope, and description of the workflow, then write a valid SKILL.md file to the appropriate .grok/skills directory.

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 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, such as deploy-k8s. The skill validates the name before proceeding.

Why is the description field important in SKILL.md?

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

How do I use a skill after it is created?

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.