universal-skill-creator

name	universal-skill-creator
description	Create, adapt, validate, and optimize reusable agent skills across agentic platforms.
version	1.2.0
since	2026-06-10
last_modified	2026-06-10
authors	["platform-engineering"]
stability	stable
min_platform_version	{"codex":"unknown","claude-code":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","windsurf":"unknown","ollama":"unknown"}
deprecated_since	null
replaces	null
supersedes	[]
changelog	[{"version":"1.2.0","date":"2026-06-10","change":"Added production-ready skill-specific operating model, checklist, decision rules, acceptance criteria, and output requirements"},{"version":"1.1.1","date":"2026-06-10","change":"Explicitly require applying the versioning schema while creating every new skill"},{"version":"1.1.0","date":"2026-06-10","change":"Mandatory versioning schema for generated skills: full YAML frontmatter, stability, min_platform_version, changelog"},{"version":"1.0.0","date":"2025-01-01","change":"Initial release"}]

Universal Skill Creator

Purpose

Create, adapt, validate, and optimize reusable agent skills across agentic platforms.

When to use

Use this skill when the task matches the description above or when the central agent instructions route work to $universal-skill-creator.

Operating model

1. Clarify the goal and constraints.
2. Inspect the minimum relevant repository context.
3. Produce a concise execution plan for non-trivial work.
4. Execute with tools when implementation is requested.
5. Validate the result with repository-native checks.
6. Summarize changed files, validation results, and residual risks.

DevSecOps guardrails

• Do not read secrets, .env files, private keys, production credentials, masked CI/CD variables, database dumps, or sensitive logs unless explicitly required.
• Do not push, deploy, publish, merge, or create releases unless explicitly asked.
• Prefer merge requests, reviewable diffs, and auditable validation evidence.
• Prefer least privilege, minimal changes, and explicit rollback notes.
• Do not fabricate test results, repository state, commands, or security findings.

Skill-Specific Operating Model

• Clarify skill domain, target users, triggering conditions, supported platforms, and governance level before drafting.
• Design skills around repeatable decisions and concrete checks, not generic role descriptions.
• Apply the mandatory versioning schema before finalizing every new or updated skill.

Skill-Specific Checklist

• Metadata includes complete YAML frontmatter, SemVer, stability, authors, dates, platform map, and changelog.
• Content includes domain-specific operating model, checklist, decision rules, acceptance criteria, and output requirements.
• Routing, platform-copy behavior, governance, security review, and validation expectations are explicit.

Decision Rules

• Never create a new skill that only differs by name and description. Every generated skill must contain domain-specific checklists, decision rules, acceptance criteria, and output requirements.
• Do not invent platform minimum versions; use unknown when not verified and document the production routing risk.
• Bump the skill version when instructions, operating model, guardrails, or required outputs change materially.

Acceptance Criteria

• A generated skill can guide real work in its domain without placeholder text.
• Frontmatter changelog and body changelog agree on the latest version.