# Create Better AI Skills

Building reusable AI skills can be inconsistent without clear structure. This skill guides Claude, Codex, and Claude Code through design, scaffolding, validation, and packaging.

## Install

```bash
npx skillstore add vercel-labs/skill-creator
```

## Metadata

- Status: approved
- Slug: vercel-labs-skill-creator
- Skillstore revision: r1
- Version status: missing
- Tree hash: 18757149acf262d80413963389a8834580328eb6238c2f7ac6acd0c617b5bed7
- Author: vercel-labs
- GitHub username: vercel-labs
- License: Complete terms in LICENSE.txt
- Repository: https://github.com/vercel-labs/agent-browser/tree/main/skills/skill-creator/
- Ref: 36e07d5e13068e5be64447e8f20b427cf2cbd21a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 81
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/vercel-labs-skill-creator
- Manifest: https://skillstore.pages.dev/api/skills/vercel-labs-skill-creator/manifest

## Capabilities

- Explains the required SKILL.md structure and optional resource folders.
- Guides planning from user examples into reusable scripts, references, and assets.
- Provides init\_skill.py to scaffold a starter skill folder with placeholders.
- Provides quick\_validate.py to check frontmatter, naming, and description rules.
- Provides package\_skill.py to validate and create a .skill archive.
- Includes reference guides for workflow structure and output patterns.

## Use Cases

- Create a New Skill: Plan the skill purpose, choose resource folders, scaffold the project, and replace placeholders with focused guidance.
- Improve an Existing Skill: Review SKILL.md, split long guidance into references, and align bundled resources with real user workflows.
- Prepare a Skill Package: Run validation, fix frontmatter and naming issues, then create a distributable .skill archive.

## Prompt Templates

### Start a Skill

```
Help me design a new skill for [task]. Ask only the most important questions, then propose the SKILL.md structure and resource folders.
```

### Plan Resources

```
Given these example user requests, identify which scripts, references, and assets this skill should include. Keep SKILL.md concise.
```

### Scaffold and Validate

```
Use this skill to scaffold a skill named [name] in [path]. Then list which placeholder files I should edit or delete.
```

### Review for Release

```
Review the skill at [path]. Check SKILL.md, bundled resources, validation results, packaging readiness, and marketplace risks.
```

## Limitations

- The scaffold contains placeholders that authors must replace or delete.
- Validation is basic and does not replace a full security review.
- Scripts write local files and should run only in intended directories.
- It does not supply domain expertise for every new skill idea.

## Best Practices

- Start from concrete user examples before writing the skill body.
- Keep SKILL.md focused and move detailed material into references.
- Validate scripts and packaging before sharing the skill.

## Anti Patterns

- Leaving generated placeholder files in the final skill.
- Putting broad background material in SKILL.md when a reference file is better.
- Packaging a skill before checking frontmatter, naming, and resource relevance.

## Security Audit

- Audited at: 2026-07-07T06:58:15.74\+00:00
- Summary: Reviewed all 50 static findings and found they are benign uses of markdown, template text, archive creation, and validation logic. No evidence found of prompt injection, data exfiltration, unauthorized network access, or malicious command execution.

## Stats

- Views: 298
- Downloads: 27
- Favorites: 1
- Popularity score: 0