Automated summary
This skill scaffolds a new AgentKit asset (skill, command, agent, Cursor rule, or guideline) at the correct location with proper frontmatter and template.
Strengths
- Automatically picks the target path based on context (consuming project with .claude/ versus AgentKit library root)
- Checks for collisions and refuses to overwrite existing files
- Validates that the description is trigger-shaped rather than a vague summary
- Fills the templates and reports which placeholder fields still need work
Limitations
- Relies on templates being available in templates/ or the AgentKit install path
- For Cursor rules, requires the user to supply the NN prefix and globs array themselves
- Only produces a skeleton; it does not guarantee the quality of the domain content
Use it when you need to quickly create a new skill, command, agent, or rule with a compliant structure and frontmatter.
Avoid it for editing or refactoring existing assets, since the skill halts on any path collision.
Security analysis
SafeThe skill only scaffolds new files in designated directories using Read, Write, Edit, Glob, and Bash. It explicitly prevents overwriting existing files and does not contain destructive, exfiltrating, or obfuscated commands. No meaningful execution risk.
No concerns found
How this analysis is madeExamples
/scaffold skill pdf-report-builder Use when the user asks to generate a PDF report from structured data/scaffold rule typescript-strict Use when writing or reviewing TypeScript files in this repo/scaffold agent backend-engineer Use when the user asks for help designing or reviewing backend servicesdescription: Scaffold a new skill, command, agent, or Cursor rule with correct frontmatter and location. argument-hint: <kind> <name> [description] allowed-tools: Bash, Read, Write, Edit, Glob
Scaffold a new AgentKit asset. Parse $ARGUMENTS as: <kind> <name> [description].
<kind>=skill|command|agent|rule|guideline<name>= kebab-case (my-skill,backend-engineer,go-service)[description]= optional one-liner; ask for it if missing
Where to create it
First determine context: are we inside an AgentKit checkout (has skills/, commands/,
agents/ at the root), or inside a consuming project with .claude/ installed?
| Context | Path |
| --- | --- |
| Consuming project (.claude/ present) | .claude/skills/<name>/SKILL.md etc. |
| AgentKit library root | skills/<name>/SKILL.md etc. |
Full dispatch table (consuming project):
| kind | Creates |
| --- | --- |
| skill | .claude/skills/<name>/SKILL.md |
| command | .claude/commands/<name>.md |
| agent | .claude/agents/<name>.md |
| rule | .cursor/rules/<NN>-<name>.mdc (ask for NN prefix) |
| guideline | shared/guidelines/<name>.md (AgentKit only) |
Before writing
- Check for collisions. If the target path exists, stop — don't overwrite.
- Validate the description. Must be trigger-shaped: "Use when the user asks to…". Reject summary-shaped descriptions like "Handles X-related tasks."
- For rules, ask for the
globsarray — don't guess the file pattern.
Use the template
Find the right template from templates/ (or from where AgentKit is installed):
- Skill →
SKILL.template.md - Command →
command.template.md - Agent →
agent.template.md - Rule →
rule.template.mdc
Fill every <placeholder>. Mark genuinely optional sections with <!-- TODO -->.
After creating
- Print what was created and what still needs filling in (the
<...>fields). - Remind the user:
- Description must be trigger-shaped or discovery won't work.
- No project-specific names, credentials, or internal URLs in assets meant to be reused.
- Reference
shared/guidelines/for security, multi-cloud, or document rules rather than duplicating them inline. - Keep the body under ~120 lines — it's loaded into context on every use.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/scaffold-an-agentkit-asset-ms8gxn6t/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/scaffold-an-agentkit-asset-ms8gxn6t' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/scaffold-an-agentkit-asset-ms8gxn6t/download' --output '.skill-downloads/scaffold-an-agentkit-asset-ms8gxn6t/SKILL.md.part' && mv '.skill-downloads/scaffold-an-agentkit-asset-ms8gxn6t/SKILL.md.part' '.skill-downloads/scaffold-an-agentkit-asset-ms8gxn6t/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash, Read, Write, Edit, Glob
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/scaffold-an-agentkit-asset-ms8gxn6t/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.