Submit and complete Ergouzi image generation, editing, virtual try-on, and upscaling tasks through ergouzi.life, including tasks that use local image files or HTTPS URLs. Use when Codex must call an ergouzi/e-image model, poll the asynchronous task, download its outputs, resume a task ID, or cancel an image task.
Submit and complete Ergouzi video generation, animation, avatar, and person-replacement tasks through ergouzi.life, including tasks that use local media files or HTTPS URLs. Use when Codex must call an ergouzi/e-video model, poll the asynchronous task, download its output, resume a task ID, or cancel a video task.
Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
This skill should be used when the user asks to "find jobs", "scrape LinkedIn jobs", "what roles were posted this week", "search for [role] postings", or wants a ranked list of recent job postings matched and fit-scored against their background.
This skill should be used when the user wants to "create a persona", "generate a user persona", "set up a test persona", "make a simulated user for UX testing", or runs any user-persona-generator skill without an existing persona. It captures a profile of the app under test (once per project), then builds a…
This skill should be used when the user wants to "run a persona test", "start a UX test session", "have {persona} try the app", "assign a task to a persona", or after create-persona when they want the persona to actually use the app. It embodies a persona from ux-testing/personas/, drives the app under test in a live…
Create or edit openEHR specification documents — the AsciiDoc sources, manifest.json, and boilerplate includes in specifications-XX repos. This skill should be used when the user asks to create a new spec, add or edit a chapter/section, set up master.adoc, edit a spec manifest.json, or work on .adoc files in a…
Generate openEHR class documentation — class-definition tables, effective views, and UML class/package diagrams — from BMM schemas with the bmm-publisher tool, for specifications-XX repos and their docs/UML/ content. This skill should be used when the user asks to regenerate class tables, run bmm-publisher, generate…
Manage the openEHR specification governance lifecycle — releases, change requests (CR/PR), and lifecycle states (DEVELOPMENT/TRIAL/STABLE…). This skill should be used when the user asks to create or tag a release, prepare a release branch, update the manifest for a release, submit or manage a CR/PR, promote a spec's…
A standing crew of senior developer agents and the team's single entry point — its job is best-in-class implementation, coding standards, and project health. Use it for essentially ANY software-development request in this repo, whether or not the user says "crew": implementing a feature, fixing a bug, reviewing or…
Derive a v3 SOP-conformance file for a call site — read the agent's whole instruction surface and distill it into intents, an atomic observation vocabulary, and rules, then lint it with the bundled validator. Run after /evals:instrument so the SOP names a real call site. Use when the user says "derive an SOP", "author…
Stamp tessary.callsite.id onto the spans your LLM calls already emit, so production telemetry binds to the call sites graders are keyed on. Run after /evals:connect — it is what makes the platform's observer able to author graders for this repo. Use when the user says "instrument my call sites", "tag call sites", "why…
Use when designing REST endpoints, defining error envelopes, setting a versioning or deprecation policy, choosing pagination shape, adding idempotency to mutations, reviewing API contracts, or when two services need a stable interface between them.
Use when establishing brand foundations before any design work, when two products need to feel related, when defining voice and tone for microcopy, or when logo usage and visual identity rules need documenting.
Use when a task is complete and ready for review, when reviewing a PR, when validating an implementation against its contract, when checking quality before merging, or when a five-axis quality gate is needed before approving code.
Curate Claude Code skill / MCP / hook picks against live upstream sources and pin them in .claude/settings.json. Adding a process harness (a paired skill set) is an ordinary pick this door handles. Reads stack from docs/techstack.md, workflow signal from docs/overview.md + existing pins, then live-queries six source…
A release guide for publishing a software package, including projects with multiple independently versioned packages in one repository, called a monorepo. It determines the release unit, updates versions using Semantic Versioning, and prepares the related GitHub release steps after approval.
A project-discovery workflow that creates `.claude/context.md`, a shared file describing the project's purpose, design, constraints, and measures of success.
A procedure for running programs that may take more than a few dozen seconds, such as training jobs, evaluations, data processing, or servers, while recording logs and detecting failures.
3 1mo agoA160 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: