- Home
- Skills
- Gentleman Programming
- Gentleman.Dots
- Skill Creator
skill-creator_skill
- Shell
1.3k
GitHub Stars
1
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 gentleman-programming/gentleman.dots --skill skill-creator- SKILL.md4.2 KB
Overview
This skill helps create new AI agent skills following a clear project spec and naming conventions. It guides when to create a skill, how to structure files and assets, and what mandatory metadata to include. The outcome is consistent, discoverable skills that encode reusable patterns and project-specific rules.
How this skill works
It inspects recurring patterns, project conventions, and complex workflows to generate a new skill scaffold with required frontmatter and minimal examples. It advises whether to include code templates or local documentation links and provides a checklist to validate the new skill before registering it. The result is a concise, rule-driven skill file plus optional assets and local references.
When to use it
- A pattern repeats and the AI needs explicit guidance or constraints
- Project conventions differ from generic best practices
- Workflows require step-by-step instructions or decision trees
- You need to provide reusable code templates, schemas, or configs
- You want to encode decision logic for choosing approaches
Best practices
- Start with the most critical patterns the AI must follow
- Keep examples minimal, focused, and copy-paste ready
- Place code templates and JSON schemas in assets/ when needed
- Point to local documentation in references/ rather than external URLs
- Ensure frontmatter includes name, description with trigger, author, license, and version
Example use cases
- Create a skill that standardizes test runner setup and common commands
- Add a project-specific formatting and linting skill with config templates
- Document a multi-step deployment workflow with decision tables
- Provide JSON schemas and example configs for configuration-heavy components
- Encode naming conventions and registration checklist for new skills
FAQ
Put code templates, schemas, and example configs in assets/. Use references/ to link to local documentation files only.
What frontmatter fields are mandatory?
Include name (lowercase hyphenated), description with trigger, license (Apache-2.0), metadata.author, and metadata.version.