bcos-wiki

Wiki zone manager for BCOS. Ingests URLs / local docs / inbox captures into docs/_wiki/ as schema-validated pages with banner citations, three structural shapes for source-summary, and two-tier refresh. Schema-driven, CLEAR-governed, derived-artifact. Invoke with /wiki.

audit-references

Use when literature notes exist and need citation verification, or before publishing any artifact that cites literature

Bitrise

MCP Server for Bitrise, enabling app management, build operations, artifact management, and more.

Session manager for Claude Code with automatic documentation and artifact tracking

adopt

Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.

solo-artifacts

Use when a Solo task or thread should become an interactive, reviewable, self-contained HTML artifact for progress/status, review/decision, or comparison/leaderboard work inside Solo.

synapse

Codex-led multi-model workflow (Codex + Claude + Gemini). Use when the user asks to run `synapse <cmd> ...` to generate draft diffs/audits and persist artifacts to `./.synapse/**`.

Evaluation framework for LLM knowledge inputs — prompts, RAG corpora, skills, agent workflows. Fix the model, vary the artifact. Built-in statistical rigor: bootstrap CI, Krippendorff α, length-debias, saturation curves.

project-artifact — an opinionated project status page

This skill produces one specific *kind* of artifact: a tabbed status page that represents a project too big for one update — a software migration, a research effort, a launch, an org initiative; anything with a set of parallel/dependent workstreams tracked over time. It generates the HTML (one fil

grace-ask

Answer a question about a GRACE project using full project context. Use when the user has a question about the codebase, architecture, modules, or implementation — loads all GRACE artifacts, navigates the knowledge graph, and provides a grounded answer with citations.

artifact-naming

Naming conventions for artifact kind and path, ensuring data can be aggregated and analyzed

build-artifacts

Regenerate dbt test fixtures after dbt_project changes

github-actions

GitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts. Use when setting up CI build pipelines or downloading GitHub Actions artifacts via gh CLI and GitHub API.

dependency-analysis

Generate and validate controller-resource dependency graph artifacts for Kamera coverage strategy v2. Use this when extracting triggers/reads/writes from Kubernetes control planes, assigning resource roles, and producing contract-compliant dependency-graph.json plus schema-map.json outputs.

skills-hub

Use this skill when the user wants to discover, inspect, install, or apply Skills Hub presets, kits, AGENTS.md policies, or skill packages for a project. It guides the agent to use the Skills Hub CLI to search presets, inspect their policy and selected skills, install them as kit artifacts, and apply them with optional temporary skill overrides after user confirmation.

cleanup-build-artifacts

Removes transient build artifacts this task produced in the ironlint repo before declaring work done. Use at the end of any task that ran `cargo build --release`, `cargo mutants`, `cargo llvm-cov`, generated a one-off binary, wrote a scratch file like `pr.diff` or an ad-hoc tarball, or any other throwaway output. Do NOT use to wipe the actively-iterating `target/` directory.

Suggesting /masterplan import for legacy planning artifacts

This skill **suggests**, it does not act. The user must explicitly run `/masterplan import` to convert anything.

Executor Workflow Skill (Strict Protocol)

You are an Executor in the Artifact-Driven Workflow. Your task is to perform the work efficiently and document the result in an artifact.

Io.Github.AgiMaulana/CodemagicMcp

Codemagic CI/CD MCP Server — manage builds, apps, artifacts, and caches from your AI

audit-plan

Structural audit of implementation plans — dependencies, data flow, ordering, stale artifacts. Runs BEFORE per-phase reviews to catch design-level issues early. Use when asked to 'audit the plan' or after /create-plan for plans with 3+ phases. Do NOT use for per-phase template checks — use /review-plan instead.

Artifacts

Save decisions, plans, and notes from any AI session and retrieve them later — from any client. Ask

design-elevation

Comprehensive design elevation system that automatically transforms functional visual outputs into polished, professional designs. Use when creating ANY visual output including presentations (pptx), spreadsheets (xlsx), dashboards, reports, HTML artifacts, PDFs, web pages, or data visualizations. Applies systematic design thinking grounded in Tailwind CSS as the canonical design token system. Structures decisions through functional patterns (what users interact with) and perceptual patterns (how the design feels), following Alla Kholmatova's design systems framework. Triggers on ALL requests for visual content creation, ensuring outputs look hand-crafted rather than template-based.

Testrail Mcp Server

Model Context Protocol (MCP) server for TestRail platform, enabling LLMs to manage test artifacts.

Build the artifact CI will publish

npm run build && npm run build:server

debug-capz-k8s

Debug CAPZ (Cluster API Provider Azure) Kubernetes cluster failures. Covers live cluster inspection via kubectl, VM-level debugging via az CLI, Prow/GCS artifact analysis, and build log triage. Knows CAPZ template flavors, E2E test structure, addon deployment (Calico, cloud-provider-azure, CSI), common failure patterns, and transient errors to ignore.

Io.Github.Autonomous Testing/Wopee Mcp

AI testing agents for web apps — dispatch test runs, crawls, fetch artifacts and status.

/capture Skill

> Emergency ejector seat for untracked conversations. When invoked, reads the JSONL transcript, extracts the current topic's conversation, writes a structured research artifact to docs/reports/, and commits it. Closes the governance gap where pure conversation sessions bypass all framework enforceme

bounded-loop-runner

Design safe unattended or long-running loops with explicit limits, checkpoints, and handoff artifacts.

notebooklm-research

Full-autopilot AI research agent powered by Google NotebookLM (notebooklm-py v0.3.4). Ingests sources (URL, text, PDF, DOCX, YouTube, Google Drive), runs deep web research, asks cited questions, and generates 10 native artifact types (audio podcast, video, cinematic video, slide deck, report, quiz, flashcards, mind map, infographic, data table, study guide). Produces original content drafts via Claude, with optional publishing to social platforms via threads-viral-agent integration. Use this skill when the user mentions: NotebookLM, research with sources, create notebook, generate podcast from articles, turn research into content, trending topic research, research pipeline, source-based analysis, cited research answers, generate slides, generate quiz, make flashcards, deep web research, create infographic, compare sources, research report, study guide, source analysis, or knowledge synthesis.

evidence-heavy-evaluator

Generate an evidence-first, read-only repository evaluation report with deterministic scoring and actionable recommendations. Use when the user asks to assess readiness, maintainability, release-readiness, documentation gaps, or engineering health and wants auditable artifacts (`json` + `markdown` + raw command logs).

cap-change-workflow

Use for end-to-end CAP change workflows: modify CDS/handlers, regenerate artifacts, and run a short verification checklist for this repository.

audit-context

Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.

openspec-update-change

Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

og-board-individual

Use when you need to work with tasks: view tasks, list tasks, update task status, add blockers, artifacts, and worklogs.

loopx-auto-research

Use when a LoopX worker is operating an auto-research lane, demo pane, frontier item, evidence packet, promotion/retirement decision, or visible tmux/Codex auto-research rehearsal. Identity must come from the LoopX role profile and quota/frontier packet; this skill only provides role-specific execution checklists, artifact contracts, and stop conditions.

super-dev

Super Dev pipeline governance: research-first, commercial-grade AI coding delivery with 10 expert roles, 9 pipeline stages, quality gates, and audit artifacts.

analysis-phase

Validates cross-artifact consistency and detects breaking changes during feature analysis. Use when running /analyze command, validating spec-plan alignment, checking task-implementation consistency, or identifying API/database/UI breaking changes before deployment. (project)

cypilot

Invoke when user asks to do something with Cypilot, or wants to analyze/validate artifacts, or create/generate/implement anything using Cypilot workflows, or plan phased execution. Core capabilities: workflow routing (plan/analyze/generate/auto-config); deterministic validation (structure, cross-refs, traceability, TOC); code↔artifact traceability with @cpt-* markers; spec coverage measurement; ID search/navigation; init/bootstrap; adapter + registry discovery; auto-configuration of brownfield projects (scan conventions, generate rules); kit management (install/update with file-level diff); TOC generation; agent integrations (Windsurf, Cursor, Claude, Copilot, OpenAI). Kit sdlc: Artifacts: ADR, CODEBASE, DECOMPOSITION, DESIGN, FEATURE, PR-CODE-REVIEW-TEMPLATE, PR-REVIEW, PR-STATUS-REPORT-TEMPLATE, PRD; Workflows: migrate-openspec, pr-review, pr-status.

picasso

The ultimate frontend design and UI engineering skill. Use this whenever the user asks to build, design, style, or improve any web interface, component, page, application, dashboard, landing page, artifact, poster, or visual output. Covers typography, color systems, spatial design, motion/animation, interaction design, responsive layouts, sound design, haptic feedback, icon systems, generative art, theming, React best practices, and DESIGN.md system generation. Also use when the user asks to audit, critique, polish, simplify, animate, or normalize a frontend. Triggers on any mention of "make it look good," "fix the design," "UI," "UX," "frontend," "component," "landing page," "dashboard," "artifact," "poster," "design system," "theme," "animation," "responsive," or any request to improve visual quality. Use this skill even when the user does not explicitly ask for design help but the task involves producing a visual interface.

signum

Use when the user wants a contract-first implementation workflow, asks to define correctness before coding, wants multi-stage execution with verification and audit, or needs a proof-style artifact for a code change. Codex should run a CONTRACT -> EXECUTE -> AUDIT -> PACK pipeline.

Artifacts — Serving Interactive Web Content

ui-i18n

i18n pipeline for UI features developed with ui-develop. Adds internationalization to components with hardcoded strings. Automatically reads artifacts from `.ui-develop/ui-develop-{FEATURE}/` directory. Supports auto-detection of feature name.

Electrobun Build

Use when building an Electrobun app for distribution, setting up code signing, understanding platform-specific build requirements, or diagnosing build failures. Covers dev/canary/stable environments, all three platforms, toolchain prerequisites, artifact output, and CI/CD setup.

display-dev

Publishes HTML or Markdown as display.dev URLs with public, company, or private access. Supports signup, claiming, sharing, browsing, bounded reads, exact edits, and comment iteration. Use when the user asks to "publish this", "share this", "share with the org", "post this online", "make a private link", "share with [email]", "publish a report", "list my artifacts", "find an artifact", "publish a large file", "publish this generated HTML file", "read this artifact", "search inside this artifact", "change this passage", "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL. Prefer authorized bundled remote MCP, then packaged helpers or an installed dsp CLI.

brain-hydrate

Use when users want to bootstrap the brain with existing project knowledge -- reading ADRs, feature specs, UX docs, commit history, retro lessons, and error patterns to seed institutional memory on a project that already has artifacts on disk. Also use for incremental re-hydration after significant work outside the pipeline. Triggers on "hydrate brain", "bootstrap brain", "seed memory", "brain init", "populate brain", "import history".

muriel

A multi-constraint solver for visual production — raster, SVG, web, interactive, video, terminal, density viz, gaze, science, infographics, diagrams across eleven output channels plus dimensions + style-guides cross-channel references. Brand tokens, 8:1 contrast rule, and dimension constants stay active at render time. Use when the user needs any visual artifact for human eyes.

kernel-analysis-vphone600

Analyze vphone600 kernel artifacts using the local symbol database and XNU source tree. Use when working on kernel reverse engineering, address-to-symbol lookup, release-vs-research kernel comparison, or patch analysis for vphone600 variants in this repository.

fix-buildkite-ci

Triage and fix failing Buildkite CI checks for RisingWave pull requests by extracting concrete failing tests, diffs, and error messages from Buildkite build/job logs and artifacts, then applying focused code or test fixes. Use when users ask to diagnose red Buildkite checks, investigate flaky/failing CI jobs, understand why a Buildkite build failed, or provide Buildkite/GitHub check URLs and want a concrete fix.

leanspec-development

Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec. Use when contributing code, fixing bugs, setting up dev environment, running tests or linting, working with the monorepo structure, looking up build/dev/test/publish/format/lint commands, preparing releases, publishing to npm, bumping versions, syncing package versions, testing dev builds, troubleshooting npm distribution, updating changelogs, triggering CI/CD workflows, monitoring build status, debugging failed runs, managing artifacts, checking CI before releases, or researching AI agent runners. Triggers include any development, scripting, publishing, CI/CD, changelog, or runner research task in this project.

FO Semantic MCP

Semantic search over 50,000+ Dynamics 365 F&O artifacts: tables, forms, classes, and more.