conventions-codex

Enforces Codex CLI artifact layout, manifests, and hook conventions for Tier 2-Codex scoring.

111|29|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/xiaolai/nlpm --skill conventions-codex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventions-codex
Source: https://github.com/xiaolai/nlpm/tree/main/codex/skills/conventions-codex
Command: npx skills add https://github.com/xiaolai/nlpm --skill conventions-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents inconsistent, tool-specific Codex CLI artifacts from being silently accepted by catching schema, layout, manifest, and hook/agents mismatches before they impact behavior.

Core Features & Use Cases

  • Codex CLI artifact layout guidance: Clarifies the separation between the cross-tool .agents/ surface and Codex-private .codex/ surface.
  • Marketplace + plugin manifest expectations: Documents required .codex-plugin/plugin.json fields and optional Codex components plus the .agents/plugins/marketplace.json structure.
  • Hook and memory conventions: Defines Codex hook event expectations and the hierarchical AGENTS.md reading order so scoring/checking matches real runtime behavior.
  • Tier-aware scoring overlay: Applies Codex-specific rules when an artifact is classified as Tier 2-Codex, while respecting a universal base via nlpm:conventions.

Quick Start

Ask an assistant to score your repository’s Codex CLI artifacts using nlpm:check so it flags layout, manifest, and hook/agents convention issues against Codex’s documented conventions.

Frequently Asked Questions about conventions-codex

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

FAQPage Schema
How do I validate Codex CLI artifacts in my repository?

Validating Codex CLI artifacts involves checking the `.agents/` and `.codex/` directory separation, required manifests, and hook conventions. You can use an assistant to score your repository's artifacts with `nlpm:check` to flag layout, manifest, and hook issues against documented conventions.

What is the correct directory layout for Codex plugins and marketplace entries?

The correct Codex layout separates cross-tool surfaces in `.agents/` from Codex-private files in `.codex/`. Specifically, Codex plugins require a `.codex-plugin/plugin.json` manifest, while marketplace entries use the `.agents/plugins/marketplace.json` structure to ensure proper tool-specific validation.

How do Codex hooks and AGENTS.md conventions work together?

Codex hooks and AGENTS.md conventions work together by defining hook event expectations in `.codex/hooks.json` and establishing a hierarchical reading order for AGENTS.md files. This ensures scoring and checking matches real runtime behavior across the repository.

Do I need specific configuration files for Tier 2-Codex artifact validation?

Yes, Tier 2-Codex artifact validation requires Codex-specific checks for `.codex-plugin/plugin.json`, `.codex/config.toml`, and `.codex/hooks.json` or inline hooks. It applies tier-aware scoring overlays while respecting a universal base via `nlpm:conventions`.

Why are my Codex CLI artifacts being silently accepted with schema mismatches?

Codex CLI artifacts are silently accepted when schema, layout, manifest, and hook mismatches go unchecked. Scoring with `nlpm:check` catches these mismatches before they impact behavior by enforcing Codex hook event contracts and hierarchical AGENTS.md expectations.

Can I include an optional skill sidecar with my Codex CLI configuration?

Yes, you can include an optional skill sidecar file at `agents/openai.yaml` alongside your Codex CLI configuration. This is validated alongside required manifests like `.codex-plugin/plugin.json` and `.agents/plugins/marketplace.json` during the artifact scoring process.