A skill for driving GitHub pull request creation. Handles change review, required checks, commit, push, and PR creation in one flow, and expects fresh verification evidence from `code-change-verification` when repository code changed.

React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.

Review a GitHub pull request for this repository when the user starts the prompt with `$pr-review` followed by a PR number, such as `$pr-review 105`. Conduct a real PR review focused primarily on backend correctness, API/schema consistency, persistence/runtime safety, and frontend interoperability with the backend. Submit the final review on GitHub as either approval or changes requested.

Ensure every run ends with persisted artifacts and an updated run outputs ledger.

Three.js performance optimization and best practices guidelines. Use when writing, reviewing, or optimizing Three.js code. Triggers on tasks involving 3D scenes, WebGL/WebGPU rendering, geometries, materials, textures, lighting, shaders, or TSL.

Apply clean code practices for readability, naming, cohesion, maintainability, and low-risk refactoring.

Perform high-rigor structural and aesthetic audits with findings-first output, actionable remediation, and governance-aware preconditions.

python-expert

Publica conteúdo no Instagram via Instagram Graph API (Meta) — suporta posts de imagem, carrosséis e reels. Usa ImgBB para hospedagem gratuita de imagens.

Extend, edit, validate, and review shipped Grafana dashboards for BioETL. Use when tasks touch `grafana/dashboards/*.json`, dashboard navigation, panel queries, variables, units, thresholds, Loki/Tempo drilldowns, or operator-facing dashboard UX. Treat repo dashboard JSON as source of truth and update docs when shipped dashboard behavior changes.

Qwen CLI integration for Alibaba's Qwen AI models. Use for code generation, review, and autonomous coding tasks with Qwen Coder.

When designing backend system architecture, choosing between API styles, or making database scaling decisions. When reviewing backend code for production readiness, performance bottlenecks, or architectural anti-patterns. Also when planning authentication architecture or error handling strategy across service boundaries. For code quality patterns use clean-code instead. For database-specific queries use database instead. For security reviews use security-best-practices instead. For containerization use docker-expert instead. For NestJS-specific work use nestjs-expert instead. For debugging errors use error-resolver instead.

'Author, fix, and review Eraser Diagram-as-Code DSL from natural language requirements using this repository specs. Use this skill whenever the user asks for Eraser DSL, diagram-as-code, flowcharts, ERD/schema diagrams, architecture/cloud diagrams, sequence diagrams, BPMN/swimlane diagrams, syntax fixes, icon/styling updates, or conversion from plain English process/system descriptions into runnable Eraser code.'

Embedded C development, motor control algorithms, Field Oriented Control (FOC), BLDC six-step commutation, sensing topologies, protection design, and STM32G4 hardware acceleration for digital drives. Use this skill when writing or reviewing firmware for PMSM, BLDC, and related motor-drive systems involving SVPWM, Park/Clarke transforms, current/speed/position cascades, sensorless observers (SMO/PLL), signal filtering, and hardware optimizations such as CORDIC and FMAC when justified by timing, determinism, or control-loop workload.

Role-based review system with lite mode for fast reviews and council mode for chaired deliberation. Reviewers speak from their own job function, can disagree with reasons, and the chair decides whether to approve, request changes, defer, or veto.

Use when reviewing a project's architecture for design pattern applicability -- either validating a design document before implementation, or analyzing an existing codebase for pattern improvement opportunities.

Multi-turn verification loop for LaTeX papers via external reasoning model. Each section agent conducts back-and-forth dialogue, pushing back on weak points, and produces structured reports.

Review, create, update, and sync Markdown documentation so it stays accurate, current-state only, code-aligned, concise, and non-duplicative. Use when the user asks to write docs, update README/docs/*.md, sync docs with the codebase, review docs for drift, stale content, overlap, or inconsistent naming, or enforce documentation standards. Do not use for roadmap writing, speculative design, historical writeups, migration narratives, or changelog-style release narration unless the user explicitly asks for them.

Compare actual patient care against guideline recommendations — flag patients who are overdue for review, off-protocol, or missing recommended interventions. Generate structured audit reports with improvement actions. Integrates with Herald-parsed guideline JSONs. Use for clinical governance cycles, quality improvement, or pre-inspection preparation.

Use when the Apple setup flow needs to create or align project .codex/config.toml, official multi-agent runtime settings, and optional MCP integrations for an Apple repository.

Common software architecture patterns, ADR templates, and anti-pattern detection. Supports architectural review, design decisions, and system documentation.

Structured code review criteria for pre-implementation plan review (Critic) and post-implementation security/quality review. Covers security, performance, maintainability, and correctness with severity ratings.

Security vulnerability detection patterns including OWASP Top 10, language-specific vulnerabilities, and remediation guidance. Load when reviewing code for security issues, conducting audits, or implementing authentication/authorization.

TDD workflow and test strategy patterns including test pyramid, coverage strategies, mocking approaches, and anti-patterns. Load when writing tests, designing test strategies, or reviewing test coverage.

Refines ML/scientific LaTeX papers based on reviewer or advisor feedback. Handles structural reorganization (moving problem statements, merging sections), concrete instantiations of abstract tables, cross-file deduplication, and compilation verification. Use when the user requests paper revisions, addresses reviewer comments, restructures sections, or improves exposition clarity.

Draft or revise a mathematically rigorous LaTeX research paper for theory-heavy ML, scientific computing, numerical analysis, control, geometry, or applied mathematics. Use when the user wants help planning the paper, structuring sections, formalizing notation, deciding theorem/proof obligations, specifying complexity or convergence claims, designing figures, or improving global flow and cross-references. Do not use for final QA-only review without drafting or restructuring work.

Review a LaTeX research paper for mathematical rigor, notation consistency, proof obligations, numerical-analysis discipline, complexity claims, convergence/error bounds, figure quality, section flow, cross-references, and global coherence. Use when the user wants a deep technical review or verification pass on a paper, supplement, or LaTeX project. Do not use for initial drafting unless the user explicitly asks for review-first feedback.

Research-Plan-Implement workflow with Codex peer review. Use when the user says /rpi, asks to start a research-plan-implement cycle, wants Codex review on a plan, or needs to create research docs, plans, or implementation reports following the RPI protocol.

Review and fix alignment, label collision, clipping, legend-over-data, overlap, and layout issues in TikZ and pgfplots figures inside LaTeX documents. Use when the user wants to review figures in a paper, tutorial, lecture notes, or thesis before submission; when a reviewer flags figure problems; when a rendered figure visibly has overlap, clipping, or label collisions; when setting up a per-figure review workflow across a large document; or when the user shows a screenshot of a figure that looks wrong. Trigger proactively whenever the user mentions figure alignment, TikZ layout, pgfplots legends/axes, figure cleanup, or asks to fix a figure — even if they don't explicitly say 'review'. Covers a fast iteration loop: extract each tikzpicture into a standalone, compile to PNG, fix, sync back to the main file.

Analyze contracts to identify key clauses, risks, obligations, deadlines, and parties. Multi-language support with focus on French and EU commercial law.

Evaluate AI agent outputs systematically using rubrics, assertions, and reference comparisons. Detect quality drift over time.

Detect and classify technical debt in AI-generated code — patterns specific to LLM outputs, shallow implementations, missing edge cases, and accumulation signals.

Manage skill versioning, freshness tracking, deprecation, changelog generation, and maintenance workflows for skill repository maintainers.

Validate SKILL.md structure, frontmatter completeness, token budget, freshness, naming conventions, and cross-platform portability before publishing.

Use when executing an implementation plan task-by-task - dispatches subagents for implementation, manages git worktrees, handles phased multi-service deployment

Use when starting a software development conversation and the user's intent is not clearly matched by a specific enggenie skill - routes to the right role-based expert

Use when requesting or receiving code review - dispatches reviewer subagent or processes human PR feedback with technical evaluation

Use when reviewing frontend implementation against design specs - design system compliance, responsive behavior, accessibility audit

Use this skill when the user is stuck in a video game and wants help without spoilers. Triggers: 'hintme', 'I'm stuck', 'what do I do next', 'hint me', 'game help', 'stuck in game', 'where do I go', 'how do I beat this', 'game screenshot help'. Analyzes game screenshots and gives progressive hints — nudge first, then clearer direction, then explicit answer. Works with any game. Do NOT use for: game recommendations, game reviews, non-gaming questions, or cheat codes.

Scan a user's Gmail to find upcoming subscription renewals, recurring payments, and billing deadlines. Use this skill whenever the user asks about their subscriptions, recurring charges, upcoming renewals, payment schedules, billing timelines, or wants to audit what services they're paying for. Also trigger when users say things like 'what am I subscribed to', 'when is my next bill', 'show me my recurring payments', 'subscription audit', 'what's renewing soon', 'am I still paying for X', or any variation involving tracking, managing, or reviewing subscription costs from their email. This skill requires the Gmail MCP connector to be enabled.

Evalúa la salud de un proyecto open source (repo GitHub, paquete npm/pip, o URL). Genera un brief estructurado con semáforo por categoría. Usar cuando el usuario quiera evaluar un nuevo proyecto, librería, o dependencia antes de usarlo.

>

>

Maintain DesignVault health and writeback quality. Use when Codex needs to scaffold a starter vault, search current truth, lint vault structure, trace changed files back to wiki pages, generate conservative writeback suggestions, draft change-review pages, or perform maintenance-only cleanup on a DesignVault repo.

Quality review skill based on EPUB 3.3 (W3C Recommendation). Performs structure validation, specification compliance checking, and accessibility evaluation of EPUB files, generating reports with specification rationale. Use this skill for any EPUB-related verification tasks including validation, quality checks, spec compliance confirmation, and e-book inspection.

Audit a repository after large refactors, branch merges, or parallel agent threads for contradictions between implementation, docs, configs, tests, examples, and control files. Use when the goal is post-merge validation, release-readiness consistency checking, documentation-drift detection, or merged-only edge-case hunting rather than style review.

Stage committed Ceratops skill changes into the runtime checkout's local `release/*` branch for coherent local preview. Use when Codex should merge ready task-worktree branches into a release branch created from `main`, switch the runtime checkout to that branch, update the local skill install, and run the local validation batch before GitHub shipping.

Merge a GitHub pull request safely with Ceratops defaults, starting with a live scripted readiness check and ending with verified cleanup.

Refresh and update the Ceratops GitHub skill family in the `codex-skills` repo against current GitHub standards and live GitHub behavior. Use when routine or explicit GH-skill upkeep should review `skills/ceratops-gh-*`, shared core rules, helper-runtime claims, and repo docs, apply safe low-risk updates, and ship the resulting skill changes.