| name | universal-skill-creator |
| description | Create, adapt, validate, and optimize reusable agent skills across agentic platforms. |
| version | 1.0.0 |
| since | 2026-07-28 |
| last_modified | 2026-07-28 |
| authors | ["platform-engineering"] |
| stability | stable |
| min_platform_version | {"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"} |
| deprecated_since | null |
| replaces | null |
| supersedes | [] |
| changelog | [{"version":"1.0.0","date":"2026-07-28","change":"Initial generated production-ready SDLC / DevSecOps skill"}] |
Universal Skill Creator
Purpose
Create new production-ready skills and prevent generic copy-paste skills by enforcing full frontmatter, SemVer, dates, authors, stability, min_platform_version, changelog, domain-specific scope, checklist, decision rules, finding categories, severity guidance, outputs, acceptance criteria, anti-patterns, and no generic body reuse.
When to use
- A user asks to create or upgrade a skill.
- A skill body must be checked for generator smell or copy-paste generic content.
- Skill metadata, versioning, compatibility, or changelog rules need enforcement.
- A skill needs domain-specific review logic, not only name and description changes.
- The central agent routes to universal skill creation.
Operating model
- Identify the skill domain, users, trigger conditions, outputs, risks, and non-goals.
- Write domain-specific review scope, checklist, decisions, categories, severity, outputs, acceptance, and anti-patterns.
- Reject bodies that only differ by name, purpose, or generic operating text.
- Ensure frontmatter, body changelog, compatibility metadata, and versioning are consistent.
- Validate generated examples or tests that prove the skill is not generic.
Spec-Driven Change Context
- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.
- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal/design/tasks record before implementation begins.
- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.
- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.
- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.
- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.
- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal/spec/tasks outline instead of relying on chat-only intent.
Skill-Specific Review Scope
- YAML frontmatter, SemVer, since, last_modified, authors, stability, and min_platform_version.
- Body changelog, purpose, review scope, checklist, decision rules, and finding categories.
- Severity guidance, output requirements, acceptance criteria, and anti-patterns.
- Generic body reuse detection and platform compatibility honesty.
- Skill routing, generated copies, validation, and governance preservation.
