skill-creator

Creates new AI agent skills following the Agent Skills specification.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Balthael/ciberbal-ai --skill skill-creator-balthael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Balthael/ciberbal-ai/tree/main/internal/assets/skills/skill-creator
Command: npx skills add https://github.com/Balthael/ciberbal-ai --skill skill-creator-balthael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams repeatedly explain the same conventions and workflows to AI agents, and ad-hoc instructions produce inconsistent results. This Skill provides a standardized process for authoring reusable SKILL.md files so agent guidance is structured, discoverable, and consistent. ## Core Features & Use Cases - Standardized Skill Authoring: Provides a complete SKILL.md template with required frontmatter fields (name, description, license, metadata) and content guidelines. - Naming and Structure Conventions: Defines naming patterns for generic, project-specific, testing, and workflow skills, plus rules for when to use assets/ versus references/ directories. - Quality Checklist: Includes a pre-creation checklist covering duplication checks, trigger keywords, minimal examples, and AGENTS.md registration. - Use Case: When your team notices the AI repeatedly mishandles a project-specific testing pattern, use this Skill to create a myapp-test-api skill with proper frontmatter, critical patterns, and commands, then register it in AGENTS.md. ## Quick Start Ask the agent to create a new skill for your project's API conventions following the skill-creator template and naming conventions.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new skill for an AI agent?

Create a directory under skills/ with a SKILL.md file containing YAML frontmatter (name, description, license, metadata) followed by usage instructions. Follow the naming conventions and register the skill in AGENTS.md.

What frontmatter fields are required in SKILL.md?

SKILL.md requires name (lowercase with hyphens), description (what plus trigger), license (Apache-2.0), and metadata with author and semantic version. The description should include trigger keywords so the agent knows when to load the skill.

When should I use assets versus references in a skill?

Use assets/ for code templates, JSON schemas, and example configs. Use references/ for links to local documentation files. References should point to local paths, not web URLs.

When should I not create a skill?

Skip skill creation when documentation already exists (create a reference instead), when the pattern is trivial or self-explanatory, or when it is a one-off task that will not be reused.

How do I name a project-specific skill?

Use the pattern {project}-{component} for project-specific skills, {project}-test-{component} for testing skills, and {action}-{target} for workflow skills. Generic technology skills just use the technology name like pytest or typescript.