create-skill
Interactively create a new Grok skill (SKILL.md + optional scripts/references). Use when the user wants to create a skill, scaffold a skill, or runs /create-skill.
- License 许可
- MIT
- 最近更新
- 2026-07-19
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- create-skill
- metadata
- { "short-description": "Create a new Grok skill" }
- description
- Interactively create a new Grok skill (SKILL.md + optional scripts/references). Use when the user wants to create a skill, scaffold a skill, or runs /create-skill.
03 SKILL.md 正文
Create Skill
Interactively gather requirements from the user and create a fully working Grok skill on disk.
Step 1: Gather information
Ask the user the following questions one at a time as regular conversation questions (do NOT use structured option prompts for free-text inputs):
- Skill name - ask the user to type a name. Lowercase letters (a-z), digits (0-9), and hyphens (-) only. Must start and end with a letter or digit. Must be 2-64 characters long (e.g.
deploy-k8s). Validate the name before proceeding. - Scope - present the user with two options:
- Project (Recommended):
<repo-root>/.grok/skills/<name>/SKILL.md- available only in this repo, shareable with teammates - User:
~/.grok/skills/<name>/SKILL.md- available in all projects - Default to Project if inside a git repo, otherwise User.
- Project (Recommended):
- What it should do - ask the user to describe the workflow, paste an example prompt they keep repeating, or explain the task the skill should automate.
Step 2: Draft the description
Write a description frontmatter value that includes:
- What the skill does (1-2 sentences)
- Trigger phrases and keywords so Grok knows when to auto-invoke it
- The slash command name (e.g. "Use when the user runs /deploy-k8s")
Show the drafted description to the user and let them approve or edit it.
Step 3: Create the directory
Run this bash command to create the skill directory:
mkdir -p <SKILL_DIR>
Where <SKILL_DIR> is:
- User scope:
~/.grok/skills/<name> - Project scope:
<repo-root>/.grok/skills/<name>
If the skill needs helper scripts, also create <SKILL_DIR>/scripts/.
If the skill needs reference docs, also create <SKILL_DIR>/references/.
Step 4: Write SKILL.md
Use search_replace with an empty old_string to create the file at <SKILL_DIR>/SKILL.md.
The file MUST follow this exact format:
---
name: <skill-name>
description: <the description from Step 2>
---
<markdown body with instructions, steps, code blocks>
Also write any supporting files (scripts, references) using the same create method.
Step 5: Verify and confirm
- Run
cat <SKILL_DIR>/SKILL.mdto verify the file was written correctly. - Tell the user the skill is ready and how to use it:
- Slash command:
/<skill-name> - TUI menu:
/skills <skill-name> - Automatic: Grok will invoke it when the description matches user intent
- Slash command:
- Tell the user the skill should appear in the slash menu within a few seconds (skills auto-reload when files change on disk).
Guidelines
- Keep the SKILL.md body focused and actionable. It is a prompt for the agent, not documentation.
- The
descriptionfield is critical. It controls auto-invocation. Be specific with trigger words. - Prefer referencing existing CLI tools over writing custom scripts.
- Do NOT skip creating the directory. The file will fail to save without it.
- Always use absolute paths when creating files to avoid writing to the wrong location.
04 同仓库更多 Skills
Zotero
Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.
zoom-apps-sdk
Use when using Apps SDK.
youtube
Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".
yeet
Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.
x-post-creator
Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.
x-api
Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".