codex-missing-assets-dir

Validate SKILL.md frontmatter and asset directories for skill units.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/poisontr33s/chthonic-archive --skill codex-missing-assets-dir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-missing-assets-dir
Source: https://github.com/poisontr33s/chthonic-archive/tree/main/codex/mailbox/archive/2026_02_10_meta_cleanup/.tmp_fixture_eval/codex_missing_assets_dir
Command: npx skills add https://github.com/poisontr33s/chthonic-archive --skill codex-missing-assets-dir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex skill units often rely on accompanying assets to function correctly. This fixture demonstrates a minimal skill that requires an assets directory to be present and recognized during discovery and activation.

Core Features & Use Cases

  • Validates frontmatter presence (name, description) and optional asset references.
  • Serves as a test fixture for asset loading, discovery, and error handling in the skill system.
  • Useful for CI pipelines to verify that missing assets are surfaced early.

Quick Start

Place the assets in an assets/ directory next to SKILL.md and run the validator to verify discovery.

Frequently Asked Questions about codex-missing-assets-dir

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

FAQPage Schema
How do I validate YAML frontmatter in SKILL.md files?

To validate YAML frontmatter in SKILL.md files, this skill checks for mandatory name and description fields, captures metadata like category and keywords, and returns a structured payload confirming discovery.

How do I verify required assets and dependencies exist for codex skills?

You verify required assets and dependencies for codex skills by running a discovery process that checks root-level SKILL.md files alongside optional sibling directories to ensure all referenced assets are present.

What is the best way to catch missing skill assets early in a CI pipeline?

The best way to catch missing skill assets early in a CI pipeline is using a validation fixture that enforces YAML frontmatter presence and checks sibling directories, surfacing missing assets during automated discovery.

Can I use this validation fixture to check optional sibling directories?

Yes, you can use this validation fixture to check optional sibling directories; it scopes discovery to root-level SKILL.md files and adjacent folders to verify metadata, component availability, and asset dependencies.

Why does my skill discovery fail when the assets directory is missing?

Skill discovery fails when the assets directory is missing because codex skill units rely on accompanying assets to function, and the validator surfaces these missing directories early to prevent activation errors.