marketplace

Create or update independent vendor positioning matrix reports. Use when asked for magic quadrant style vendor comparisons, analyst-style market matrices, provider landscapes, technology shortlists, two-axis vendor charts, sourced scoring models, or PDF, Microsoft Word/DOCX, and Markdown vendor evaluation packages. Produces original, evidence-led reports with source ledgers, transparent scoring, bank/regulatory due diligence, and safeguards against Gartner or other analyst-firm imitation.

Create and edit checkpointflow workflow YAML files. Use this skill whenever the user wants to create a workflow, automate a process as a YAML pipeline, define steps that mix CLI commands with human or agent checkpoints, turn a conversation into a reusable runbook, or asks about writing cpf/checkpointflow workflows. Also use it when you see keywords like "workflow", "runbook", "approval flow", "pause and resume", or "await event" in the context of automation.

Create and improve Claude Code skills using a structured checkpointflow workflow with test-driven iteration. Use this skill whenever the user wants to create a skill, make a skill, build a skill, improve an existing skill, test a skill with evals, benchmark skill quality, optimize a skill description, or turn a conversation into a reusable skill. Also triggers on "skill for X", "automate this as a skill", "package this as a skill", and similar phrases.

Create new architecture evaluation rubrics (profiles and overlays) based on the Enterprise Architecture Rubric Operational Standard (EAROS). Use this skill whenever the user wants to "create a rubric", "add a rubric profile", "write an architecture evaluation rubric", "define scoring criteria for architecture artifacts", "create an EAROS profile", "add an overlay", "create a security overlay", "create a data overlay", "evaluate architecture artifacts", "set up architecture review criteria", "build a rubric for solution architecture", "create an ADR rubric", "create a capability map rubric", "define architecture quality criteria", or mentions "EAROS", "rubric", "architecture evaluation", "scoring profile", or "architecture review criteria" in the context of creating or extending evaluation rubrics. Also triggers when the user says "help me evaluate architecture documents", "define review criteria for our artifacts", "standardize architecture review", "create a review checklist", or any request to systematicall

Apply an EAROS rubric to an architecture artifact using the three-pass agent evaluation pattern (Extractor, Evaluator, Challenger). Use this skill whenever the user wants to "evaluate an architecture artifact", "apply a rubric", "review an architecture document", "score an architecture artifact", "run an EAROS evaluation", "assess architecture quality", "apply the solution architecture rubric", "evaluate this ADR", "review this capability map", "check this against the rubric", "run the architecture review", or mentions "evaluate", "score", "assess", "review", or "apply rubric" in the context of applying an EAROS rubric to a specific artifact. Also triggers when the user says "how does this artifact score", "is this architecture document good enough", "run the three-pass evaluation", "extract evidence from this document", or any request to systematically evaluate a specific architecture work product against defined criteria. Does NOT trigger for creating rubrics (use earos-rubric for that), general architectur

Autonomous agent-driven optimization loop inspired by Karpathy's autoresearch. Sets up and runs an iterative hill-climbing harness where subagents modify an artifact, evaluate against a single scalar metric, and keep improvements. Use this skill whenever the user wants to "optimize something iteratively", "run an autoresearch loop", "hill-climb on performance", "auto-optimize", "iterate and improve automatically", "run experiments autonomously", "autonomous optimization", or mentions "autoresearch" in any context. Also triggers when the user describes a workflow like "try variations and measure which is best", "keep tweaking until it's faster", "optimize this config", "find the best prompt", "tune hyperparameters", "benchmark variations", or any scenario where they want an agent to autonomously explore a search space against a measurable objective. Works with any domain — code performance, prompt engineering, config tuning, SQL optimization, CSS optimization, model training, build flags, or anything with a me

Discover, audit, reconcile, modify, and delete GitHub Copilot customizations across both Copilot IDE (VS Code) and Copilot CLI environments. Use this skill whenever the user wants to "list copilot customizations", "find copilot files", "audit copilot setup", "what copilot configs do I have", "reconcile copilot IDE and CLI", "clean up copilot files", "delete copilot agent", "show copilot instructions", "compare copilot configs", "remove unused copilot customizations", "copilot drift", "copilot inventory", "what does copilot see", "manage copilot", "copilot hygiene", or any request involving exploring, inspecting, modifying, or removing existing Copilot customization files. Also triggers when the user mentions conflicts between Copilot IDE and Copilot CLI, cross-readability issues, or wants to understand which files each Copilot variant sees. Does NOT trigger for creating new customizations from scratch (use copilot-customization skill instead).

Generate enterprise-ready, agent-first CLIs from OpenAPI or Swagger specifications. Use this skill whenever the user wants to "generate a CLI from an OpenAPI spec", "turn a Swagger API into a CLI", "scaffold an enterprise REST CLI", "create a CLI wrapper around a REST API", "derive a machine-readable CLI from an API description", "generate auth-aware commands from an OAS file", "build a deterministic CLI for this service", "create an agent-friendly CLI from this API", or mentions "api-anything", "OpenAPI CLI", "Swagger CLI", "REST CLI generator", "OAS to CLI", or "API CLI scaffold" in the context of generating CLI code from an API specification. Also triggers when the user provides an OpenAPI/Swagger spec file and asks to build a command-line tool from it, even if they don't use the exact term "CLI". Does NOT trigger for generic API discussion, SDK generation, client library generation, API debugging, or consuming an existing CLI.

Run a blackbox test of the project's CLI or executable. Use this skill whenever the user wants to "blackbox test", "test the CLI blindly", "test as an outsider", "test without reading source", "QA test the tool", "smoke test the CLI", "exploratory testing", or says anything like "pretend you don't know the code and test it". Also triggers when the user mentions "blackbox", "black box", "blind test", or "external test" in the context of testing their project. This skill works with any tech stack — Python, Node, Rust, Go, or anything else that produces a CLI.

Augment an existing Execution Plan (ExecPlan) with CLI design requirements and project scaffolding guidance. Use this skill whenever the user wants to "augment a plan", "add CLI requirements to a plan", "add scaffolding to a plan", "enrich a plan with CLI design", "make my plan CLI-ready", "add agent-first CLI patterns to my plan", or mentions "augment plan", "plan augmentation", "CLI plan", or "scaffold plan" in the context of enhancing an existing ExecPlan. Also triggers when the user has an existing PLAN.md and wants to add CLI interface design, structured output patterns, error handling contracts, or project scaffolding milestones. Covers both adding CLI-specific milestones (structured envelopes, error codes, exit codes, guide commands, dry-run, safety flags) and scaffolding milestones (repo layout, documentation, agent guidance files, quality infrastructure). Even if the user only mentions one aspect (e.g., "add CLI stuff to my plan" or "add scaffolding steps"), use this skill — it handles both independe

Generate self-contained, agent-executable Execution Plans (ExecPlans) from PRD files. Use this skill whenever the user wants to "create a plan", "generate an execution plan", "turn a PRD into a plan", "write an ExecPlan", "create an implementation plan from a PRD", "break down a PRD into steps", "make a plan from requirements", "convert PRD to plan", or mentions "ExecPlan", "execution plan", or "implementation plan" in the context of producing one from a requirements document. Also triggers when the user has a PRD.md file and wants actionable next steps, says "plan the implementation", "create milestones from this PRD", or "how do I implement this PRD". This skill produces plans that a stateless coding agent or human novice can follow from top to bottom to deliver working, observable results.

Write enterprise-ready, agent-executable Product Requirements Documents (PRDs). Use this skill whenever the user wants to "write a PRD", "create a PRD", "draft product requirements", "create a product spec", "write requirements for a new feature", "create a product document", "write an agentic PRD", "create a requirements document", "draft a PRD for coding agents", "plan a new product or feature", or mentions "PRD", "product requirements document", or "product spec" in the context of writing or creating one. Also triggers when the user says "help me plan a feature", "scope out a project", or "define requirements for" something. This skill produces PRDs that coding agents can execute with low drift, low rework, and strong governance.

Approximate the Danske Bank Sapphire design system using plain CSS and HTML, without installing @danske/sapphire-* packages. Use this skill whenever the user asks to build UI that should look like Sapphire, match Danske Bank's design system, create Sapphire-styled components, or wants banking/fintech UI with a Scandinavian design language. Also trigger when the user mentions 'sapphire tokens', 'sapphire components', or wants to create UI prototypes that follow the Sapphire visual style. This skill is framework-agnostic and works with any frontend stack.

Integrate skills as plugins into the Claude Code plugin marketplace. Use this skill whenever the user wants to "add a skill to the marketplace", "create a plugin from a skill", "package a skill as a plugin", "register a plugin", "integrate a skill", "convert a skill to a plugin", "scaffold a plugin", or mentions adding something to the plugins directory. Also activate when the user has a SKILL.md they want to publish, wants to update marketplace.json, or is working on plugin structure in this repository.

This skill should be used when the user asks to "improve a skill", "optimize a skill", "review a skill", "audit a skill", "apply SkillsBench findings", "make a skill more effective", "refactor a skill", "fix a skill", or mentions improving, optimizing, or auditing an existing Claude Code skill based on research-backed best practices.

Create, scaffold, and configure GitHub Copilot customizations for VS Code projects. Covers custom instructions (.instructions.md), prompt files (.prompt.md), custom agents (.agent.md), agent skills (SKILL.md folders), hooks (.github/hooks/), and MCP server integration. Use when asked to "set up copilot", "create an agent", "add instructions", "create a prompt", "scaffold a skill", "configure hooks", "customize copilot", or when building any GitHub Copilot customization for VS Code or GitHub.com.

TODO: Describe what this skill does and when Copilot should load it. Include trigger phrases like "create X", "set up Y", "scaffold Z". Be specific — the description determines automatic activation.

This skill should be used when the user asks about "ArchiMate elements", "which element to use", "ArchiMate layers", "business layer", "application layer", "technology layer", "motivation layer", "strategy layer", "active structure", "passive structure", "behavior elements", or needs help selecting the correct ArchiMate element type for modeling enterprise architecture.

This skill should be used when the user asks about "ArchiMate patterns", "microservices in ArchiMate", "cloud architecture ArchiMate", "API gateway pattern", "event-driven architecture", "container architecture", "Kubernetes ArchiMate", "data architecture pattern", "security architecture", "capability mapping", "value stream", or needs to model modern architecture patterns in ArchiMate.

This skill should be used when the user asks about "ArchiMate naming conventions", "model quality", "EA smells", "anti-patterns", "ArchiMate best practices", "model review", "abstraction levels", "viewpoints", "model organization", or needs guidance on creating high-quality ArchiMate models.

This skill should be used when the user asks about "ArchiMate relationships", "composition vs aggregation", "realization relationship", "serving relationship", "assignment relationship", "triggering", "flow relationship", "access relationship", "influence", "specialization", "cross-layer relationships", or needs help connecting ArchiMate elements correctly.

This skill should be used when the user asks to "create a jArchi script", "write an Archi script", "automate ArchiMate", "export from Archi", "query ArchiMate elements", "create ArchiMate views", "run Archi headlessly", "Archi CLI", "batch process ArchiMate model", or mentions "jArchi", ".ajs script", "Archi automation", or ArchiMate scripting. Provides comprehensive jArchi API knowledge and CLI automation support.

This skill should be used when the user asks to "create a diagram", "make a flowchart", "generate a .drawio file", "draw.io diagram", "diagrams.net", "architecture diagram", "sequence diagram", "ER diagram", "class diagram", "network diagram", "org chart", "workflow diagram", "UML diagram", "ArchiMate diagram", "C4 diagram", "C4 model", "enterprise architecture", or mentions "drawio", "mxGraph", or diagram visualization. Provides comprehensive knowledge for creating production-ready DrawIO XML files.