ariffazil/create-skill
skills/create-skill/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add ariffazil/openclaw-workspace create-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 8, 2026, 4:02 AM256.9s2 files scanned
SKILL.md
- name:
- create-skill
- id:
- create-skill
- version:
- 1.0.0
- risk_tier:
- low
- description:
- Interactively create a new Grok skill (SKILL.md + optional scripts/references).
- short-description:
- Create a new Grok skill
- owner:
- AAA
- autonomy_tier:
- T1
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.
Related Skills
ariffazil/openclaw
testing
VerifiedTrustedCommunity
OpenClaw edge agent bridge — operational triage, doctor, restart, and A2A bridge routing for the federation edge (Telegram surface). USE WHEN: "openclaw unhealthy", "gateway down", "edge bot not responding", "a2a bridge disconnected", "watchdog tripped", "openclaw doctor", "openclaw restart". NOT for token/security audit — use FORGE-telegram-audit.
2SKILL.mdUpdated Aug 8, 2026
ariffazil/MiniMax Image Generation
tools
VerifiedTrustedCommunity
Generate images, videos, TTS, voice clone, and music via MiniMax MCP server. Use when user asks to "draw", "generate image", "create picture", "make a photo", "text to image", "image generation".
2SKILL.mdUpdated Aug 8, 2026
ariffazil/arifos-constitutional-judge
testing
VerifiedTrustedCommunity
Single load-bearing constitutional-judgment skill. Routes all F1–F13, verdict, hold, seal, scope, authority and floor-check calls through the live arif_judge surface. Replaces 7 overlapping predecessors (arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge).
2SKILL.mdUpdated Aug 8, 2026
ariffazil/FORGE-lsp-pre-edit-gate
development
VerifiedTrustedCommunity
MANDATORY LSP grounding gate BEFORE any code mutation on .ts, .py, .js, .tsx, .jsx files. Forces the agent to read real-time compiler diagnostics and structural project context before editing — eliminating blind guesses and anchoring every mutation in F2 (TRUTH). Routes through arifOS kernel (:8088) for centralized gate logic.
2SKILL.mdUpdated Aug 8, 2026