agentsclimarketplace

Codex chef operator

Skill ucsahinn/codex-chef/plugins/codex-chef-workflows/skills/codex-chef-operator

Codex Chef: Windows-first Codex setup kit with agents, skills, MCP connectors, safe installers, validation gates, and multilingual docs.

Install
npx -y skills add ucsahinn/codex-chef --skill codex-chef-operator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Maintain, audit, and improve Codex Chef setup repositories. Use for README/docs/template/catalog/installer/validation updates, release-readiness work, and safe Codex starter maintenance without weakening security, leaking local state, or changing external systems.

SKILL.md

2.5 KB, as published. Nobody here has run it

Codex Chef Operator

Use this skill when maintaining the Codex Chef repository or a derived local setup.

Reference Routing

Read references/repo-maintenance.md before broad setup, installer, README, catalog, docs, verification, release-readiness, or public-repo changes. Keep SKILL.md as the routing entry point and put detailed repo policy in that reference.

Workflow

  1. Inspect current files before changing anything.
  2. Preserve security defaults:
    • sandbox stays enabled
    • approvals stay interactive
    • authenticated connectors stay disabled until needed
    • no secrets, sessions, memories, auth files, or local project paths are added to source
  3. Keep docs and templates aligned:
    • AGENTS.md
    • README.md
    • README.tr.md
    • templates/codex/AGENTS.md
    • templates/codex/config.windows.toml
    • templates/codex/config.unix.toml
    • docs/how-to.md
    • docs/how-to.tr.md
    • docs/skills-and-agents.md
    • docs/skills-and-agents.tr.md
    • docs/mcp-catalog.md
    • docs/mcp-catalog.tr.md
    • docs/codex-flags.md
    • docs/codex-flags.tr.md
    • docs/public-readiness.md
    • docs/public-readiness.tr.md
    • docs/install.md
    • docs/install.tr.md
    • docs/security-model.md
    • every English operator doc in docs/ should have a matching .tr.md pair
    • the six root README entry points should route readers honestly to the complete English and Turkish operator docs
    • bundled local skills should stay reference-backed, zero-network unless their own script or workflow explicitly says otherwise, and validated by repo checks
    • public README visuals under assets/ should stay purposeful, accessible, lightly animated with reduced-motion fallback, and public-safe
  4. Validate after edits:
    • npm run validate
    • npm run validate:plugin-skills
    • git status --short
    • Gitleaks when available
  5. Do not commit, push, tag, release, deploy, publish, rotate credentials, or perform account-level changes unless the user explicitly approves the exact action.

Output

Report:

  • changed files
  • validation commands and status
  • remaining security or publishing risk

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.