Codex Skills Library
Codex Skills Library is the durable source repository for Maggie Lerman's custom Codex skills, custom local plugin backups, generated skill catalogs, and the public docs site that explains the workflows. The repo turns local agent behavior into portable, inspectable artifacts: each skill folder carries trigger metadata, instructions, references, scripts, examples, assets, and validation expectations, while the catalog tooling keeps the public docs aligned with the suite allowlist.
Narrative
Portable Workflows As Source Code
Codex Skills Library turns repeatable agent behavior into source-controlled folders rather than loose prompts or chat memory. The project keeps each skill portable with trigger metadata, instructions, references, scripts, examples, assets, and agent metadata, then uses generated catalogs to make the suite inspectable. The important decision is operational: workflows should be reusable and reviewable, but still checked inside the target repository where local instructions, constraints, and verification commands matter.
Catalog Discipline And Human Review
The repository separates skill membership, lifecycle metadata, generated catalog output, plugin backups, and public docs-site pages. Catalog scripts detect drift before regeneration, while the maintainer decides whether a local skill belongs in the curated suite or should stay outside the public catalog. That distinction matters because the repo is public-learning-oriented but still preserves provenance-sensitive skill folders, third-party notices, local plugin backups, and unresolved license boundaries.
Current Intake Boundary
This intake records the repo locally as a Hyphenomenon project without mutating the production knowledge database. The captured state includes a local docs-site review, source-backed hydration artifacts, and an explicit drift finding: an in-progress hyphenomenon-chat-intake skill folder exists outside skills/SUITE_SKILLS.txt. That is useful proof of the real operating model because the project depends on human/operator review before deciding whether local skill work becomes curated public catalog content.
System design
System surfaces
Skill Source Library
`skills/` contains portable custom Codex skill folders, with suite membership governed by `skills/SUITE_SKILLS.txt` and lifecycle metadata tracked separately.
Plugin Backup Library
`plugins/` preserves selected custom local plugin bundles separately from the standalone skill suite so larger surfaces keep plugin metadata, assets, scripts, and bundled skills intact.
Generated Public Docs Site
`docs-site/` is a Next.js catalog and documentation surface generated from source metadata so readers can browse skills and plugin patterns without hand-maintained marketing pages.
Repo-Native Evidence And Project Memory
`DOCS/` stores lean notes, project memory, evidence, and intake artifacts for repository maintenance without turning the repo into a full delivery scaffold.
Implementation stack
Skill And Plugin Artifacts
- • Codex SKILL.md folders
- • agent metadata YAML
- • reference files
- • bundled scripts
- • plugin.json metadata
- • repo-local plugin registry
Catalog Tooling
- • Python catalog builder
- • suite allowlist
- • suite lifecycle metadata
- • generated Markdown index
- • generated JSON manifest
- • generated TypeScript docs-site catalog
Docs Site Runtime
- • Next.js 16
- • React 19
- • TypeScript
- • Tailwind CSS
- • shadcn/base-ui
- • lucide-react
Verification
- • python3 scripts/build_catalog.py --check
- • python3 scripts/build_catalog.py
- • python3 scripts/build_docs_site_catalog.py
- • docs-site npm run build
- • local browser screenshots
Artifacts
Plugin Backup Model
Custom local plugin bundles stay in `plugins/` with plugin metadata and registry records so larger workflow surfaces are preserved without pretending they are ordinary standalone skills.
Skill Suite Catalog Model
The source suite maps portable skill folders through an allowlist and lifecycle metadata into generated Markdown, JSON, and TypeScript catalog surfaces.
Codex Skills sync and catalog governance
How local skill or plugin changes become durable repository artifacts: inspect the repo instructions, compare local skill homes to the allowlisted suite, decide whether new local work belongs in the curated catalog, regenerate source-backed indexes, review docs-site output, and record drift or blockers before publishing or handoff.
Codex Skills Library Intake Dossier
Codex Skills Library is the durable source repository for Maggie Lerman's custom Codex skills, custom local plugin backups, generated skill catalogs, and the public docs site that explains the workflows. The repo turns local agent behavior into portable, inspectable artifacts: each skill folder carries trigger metadata, instructions, references, scripts, examples, assets, and validation expectations, while the catalog tooling keeps the public docs aligned with the suite allowlist.
README
Source Summary Maggie Lerman Codex Skills Site This is the public marketing and documentation site for Maggie Lerman's Codex skills library. It is intentiona...
AGENTS
Source Summary Repository Guidance This repository stores portable custom Codex skills, backups of custom local plugins, and the docs/scripts that maintain b...
plugin
Source Summary { "name": "context-layer", "version": "0. 1. Imported Context { "name": "context-layer", "version": "0.1.0", "description": "Skill package for...
01-home
Source Summary © MasgieLeman by Googe Soper CODEX SKILLS LIBRARY PUBLIC CODEX SKILLS LIBRARY CURRENT Focus r WwW Nn Co . Maggie Lerman y Buildingin public I]...
Visual evidence
Key dates
Git history shows the repository began with `Initial codex skills suite repository`, then quickly narrowed to an allowlisted custom skill suite with explicit lifecycle metadata.
Git history records the addition of the customer docs site and catalog guardrails, followed by Vercel monorepo settings and a calmer public docs design.
Git history records a skills sync workflow repair, aligning with the durable convention that local Codex skills are reconciled into this repository through explicit checks.
This local-only intake created source-backed project artifacts and applied them only to the non-production Hyphenomenon knowledge backbone.