Manage Yandex Tracker spaces through the REST API. Use when Codex needs to work with any documented Tracker API function: issues, issue filters, checklists, comments, attachments, bulk operations, fields, projects, portfolios, goals, queues, automation, boards, dashboards, components, issue types, statuses…
Stop the active Loop in this Codex CLI session — stop re-arming clock.sleep and close out the turn the loop was running in. Use ONLY when the user explicitly asks to stop, end, kill, or cancel the loop. Never invoke this on your own initiative while a loop is running.
Inspect Skill Manager's locally installed Claude Code, Codex, Muse, or Grok skills before non-trivial work, report the smallest clearly relevant set already active, temporarily activate relevant inactive skills, load all selected instructions, and clean up any receipt it creates before finishing. Use at the start of…
Use for bounded native Codex multi-agent orchestration when a task has at least two independent workstreams or independent verification would materially improve confidence: broad or high-risk multi-step work, audits, migrations, multi-area review-and-fix, adversarial verification, cross-checked research, or explicit…
A routing suite that chooses a working mode for a coding-agent session based on the first request. It supports modes for detailed specification work, fast implementation work, or uncertain cases, with status checks and one-off subprocess modes.
Runs a systematic debugging workflow for bugs, regressions, flaky behavior, and performance surprises. Use when something is broken, failing, throwing, slow, flaky, or when the user asks to debug or diagnose a specific problem.
A delivery workflow for Android APK files, the installable packages used to distribute Android apps. It reads the app version, gives the file a dated name, and copies it to a local network SMB share, a shared folder protocol.
Autonomously choose the smallest suitable reasoning effort for each task, lowering effort for simple or low-risk work and raising it when ambiguity, risk, stakes, or repeated failures warrant deeper reasoning. Use as a broad implicit runtime policy for all Codex tasks, especially when reasoning effort could otherwise…
Use when reviewing a pull request or branch diff with fixed perspectives and unified findings. Orchestrates code-reviewer, silent-failure-hunter, pr-test-analyzer, comment-analyzer, type-design-analyzer, and code-simplifier viewpoints.
🧩 Codex Skill — Refresh Codex CLI auth.json from ChatGPT. Skipphone verification, no overseas number needed. For users behind firewalls, in WSL, or remote desktop.
Use when the user wants to keep an open triage console for a software project - capturing bugs/change-requests as structured tickets, scoring them, and routing them to the right AI provider/sub-agent for an immediate fix or into the project's task management. Cloud-ready: works across multiple machines sharing a…
Guidelines for designing command-line tools that both people and coding agents can use reliably. A command-line tool is a program operated through typed commands in a terminal.
Diagnose OpenAI Codex CLI, Desktop, IDE, skill, plugin, MCP, session, configuration, authentication, network, storage, and performance problems using a local-first evidence workflow. Use when Codex is failing, slow, stuck, reconnecting, losing sessions, or behaving unexpectedly; do not use it to perform unrequested…
Build high-quality /goal commands for OpenAI Codex CLI 0.128+ that maximize audit-friendliness and minimize false-completion. Use this skill whenever the user wants to write, draft, generate, improve, or refine a /goal prompt — even if they don't say "skill" — including phrases like "help me write a goal", "design a…
Export the active Codex CLI session to a file in a TUI-style transcript format. Use when Codex needs to save the current session, reconstruct the visible terminal conversation, capture user prompts plus assistant messages plus tool activity, or write a current-session transcript to a user-specified path resolved from…
Review a Codex, Claude Code, or agent skill/plugin before public release. Use when the user wants to assess trigger quality, folder structure, documentation, validation gaps, GitHub readiness, or OSS release quality for an agent extension.
Use when a software project needs durable cross-session governance for formal documents, WBS or tracker coordination, worktree delivery boundaries, evidence and acceptance states, handoffs, or architecture and design-document control.
Use when the user invokes $windows-appshot or asks to create a Windows appshot bundle, including foreground-window screenshots, UI Automation text, metadata.json, prompt.md, or appshots generated by scripts/New-Appshot.ps1.
A tool for turning a talk, lesson, or product demonstration into an interactive HTML, CSS, and JavaScript slide deck with a storyboard, presenter notes, and rehearsal cues.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: