Codex Skill Development
Compose official $skill-creator with this repository's release gates. Do not
copy, replace, or shadow the official system skill.
Author
- Read
$skill-creator completely and follow its creation or update workflow.
- Choose a unique, lower-hyphen skill name. Check repository, user, system, and
plugin skill names before adding it.
- Keep
SKILL.md concise. Move detailed reference material into files that
SKILL.md links directly.
- Add
agents/openai.yaml with quoted strings, a 25-64 character
short_description, and a one-sentence default_prompt that names the skill
as $skill-name.
- Bundle every required local runtime file. If an external runtime or tool is
required, state installation and availability checks explicitly. Never ship
instructions that reference absent paths.
- Keep scripts deterministic and testable. Prefer Rust for repository tooling;
use an existing official helper in its native language when it is the
authoritative validator or generator.
- Preserve portable licensing. Third-party-derived skill directories must
carry required license and notice files, and root notices must identify them.
- Update every caller, guide, default prompt, and relative link when renaming a
skill.
Validate
Run repository gate from repository root:
cargo run --manifest-path gates/rust/Cargo.toml -p skill-metadata-check -- \
--skills-dir skills --plugin-manifest .codex-plugin/plugin.json
Then:
- Run official
quick_validate.py from installed system $skill-creator
against each changed skill. This official Python helper is retained because
it is Codex's authoritative compatibility check; repository automation stays
Rust-first.
- Run relevant script tests, repository tests, and
git diff --check.
- Resolve all local Markdown links and verify each referenced runtime file
exists inside the installable skill package.
- Search changed content for stale Claude-only names, paths, tools, settings,
hooks, and invocation syntax.
- Install from the exact candidate revision into an isolated destination or a
collision-free user skill path, then validate installed bytes and metadata.
Finish
Report skill name, trigger boundary, runtime dependencies, validation evidence,
install result, and retained or replaced colliding installations.
1---2name: codex-skill-development3description: Create or update skills in the decebal-codex-skills repository using official Codex skill authoring plus repository metadata, portability, licensing, validation, and installability gates. Use for work under this repository's skills directory; use official system skill-creator directly for unrelated personal skills.4metadata:5 source: https://skillmd.com/skills/decebal/codex-skill-development6---78# Codex Skill Development910Compose official `$skill-creator` with this repository's release gates. Do not11copy, replace, or shadow the official system skill.1213## Author14151. Read `$skill-creator` completely and follow its creation or update workflow.162. Choose a unique, lower-hyphen skill name. Check repository, user, system, and17 plugin skill names before adding it.183. Keep `SKILL.md` concise. Move detailed reference material into files that19 `SKILL.md` links directly.204. Add `agents/openai.yaml` with quoted strings, a 25-64 character21 `short_description`, and a one-sentence `default_prompt` that names the skill22 as `$skill-name`.235. Bundle every required local runtime file. If an external runtime or tool is24 required, state installation and availability checks explicitly. Never ship25 instructions that reference absent paths.266. Keep scripts deterministic and testable. Prefer Rust for repository tooling;27 use an existing official helper in its native language when it is the28 authoritative validator or generator.297. Preserve portable licensing. Third-party-derived skill directories must30 carry required license and notice files, and root notices must identify them.318. Update every caller, guide, default prompt, and relative link when renaming a32 skill.3334## Validate3536Run repository gate from repository root:3738```bash39cargo run --manifest-path gates/rust/Cargo.toml -p skill-metadata-check -- \40 --skills-dir skills --plugin-manifest .codex-plugin/plugin.json41```4243Then:44451. Run official `quick_validate.py` from installed system `$skill-creator`46 against each changed skill. This official Python helper is retained because47 it is Codex's authoritative compatibility check; repository automation stays48 Rust-first.492. Run relevant script tests, repository tests, and `git diff --check`.503. Resolve all local Markdown links and verify each referenced runtime file51 exists inside the installable skill package.524. Search changed content for stale Claude-only names, paths, tools, settings,53 hooks, and invocation syntax.545. Install from the exact candidate revision into an isolated destination or a55 collision-free user skill path, then validate installed bytes and metadata.5657## Finish5859Report skill name, trigger boundary, runtime dependencies, validation evidence,60install result, and retained or replaced colliding installations.