Our review
This skill is a demonstration example showing the full directory structure for Codex skills, including scripts, references, assets, and examples.
Strengths
- Clear and well-organized structure
- Easy to follow for beginners
- Includes all necessary components
- Serves as a reproducible template
Limitations
- Performs no practical task
- Purely demonstrative
- Requires adapting references to your own project
When you want to learn or teach the standard structure of a Codex skill.
When you need a ready-to-use skill for a specific task.
Security analysis
SafeThis is a harmless example skill describing directory structure with no executable code or dangerous instructions.
No concerns found
Examples
Use the example-skill structure to create a new skill for generating project documentation. Include scripts, references, assets, and examples folders.Show me how to structure a Codex skill using the example-skill as a reference. Explain each folder (scripts, references, assets, examples) and what they contain.Run the validate.sh script from the example-skill to check if my skill directory follows the correct structure.name: example-skill description: Example skill demonstrating the full skill directory structure with scripts, references, assets, and examples. Use when learning how to structure Codex skills.
Example Skill
This is a demonstration skill showing all possible subdirectories.
Quick Start
- Check
references/patterns.mdfor detailed patterns - Use
assets/component-template.tsxas a starter - Run
scripts/validate.shto check your code - See
examples/good-example.tsxfor reference
Structure
scripts/- Executable automation scriptsreferences/- Detailed documentationassets/- Templates and resourcesexamples/- Real code examples
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Typed Documentation Forms System
Documentation
Add typed comments, documentation, todos, and metadata to Scheme code using `(doc ...)` forms. Doc annotations are authoritative for type inference, extracted by search commands (lf-todo, lf-types), and integrated with the type checker and LSP. Useful for annotating functions, marking deprecations, or tracking localized improvements alongside the code.