skill-crafter

skill-crafter is a skill for Claude Code from cobusgreyling/grok-build-showcase. It costs 92 tokens per session (801 once invoked), scanned A, original, MIT.

A skill for writing Grok Build skills: instruction files that tell an agent when and how to perform a particular workflow. It creates the required metadata, steps, tool references, and usage guidance.

In plain words
What is it for?
Use it to scaffold or write a new production-ready SKILL.md, define trigger phrases and argument hints, document numbered procedures, and add safety or verification rules.
Why use it?
It helps turn an informal workflow into a structured skill that agents can discover and follow. The required format makes triggers, inputs, actions, and success criteria clear.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions AGENTS.md.

Good fit Use it to scaffold or write a new production-ready SKILL.md, define trigger phrases and argument hints, document numbered procedures, and add safety or verification rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cobusgreyling/grok-build-showcase/skill-crafter
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cobusgreyling/grok-build-showcase --skill skill-crafter
Clone the repo
git clone --depth 1 https://github.com/cobusgreyling/grok-build-showcase

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for skill-crafter

README.md
[![agentmods](https://agentmods.dev/badge/skills/cobusgreyling/grok-build-showcase/skill-crafter/github.svg)](https://agentmods.dev/skills/cobusgreyling/grok-build-showcase/skill-crafter)
Your own site
<a href="https://agentmods.dev/skills/cobusgreyling/grok-build-showcase/skill-crafter"><img src="https://agentmods.dev/badge/skills/cobusgreyling/grok-build-showcase/skill-crafter/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for skill-crafter

Your own site · 80×15
<a href="https://agentmods.dev/skills/cobusgreyling/grok-build-showcase/skill-crafter"><img src="https://agentmods.dev/badge/skills/cobusgreyling/grok-build-showcase/skill-crafter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 801 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.00801
Opus 5 $0.00046 $0.00400
Sonnet 5 $0.00018 $0.00160
Haiku 4.5 $0.00009 $0.00080

Measured 11d ago against content hash 72f51e45fba1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

skill-crafter scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.grok/skills/skill-crafter/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill Crafter

You produce skills that are immediately useful, auto-discoverable, and follow the exact conventions from the official Grok Build skills guide.

Required Output Format

Every skill you create must contain:

---
name: kebab-case-name
description: >
  One or two sentence description that is specific enough for automatic
  invocation. Include example trigger phrases the user might say.
when-to-use: Optional but recommended — explicit trigger phrases.
argument-hint: "<example usage>"
metadata:
  short-description: "Very short label (optional)"
---

# Human Friendly Title

Intro paragraph.

## Steps (or Usage / Workflow)

1. Numbered, concrete actions.
2. Each step should mention tools by name when relevant
   (`read_file`, `grep`, `spawn_subagent`, `run_terminal_command`, `write`, etc.).
3. Include success criteria or "what good looks like".

## Principles / Important Notes (recommended)

- Anti-hallucination, safety, or verification rules.
- References to other skills or AGENTS.md sections when useful.

Creation Process

  1. Clarify the workflow the skill should capture.

    • Ask for (or infer) the exact trigger phrases users will say.
    • Identify the primary tools the skill will use.
  2. Write excellent description text.

    • It must be specific. Bad: "Helps with commits". Good: "Create well-formatted git commits following conventional commit standards. Use when the user wants to commit changes or asks for /commit."
  3. Structure the body:

    • Start with a short purpose.
    • Use numbered steps (the agent loves ordered procedures).
    • Include verbatim prompts, command examples, or output formats where the skill needs precision.
    • Add "Important Principles" or "Verification" sections for non-trivial skills.
  4. Make it self-contained but reference official docs or other skills when relevant (e.g. "follow the todo discipline in AGENTS.md").

  5. After writing the file, suggest how the user can test it:

    • /skills <new-name>
    • Run a small task that should trigger it automatically.

Read the full file on GitHub · 89 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 89 lines · 92 tokens per session scan A 72f51e45fba1

Subscribe to this mod's changes

skill-crafter is a skill published in the GitHub repository cobusgreyling/grok-build-showcase (2 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 801 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

stuck

Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.

QwenLM/qwen-code · 57 tokens

structured-debugging

Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…

QwenLM/qwen-code · 85 tokens

desktop-brand-builder

Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.

QwenLM/qwen-code · 69 tokens

repo-hygiene

Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.

QwenLM/qwen-code · 48 tokens

coordinate

Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.

QwenLM/qwen-code · 43 tokens

find-simplifications

Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…

QwenLM/qwen-code · 103 tokens