merceralex397-collab

Find external skills from public registries, GitHub repos, and official skill collections, then evaluate them for quality, licensing, and fitness for adoption. Use when looking for existing skills before building from scratch, evaluating external skill…

Improve an existing skill package — tighten routing, sharpen procedure, add or prune support layers, upgrade packaging. Use when the user says "improve this skill", "this skill is weak/vague/bloated", "harden this SKILL.md", or "add evals/references to this…

Install a skill package into the local agent client from a GitHub repository, local folder, or archive. Use when the user says "install this skill", "add skill from GitHub", or "list available skills". Do not use for creating new skills (use skill-creator),…

Orchestrate multi-skill pipelines through the CLI. Use when "run the creation pipeline", "execute the improvement workflow", "resume my pipeline", or when chaining multiple skills with decision points. Supports Creation, Improvement, and Library Management…

Bundle one or more completed skill folders into versioned distributable archives with manifests, integrity checksums, and OpenCode metadata. Use when a user says "package this skill", "bundle for distribution", "prepare a versioned release", "generate…

Polish and finalize an AI agent prompt file by refining structure, wording, and clarity to match proven best practices while preserving the original intent and markdown frontmatter.

Integrate LLM capabilities into applications with explicit runtime boundaries, structured schemas, cost controls, and evaluation plans. Triggers on tasks involving model inference APIs, prompt engineering systems, LLM toolchain setup, or AI agent runtime…

Register, version, and govern MLflow models through a full lifecycle from training-run artifact to production stage with validation gates, alias-based deployment routing, lineage tracking, and CI/CD automation. Triggers on "register a model", "promote model…

Design and harden agent, command, workflow, and tool prompts for reliable execution across different AI models. Use when creating or revising repo-local agents to apply model-specific prompting techniques, tighten scope, and prevent common agent failure modes…

Find external skills from public registries, GitHub repos, and official skill collections, then evaluate them for quality, licensing, and fitness for adoption. Use when looking for existing skills before building from scratch, evaluating external skill…

Create concise project handoff artifacts, especially a top-level START-HERE document and short resume context for the next session or machine. Use when scaffolding finishes, a milestone closes, or long-running autonomous work needs a compact restart surface.…

Generate structured migration plans with inventory, risk-ranked sequence, rollback procedures, and acceptance criteria for major upgrades or framework migrations. Use when upgrading major dependencies (React 17→18, Python 3.9→3.12), migrating frameworks…

Design and generate a project-specific agent team with specialized agents, tools, plugins, commands, and skills tailored to the project type and stack. Use after the base scaffold exists to customize generic agent templates into project-aware specialists. Do…

Generate client-specific overlay files (metadata, permissions, manifests) from a canonical SKILL.md source for different AI agent clients. Use when publishing a skill to multiple ecosystems (Copilot, OpenCode, Codex, Gemini CLI), converting between overlay…

Review a pull request, validate review comments against the actual implementation, and generate follow-up tickets only for findings that survive evidence-based triage. Use after a PR review cycle when comments need to be triaged into actionable work items. Do…

Create project-local skills populated with actual project data, stack-specific conventions, and domain-specific procedures. Use after scaffolding to replace generic skill placeholders with real project-aware guidance that helps agents work effectively in this…

This skill should be used when the user wants an MCP App, interactive UI resource, inline widget, picker, dashboard, chart, form, or iframe-based MCP user interface. Use after the server's deployment and protocol era are known.

Use when creating or extending a C# MCP server with tools, prompts, resources, stateless HTTP, MRTR, Apps, Tasks, AOT, or Microsoft.Extensions.AI.

Use when publishing, packaging, containerizing, deploying, or distributing a C# MCP server through dnx, MCPB, or a remote HTTP host.

Use when testing a C# MCP server's tools, stateless HTTP endpoint, MRTR retries, tasks, Apps metadata, or conformance behavior.

Use when building, testing, publishing, packaging, or extending an MCP server in C# or .NET, especially for ModelContextProtocol 2.0.0, MRTR, Apps, Tasks, AOT, or Microsoft.Extensions.AI.

This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to Claude", or discusses designing an MCP server. It selects a deployment, language, and tool surface,…

This skill should be used when the user wants to package an MCP server, bundle a local MCP server, make an MCPB, ship a local server without a separate runtime install, or distribute a local filesystem, desktop, hardware, or localhost integration.

Use this skill whenever a user reports any problem with the Claude Desktop application on Windows — including but not limited to: MCP tools or connectors not appearing in chat, extensions not loading (spinner, error badge, nothing shows), app showing a white…

Design and configure the asset sourcing, generation, provenance, compliance, optimization, and import pipeline for game projects. Use after repo-scaffold-factory when a generated repo needs machine-checkable asset truth.

Hold the project-local standards for languages, frameworks, validation, and runtime assumptions. Use when planning or implementing work that should follow repo-specific engineering conventions.

Follow the required ticket lifecycle for this repo. Use when an agent is advancing a ticket through planning, review, implementation, QA, deterministic smoke testing, and closeout and needs the repo-specific stage rules.

Generate the base repository file structure including README, AGENTS.md, docs layout, ticket templates, and the full OpenCode scaffold with agents, tools, plugins, commands, and skills. Use when creating a greenfield repo foundation. This generates a generic…

Run Scafforge's host-side diagnosis flow for an existing repository. Use when a repo needs workflow diagnosis, contract verification, professional codebase review, or a four-report diagnosis pack with evidence-backed ticket recommendations and no repair edits.

Keep code review, security review, and QA passes evidence-based and stage-aware for this repo. Use when a ticket already has an approved plan and implementation evidence and a review lane needs structured findings.

Apply Scafforge's host-side managed repair flow for an existing repository. Use when diagnosis has already identified safe workflow repairs, managed-surface replacement, or contract-refresh work that should be applied with provenance and post-repair…

Design and harden agent, command, workflow, and tool prompts for reliable execution across different AI models. Use when creating or revising repo-local agents to apply model-specific prompting techniques, tighten scope, and prevent common agent failure modes…

Focused code implementation in an assigned worktree. Keep diffs small, run targeted local tests, and report changed files. Enabled via implementer profile skills_allow.

Run and interpret local verification commands for implementer and test-runner profiles. pnpm verify or npm test plus typecheck.

Map relevant files, dependencies, tests, and risks for a codebase task. Read-only.

Guidance for building the Codex app-server runner adapter — thread lifecycle, event parsing, session resume, and version isolation. Use when working on packages/runner-codex or app-server integration.

Plan N independent worktree attempts for exploration or implementation, plus judge criteria to select a winner. Use for best-of-n-explore workflows.

Diagnose and fix failures from local test, lint, and typecheck output only. Use when pnpm verify, npm test, or npm run typecheck fails. Do not use for GitHub Actions or remote CI logs.

Generate competing debug hypotheses and scoped worker prompts for ambiguous bugs. Use before parallel investigation or debug-hypotheses workflows.

Produce a safe worktree foldback checklist before merging changes back. Explicit invocation only — the supervisor executes foldback, not this skill.

Hold the project-local standards for languages, frameworks, validation, and runtime assumptions. Use when planning or implementing work that should follow repo-specific engineering conventions.

Follow the required ticket lifecycle for this repo. Use when an agent is advancing a ticket through planning, review, implementation, QA, deterministic smoke testing, and closeout and needs the repo-specific stage rules.

Decide when risky or long-running work should move into an isolated lane such as a worktree or sandbox. Use when a ticket could destabilize the main workspace or when autonomous work needs a cleaner safety boundary.

Follow the repo's local-git-only workflow safely. Use when an OpenCode agent needs to inspect history, create local commits, or reason about diff state without assuming GitHub access.

Apply the `Weak-tier evidence-first profile` operating profile for the selected downstream models. Use when shaping prompts, delegation briefs, review asks, or evidence requests for this repo.

Use read-only delegation and persistent artifacts for research-heavy work. Use when an OpenCode agent needs background investigation, reference gathering, or comparative analysis without mutating the repo.

Keep code review, security review, and QA passes evidence-based and stage-aware for this repo. Use when a ticket already has an approved plan and implementation evidence and a review lane needs structured findings.

Inspect bootstrap provenance, invocation tracking, and workflow state to explain which repo-local agents, tools, plugins, and skills are actually being exercised.

Run browser-game playtests and frontend QA. Use when the user asks for smoke tests, screenshot-based verification, browser automation, HUD or overlay review, or structured issue-finding in a browser game.

Route early browser-game work. Use when the user needs stack selection and workflow planning across design, implementation, assets, and playtesting before moving to a specialist skill.

Design UI surfaces for browser games. Use when the user asks for HUDs, menus, overlays, responsive layouts, or visual direction that must protect the playfield.

Implement 2D browser games with Phaser. Use when the user wants a Phaser, TypeScript, and Vite stack for scenes, gameplay systems, cameras, sprite animation, and DOM-overlay HUD patterns.

Build React-hosted 3D browser games with React Three Fiber. Use when the user wants pmndrs-based scene composition, shared React state, and 3D HUD integration inside a React app.

Generate and normalize 2D sprite animations. Use when the user asks for full-strip generation from approved source frames, consistent anchor and scale normalization, or preview assets for browser-game animation.

Implement browser-game runtimes with plain Three.js. Use when the user wants imperative scene control in TypeScript or Vite with GLB assets, loaders, physics, and low-level WebGL debugging.

Prepare and optimize browser-game 3D assets. Use when the user asks for GLB or glTF shipping work, including Blender cleanup and export, collision or LOD setup, compression, texture packaging, and runtime validation.

Repo-specific Godot 4.6 Android standards for Woman vs Horse VB, including free/open asset provenance and credits requirements.

Hold the project-local standards for languages, frameworks, validation, and runtime assumptions. Use when planning or implementing work that should follow repo-specific engineering conventions.

Follow the required ticket lifecycle for this repo. Use when an agent is advancing a ticket through planning, review, implementation, QA, deterministic smoke testing, and closeout and needs the repo-specific stage rules.

Hold the repo-specific Godot, Android-export, asset-provenance, and validation rules for Woman vs Horse VB.

Follow the required ticket lifecycle for this repo. Use when an agent is advancing a ticket through planning, review, implementation, QA, deterministic smoke testing, and closeout and needs the repo-specific stage rules.

How to find, evaluate, download, and track CC0/CC-BY game assets from Kenney.nl, OpenGameArt.org, and Freesound.org. Use when sourcing sprites, tilesets, audio, or fonts for this project.

Godot 4.6 Android game development patterns for GDScript, scene structure, asset import, touch input, and export. Use when planning or implementing Godot scenes, scripts, or Android builds.

Keep code review, security review, and QA passes evidence-based and stage-aware for this repo. Use when a ticket already has an approved plan and implementation evidence and a review lane needs structured findings.

Hold the project-local standards for languages, frameworks, validation, and runtime assumptions. Use when planning or implementing work that should follow repo-specific engineering conventions.

Follow the required ticket lifecycle for this repo. Use when an agent is advancing a ticket through planning, review, implementation, QA, deterministic smoke testing, and closeout and needs the repo-specific stage rules.

Apply the `Standard-tier evidence-first profile` operating profile for the selected downstream models. Use when shaping prompts, delegation briefs, review asks, or evidence requests for this repo.

Godot 4.6 Android game development patterns, scene architecture, GDScript conventions, touch input, and export configuration. Use when planning or implementing any game scene, script, or Android build work.

GDScript procedural sprite generation patterns for Route A (colored shapes, no external assets). Use when implementing any visual element — player, enemies, UI, particles, or arena.

Guide an agent through writing a precise, actionable asset description brief that can be executed by a Blender-MCP subagent or used to source matching free assets. Use when a game project needs a specific visual asset defined before creation.

Guide agents through the repo's managed Blender-MCP asset workflow, including saved-blend chaining and audit-log verification.

Hold Godot 4.6 3D game patterns for this Android arena game. Use when implementing scenes, importing GLB models, setting up orthographic camera, or writing GDScript for 3D gameplay.

Hold the repo-specific engineering, validation, and release-proof standards for Woman vs Horse VC's Godot 4.6 Android stack.

Follow the required ticket lifecycle for this repo. Use when an agent is advancing a ticket through planning, review, implementation, QA, deterministic smoke testing, and closeout and needs the repo-specific stage rules.

Manage the Air Con for the Vulnerable Website deployment secrets through its dedicated Infisical project without exposing or broadening credentials.

Apply and maintain the Air Con for the Vulnerable petition design system in this workspace. Use when Codex needs to build or review campaign UI, accessible components, petition pages, evidence/ask layouts, sign handoffs, design tokens, guideline examples, or…

Apply and maintain the Air Con for the Vulnerable petition design system in this workspace. Use when Codex needs to build or review campaign UI, accessible components, petition pages, evidence/ask layouts, sign handoffs, design tokens, guideline examples, or…

Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use…

Repo-specific Godot 4.6 Android standards for Woman vs Horse VD, including zero-import Godot-native art and procedural SFX rules.

Godot 4.6 Android game development patterns, project structure, and mobile-specific guidance. Use when planning or implementing Godot scenes, scripts, exports, or touch input.

How to create all game visuals using only Godot built-in features. No external asset imports allowed. Covers Polygon2D, ShaderMaterial, GPUParticles2D, TileMap, Theme, Line2D, and AudioStreamGenerator with GDScript examples for each technique.