2.2K skills · sorted by relevance
Delegate coding, analysis, refactoring, or reviews from Claude Code to Codex CLI. The skill explains unattended execution, permission settings, output capture, parallel tasks, and independent checks of changed files and test results.
Delegate coding, analysis, planning, and reviews from Codex to Claude Code through its command-line interface. Capture responses, resume sessions, or run independent tasks in parallel, then verify changed files and test results independently.
Turn an explicit request for a coding plan into an ordered checklist. Review project documentation and relevant files, define scope, and outline implementation, validation, and risks without changing any files.
Reviews recent Codex conversations to identify coding habits, strengths, and recurring challenges. Produces a prioritized growth report with practical next steps and relevant HackerNews reading, then delivers it to your Slack direct messages.
Share the current coding session transcript with the Convex team, with explicit consent, for an AI review that identifies unclear setup instructions, tooling failures, and successful patterns to help improve the quickstart system.
Set up OpenRig to run a team of coding agents, including Claude Code and Codex. Open the team interface, pass project goals to its operator, reconnect to agents, and follow assigned work through to its results.
Audits GitHub Actions workflows that run AI coding agents. Traces how attacker-controlled content reaches prompts, checks permissions and sandbox settings, and reports evidence, severity, and fixes for prompt injection and related configuration risks.
Supports authorized security exercises that test data transfer outside a network. Organizes channel choices, compression, encryption, splitting, and receipt verification, alongside the monitoring signals defenders can use to identify different transfer methods.
Create flat SVG illustrations of long-legged people in design and coding scenes. Large black shapes, bright colors, and consistent poses give onboarding screens, error pages, and marketing cards a shared visual style.
Create hand-drawn SVG illustration cards featuring expressive creatures or living objects that represent coding and design ideas. A supplied brush library supports uneven ink outlines, loose watercolor fills, large eyes, and consistent details across a set.
Apply a short quality checklist to everyday code changes. Read existing code first, keep edits focused, check types and common security risks, verify execution, remove debugging leftovers, and summarize what changed and its impact.
Access TeamAI workflows for sharing skills, rules, documents, and environment settings across AI coding tools. This entry skill loads version-matched guidance for team setup, synchronization, codebase knowledge, and sharing lessons from a session.
Use Evo 2 to score DNA sequences, turn genomic regions into numerical representations for classification, and generate sequences from a supplied prefix. Compare reference and variant sequences or assess coding and regulatory regions across species.
Review a coding session to identify improvements to the agent’s working environment. Get prioritized suggestions for finding files, strengthening automated checks, clarifying guidance, reducing costly tool calls, and accessing missing information.
Analyze interviews, focus groups, and open-ended survey responses using Braun and Clarke's six-phase framework. Label meaningful passages, develop and review themes, and produce an academic Word report with an annotated map showing theme relationships.
Condensed tika-eval pattern for charset-detector regression hunts ("A picks encoding X, B picks Y") using one build and two configs — encoding-pair flip queries, OOV/languageness/FFFD signals, per-file detector attribution.
The English summary is being prepared. Showing the original description.
Add EAGLE-3 or draft-model speculative decoding to a Jetson vLLM server when TPOT is the bottleneck.
The English summary is being prepared. Showing the original description.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
The English summary is being prepared. Showing the original description.
Delegate a coding task to Aider (`aider`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Aider - phrasings like "have Aider do X", "delegate this to aider", "run it through Aider", or "use Aider to implement/fix/refactor" - or wants to run a queue of coding tasks through Aider while staying the reviewer. This includes asking Aider to drive a local or self-hosted OpenAI-compatible endpoint ("have Aider use my local model", "run Aider against llama.cpp / Ollama / vLLM / LM Studio"), which Aider reaches via `--api-base`. DO NOT USE for local-model or coding requests that do not name Aider, for tasks small enough to do inline, or when the user wants the code written directly without delegating.
The English summary is being prepared. Showing the original description.
Delegate a coding task to the Cline coding agent CLI (`cline`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Cline - phrasings like "have Cline implement X", "delegate this to cline", "run it through Cline", or "use cline to implement/fix/refactor" - or wants to run a queue of coding tasks through Cline while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.
The English summary is being prepared. Showing the original description.
Delegate a coding task to the Pi coding agent CLI (`pi`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Pi - phrasings like "have Pi implement X", "delegate this to pi", "run it through Pi", or "use pi to implement/fix/refactor" - or wants to run a queue of coding tasks through Pi while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.
The English summary is being prepared. Showing the original description.
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
The English summary is being prepared. Showing the original description.
Create, inspect, and safely update project-scoped ReachAI Agents; edit and publish Supervisor config drafts; discover published bindable Skills; and attach or detach exact Skill versions through the Agent AI Coding REST API. Use when an AI coding tool is asked to add an Agent, configure its model or prompt, bind a Skill, remove a Skill binding, or attach a published Workflow as a Tool.
The English summary is being prepared. Showing the original description.
Turns a legal question, a set of draft questions, or source material such as a statute, jury instruction, rubric, contract checklist, or coding manual into a battery of narrow questions that TypeSafe's Jev, a fast classifier that returns probabilities rather than prose, can answer reliably across many documents. The skill breaks conclusions such as negligence, felony murder, or standing into element-level questions, writes the governing rule into each question, and delivers the questions alone, in Jev's request format or in plain English. Built for legal work that asks the same questions of many texts: coding statutes across jurisdictions, coding opinions or case files for empirical research, checking contracts against a review checklist, screening intake narratives, and grading student work against a rubric. Use when asked to write Jev questions, build a classifier for legal documents, or turn a legal test into yes-or-no questions. Running the questions requires Jev access; writing them does not.
The English summary is being prepared. Showing the original description.