ReddRadar
Topic: codex
8,457 skills in this topic.
-
with-context-agent
Use when testing valid context and agent configuration
agent-sh/agnix 169
-
with-hooks
Use when testing valid hooks
agent-sh/agnix 169
-
grid-ctf-ops
Operational knowledge for the grid_ctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging grid_ctf strategies.
greyhaven-ai/autocontext 729
-
autocontext
Iterative strategy generation and evaluation system. Use when the user wants to evaluate agent output quality, run improvement loops, queue tasks for background evaluation, check run status, or discover available scenarios. Provides LLM-based judging with rubric-driven scoring.
greyhaven-ai/autocontext 729
-
swe-af
Autonomous engineering team runtime — one API call spins up coordinated AI agents to scope, build, and ship software.
Agent-Field/SWE-AF 697
-
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
xintaofei/codeg 674
-
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
xintaofei/codeg 674
-
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
xintaofei/codeg 674
-
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
xintaofei/codeg 674
-
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
xintaofei/codeg 674
-
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
xintaofei/codeg 674
-
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
xintaofei/codeg 674
-
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
xintaofei/codeg 674
-
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
xintaofei/codeg 674
-
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
xintaofei/codeg 674
-
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
xintaofei/codeg 674
-
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
xintaofei/codeg 674
-
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
xintaofei/codeg 674
-
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
xintaofei/codeg 674
-
office-hours
MANUAL TRIGGER ONLY: invoke only when user types /office-hours. YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written.
slopus/happy 17,777
-
agent-browser
Browser automation CLI for AI agents. Use this when asked to test something in a real browser.
slopus/happy 17,777
-
terminal-emulator
Test interactive CLI/TUI applications using @microsoft/tui-test. Use when you need to test CLI tools with interactive prompts, TUI rendering, arrow key navigation, or any command that requires a TTY. Triggers include "test CLI", "test TUI", "run interactively", "automate terminal input", "simulate user input in terminal".
slopus/happy 17,777
-
happier-session-control
Manage Happier sessions (list/status/send/wait/history/stop + execution runs) via the happier CLI JSON contract.
happier-dev/happier 649
-
happier-github-ops
Run GitHub CLI commands as the Happier bot account via `yarn ghops` (forced PAT auth + non-interactive).
happier-dev/happier 649