A template for writing a Codex skill, which is a set of instructions that tells an AI agent when and how to handle a particular kind of task. The template includes triggers, rules, examples, dependencies, and optional prompt files.
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detection-only mode that flags patterns without rewriting.
Ultra-compressed communication mode. Slash token usage 75% by speaking like caveman while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Use when the user asks how to check Codex access mode, continue the previous dialog instantly, use codex resume, or recover the latest session id from local Codex session files without rereading old chats.
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or…
Scan code for security vulnerabilities, leaked secrets, and dependency issues using the Autofix Bot API (api.autofix.bot), and auto-fix detected issues. Use this skill when asked to: (1) Scan or analyze a repository or code for security issues, secrets, or vulnerabilities using Autofix Bot, (2) Upload/sync a local git…
Retrieve code review results from DeepSource — issues, vulnerabilities, report cards, and analysis runs. Use when asked about code quality, security findings, dependency CVEs, coverage metrics, or analysis status.
A guided way to explain complicated code in simple language when the user asks for an explanation. It uses a fixed structure such as a short summary, everyday analogy, organisation, execution flow, and possible problems.
A guide for finding existing external resources such as coding-agent skills, MCP servers, and interface components. An MCP server connects an AI assistant to an external service or tool.
Scans git diffs for exposed secrets using truffleHog entropy detection and custom regex patterns. Integrates with pre-commit hooks and GitHub push protection API for real-time blocking.
A guide to logging in software: recording events, values, errors, state changes, and timings so developers can understand what a program did. It describes useful log levels and a readable, machine-parsable format.
A coordinator for running separate coding-agent processes in tmux, a terminal tool that keeps multiple sessions running. Each worker has an isolated context and sends results back through files or captured terminal output.
A recovery guide for coding agents that time out, crash, return incomplete results, or leave dependent agents without needed information. It describes when to retry, skip, use a fallback, or continue with partial results.
A decision guide for choosing whether to run several coding agents at once. It matches common requests, such as audits or testing plus documentation, with suitable agents and parallel work.
A reporting tool that combines findings from several parallel coding agents into one clear report. It removes duplicate findings, marks disagreements, and groups issues by urgency.
Validates environment variables in CI, prevents secret leaks, enforces masking, and provides fail-fast validation with clear documentation. Use for "secrets management", "env var validation", "credential security", or "secret masking".
Manages environment variables and secrets securely with encryption, rotation, and provider integration. Use when users request "secrets management", "environment variables", "API keys", "credentials storage", or "secret rotation".
Detects leaked API keys, tokens, passwords, and credentials in code with pre-commit hooks, CI checks, scanning rules, and remediation procedures. Use for "secret scanning", "credential detection", "API key leaks", or "secret management".
Mandatory secret scanning before any git operation. MUST trigger automatically before git commit, git push, git add, PR creation, or any commit-related skill. Scans staged files for API keys, tokens, credentials, and other secrets to prevent accidental exposure in version control.
Instructions for setting up pre-commit checks that inspect code before a commit is created. They cover formatting, linting, type checking, and Lizard, a tool that measures code complexity across programming languages.