agents2agentsai
22 verified skills1,518 total stars
babysit-pr
Babysit a GitHub pull request after creation by continuously polling CI checks/workflow runs, new review comments, and mergeability state until the PR is ready to merge (or merged/closed). Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and stop only when user help is required (for example CI infrastructure issues, exhausted flaky retries, or ambiguous/blocking situations). Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
development69
hn-discoverer
INTERNAL SUBAGENT SKILL — never invoke directly. This is called automatically by $hn-synthesis to discover relevant HN threads. If a user asks about HN discussions, use $hn-synthesis instead.
data-ai69
job-manager
Create, manage, and monitor scheduled jobs. Use when a user wants to run something on a schedule (e.g., 'run this every 2 hours', 'set up a daily digest', 'create a cron job for...'), check job status, view run history, or manage the scheduler daemon. This skill covers the full job lifecycle: creation, scheduling, monitoring, and cleanup.
testing69
kb
Knowledge Base operations for card-based research knowledge management. Use when reading, writing, searching, updating, resetting, or managing KB cards and files. Also handles "reset KB", "clear KB", and "wipe KB" — immediately resets to empty state without asking questions. Other research skills reference this skill via $kb for KB operations.
content-media69
openai-docs
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or explicit GPT-5.4 upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains.
tools69
paper-discovery
Discover and rank papers for a research topic. Use when a user asks a research question, wants to find papers, or asks how something is done in the literature.
research69
paper-synthesis
REQUIRED for any paper explanation or synthesis. Do NOT call attach_url_files and summarize inline — always use this skill. Use when given an arXiv URL, DOI, paper title, or Zotero reference.
research69
zotero
Zotero library management through the `ata zotero ...` CLI namespace. Use when the user mentions Zotero, their library, a collection, group libraries, or "my papers", and you need to search, inspect, organize, import, or update Zotero records without exposing the large native Zotero tool family.
tools69
test-tui
Guide for testing Codex TUI interactively
development69
paper-synthesizer
Subagent skill for paper synthesis. Spawned by $paper-synthesis to fetch and extract information from a single paper.
development69
cross-paper-report
Generate integrated cross-paper explanations from KB cards. Use when a user asks to explain, compare, synthesize, understand, or deep-dive into one or more knowledge base cards, or asks how cards relate or work together.
data-ai69
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
tools69
workspace
Multi-repo workspace management: clone repos, create execution runs, track papers/datasets/artifacts, manage snapshots, and review audit logs. Use when the user wants to organize multi-repo work, run experiments in sandboxes, or track research resources.
testing69
hn-synthesis
Search Hacker News for practitioner discussions on a topic, tool, library, or paper, and synthesize findings into structured KB cards. Use when a user asks about community sentiment, real-world experience, practitioner opinions, or HN discussions about a technology, project, or research paper.
tools69
research-briefing
Generate a concise research briefing from KB cards or a topic. Use when a user wants a quick overview, orientation, summary of approaches, or wants to understand what their options are before diving deep. Use instead of cross-paper-report when the user wants brevity over depth. Examples -- "give me a quick overview of VLA approaches", "what are my options for sim-to-real", "summarize what I have on diffusion policies", "brief me on action tokenization methods".
testing69
slides
Build, edit, render, import, and export presentation decks with the preloaded @oai/artifact-tool JavaScript surface through the artifacts tool.
tools69
spreadsheets
Build, edit, recalculate, import, and export spreadsheet workbooks with the preloaded @oai/artifact-tool JavaScript surface through the artifacts tool.
tools69
hn-synthesizer
INTERNAL SUBAGENT SKILL — never invoke directly. This is called automatically by $hn-synthesis when it spawns a thread-analysis subagent. If a user asks about HN discussions, use $hn-synthesis instead.
data-ai69
paper-discoverer
INTERNAL SUBAGENT SKILL — never invoke directly. Spawned by $paper-discovery to search, deduplicate, cluster, and rank papers for a research topic.
data-ai69
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
development69
adapt-environment
Adapt code to work with a GPU node's installed environment. Use when an experiment fails due to dependency version mismatches, import errors, missing packages, or API incompatibilities between the code's expected environment and what's actually installed on the GPU node. Triggered by errors like 'ModuleNotFoundError', 'ImportError', version conflicts, or when the user says 'adapt this code to the environment'.
development69
conversation-report
Generate a focused report from the current conversation and persist insights. Use when a user has been exploring papers, asking questions, and wants to capture what was discussed. Triggers -- "make a report from this", "save what we discussed", "write up what we covered", "turn this into a document".
documentation69