- Home
- Skills
- Gpolanco
- Skills As Context
- Skill Creator
skill-creator_skill
- Shell
0
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill gpolanco/skills-as-context --skill skill-creator- .DS_Store8.0 KB
- SKILL.md5.4 KB
Overview
This skill creates high-quality, reusable AI skills using local standards and templates. It enforces strict design rules: one skill per job, reuse checks, and progressive disclosure. It is opinionated and tailored for personal projects and developer workflows.
How this skill works
The skill inspects a request and validates that the proposed pattern appears at least three times and has a single responsibility. It scaffolds a standardized skill folder, populates core documentation from the local template, and adds reference and assets folders. For tool or hybrid skills it also creates scripts and runs a mandatory quality gate that checks documentation size and forbids external references.
When to use it
- When a pattern repeats three or more times and should be packaged as a reusable capability.
- When you need explicit guardrails and deterministic behavior for an agent task.
- When you want to standardize a recurring workflow or rule set across projects.
- When a request is deterministic enough to automate or document as a skill.
- Do not use for one-off tasks or when existing documentation already covers the need.
Best practices
- Enforce reusability: confirm three or more concrete uses before creating a skill.
- Keep scope tight: design one skill to solve one job; split if responsibilities mix.
- Use progressive disclosure: keep surface docs short and move deep details to reference.
- Request the minimum tool permissions required (Read, Write, Bash as needed).
- Cross-reference existing skills instead of duplicating their behavior or rules.
Example use cases
- Package a repeated formatter workflow used across multiple projects into a tool skill.
- Create a knowledge skill that codifies API contract rules referenced by several teams.
- Standardize an onboarding checklist into a reusable hybrid skill with automation scripts.
- Split a monolithic policy+framework guide into two focused skills following the hard split rule.
- Scaffold a new agent capability that must pass local quality checks before activation.
FAQ
Reject skill creation; instead produce a small snippet or checklist until reuse reaches three instances.
How do you decide skill type?
If it only teaches rules it's knowledge; if it automates deterministic tasks it's a tool; if it both teaches and automates it's hybrid.