gamekit-cli
Capture game view screenshots for visual verification
audit-references
Use when literature notes exist and need citation verification, or before publishing any artifact that cites literature
accessibility-checklist
WCAG AA accessibility checklist and verification protocols for Somali dialect classifier dashboard. Covers keyboard navigation, screen readers, color contrast, ARIA labels, and accessibility testing procedures.
beautify-decoration
Iterate on the visual identity of a top-down pixel-art decoration (sprite + layout integration) in pixtuoid. Use when redesigning an existing decoration (pantry, lounge, meeting room, cubicle decor) or adding a new one. Captures the rebuild trap, the visual-verification loop, resolution constraints, sprite-format pitfalls, and the layout-integration checklist that we learned the hard way during the pantry beautify session.
Io.Github.IncodeTechnologies/Incode Idv Mcp
MCP server for Incode IDV, providing identity verification tools for AI assistants.
nightshift-release
Release a new version of the nightshift Go project using goreleaser. Use when the user asks to cut a release, push a new version, bump the version, publish a release, or verify a release succeeded. Covers version bumping, git tagging, goreleaser dry-run validation, pushing, and post-release verification via GitHub Actions and `gh`.
zen-verification
Verify Zen's provider-neutral Brain and Worker control plane from the real CLI. Use when a change needs a bounded runtime preflight tied to source and tests.
sinch-authentication
Configures Sinch API credentials and authentication. Use when setting up OAuth2, Basic auth, application signing, API keys, or SDK credentials for any Sinch product including Conversation API, Voice, Verification, Numbers, Fax, and Mailgun. Also use when troubleshooting 401 Unauthorized, 403 Forbidden, invalid signature, or credential errors against any Sinch API.
Io.Github.0xbrainkid/Agentfolio
Query AI agent profiles, trust scores, verifications, and marketplace jobs on AgentFolio.
Auto Create PR (loop)
Turn a free-form brief into an execution plan, implement it **one commit per Step** in an isolated worktree, batch verification proofs at checkpoints, keep a live handoff doc and append-only notification log, and open a labeled PR against the configured base branch.
kn-commit
Use when committing code changes with proper conventional commit format and verification
analytics-tracking-automation
Use when you need end-to-end GA4 + GTM tracking delivery across discovery, schema, sync, and verification phases.
Curate-Ipsum
Code synthesis through belief revision, mutation testing, and verification
chargebee-webhooks
Receive and verify Chargebee webhooks. Use when setting up Chargebee webhook handlers, debugging Basic Auth verification, or handling subscription billing events.
CORAL debug & change-verification workflows
This skill is for people (and Claude Code) hacking on the CORAL package itself, not for users authoring a task. For authoring guides see the siblings: - `coral-new-task` â creating a new `examples/<task>/` (seed + task.yaml + grader) - `coral-extend` â extending CORAL itself (new runtime, new CL
skillboss
Multi-AI gateway for fullstack apps. Build/deploy websites, React apps, SaaS, ecommerce to Cloudflare Workers. DB (D1/KV/R2), Stripe payments/subscriptions/checkout, auth (login, OAuth, OTP), AI image/audio/video/TTS generation, UI generation (Google Stitch), email, presentations/slides, web scraping/search, CEO interviews/quotes, document parsing/extraction, SMS verification, serverless deploy/API/webhook.
ac-verify
Lightweight single-pass AC verification before Archive â run implementation against each AC, produce pass/fail evidence. FAIL blocks Archive and rolls back to Phase 4. Mutually exclusive with ultraqa: choose ac-verify when AC count ⤠3 AND risk â HIGH; otherwise use ultraqa. See .claude/rules/skill-precedence.md Zone C.
Io.Github.IntelagentStudios/Mcp Enrichment
Multi-source entity enrichment: company data, contacts, email verification, and phone validation
bug-triage
Reproduce, isolate, and fix a bug (or failing build/test), then summarize root cause, fix, and verification steps. Use when the user reports a bug, regression, or failing build/test and wants a fix.
context-modes
Structured work modes for agent sessions. Set LACP_CONTEXT_MODE to activate: tdd (red-green-refactor), debugging (4-phase root cause), sprint (pre-agreed criteria), verification (evidence-before-claims), brainstorm (design first), think (pause-and-reflect), orchestrate (task decomposition). Each mode injects behavioral rules at session start.
houtu-dependencies
houtu-dependencies enterprise-grade Spring Cloud microservice foundational framework complete usage guide. GroupId is io.github.lujiafa, covering unified response, exception handling, parameter parsing, session authentication, permission control, signature verification, anti-replay, distributed lock, rate limiting, database field encryption, config decryption, access logging, canary routing, weighted load balancing, Feign enhancement, Sentinel circuit breaking, service discovery, Swagger documentation, crypto utilities, HTTP client, monitoring metrics, and other enterprise-grade capabilities. When the project build file (pom.xml or build.gradle/build.gradle.kts) contains io.github.lujiafa or houtu-related dependencies, or when the user mentions houtu or houtu-dependencies, this Skill must be read and code must be generated strictly following framework conventions. Even if the user is simply doing regular Spring Boot development (e.g., writing Controller, Service, Feign), as long as the project includes houtu, the houtu approach must be used instead of native Spring. When the user explicitly wants to use the houtu framework and the project has not yet included it, proactively add the BOM and required Starters; when the project already includes it, proactively identify and import required module dependencies based on business scenarios during coding, naturally integrating framework capabilities to enhance business services based on business semantics, rather than waiting for the user to specify each one.
developing-with-fortify
Laravel Fortify headless authentication backend development. Activate when implementing authentication features including login, registration, password reset, email verification, two-factor authentication (2FA/TOTP), profile updates, headless auth, authentication scaffolding, or auth guards in Laravel applications.
app-design-thinking (doc-verification override)
For doc-verification projects the runtime shape is locked. John core's `app-design-thinking` is co-authored, taste-driven, open-ended; this template narrows it because the kc_cli methodology only ships one product archetype: a doc-verifier with the pipeline below. Per-project customization happens *
Lumen Deploy Check
Full verification across the monorepo before merging or deploying.
executor
Focused implementation mode for one planned slice with explicit verification and handoff.
update-upstream-sdk
Update the hs-temporal-sdk project against the upstream Rust core SDK (temporalio/sdk-core). Covers revision bumps, Rust compilation, C header regeneration via bindgen, Haskell FFI bridge updates, protobuf regeneration, SDK module propagation, and nix build verification across GHC versions. Use when updating, bumping, syncing, or upgrading the upstream Temporal SDK dependency.
home-assistant-manager
Expert-level Home Assistant configuration management with efficient deployment workflows (git and rapid scp iteration), remote CLI access via SSH and hass-cli, automation verification protocols, log analysis, reload vs restart optimization, and comprehensive Lovelace dashboard management for tablet-optimized UIs. Includes template patterns, card types, debugging strategies, and real-world examples.
Pre-Commit Code Verification
Automated verification pipeline before code lands. Static scans, baseline-aware quality gates, an independent reviewer subagent, and an auto-fix loop.
acquiring-disk-image-with-dd-and-dcfldd
Create forensically sound bit-for-bit disk images using dd and dcfldd while preserving evidence integrity through hash verification.
Code Gauntlet
Concern-parallel agents with context-pulling and deterministic verification. When in doubt about whether something is a real issue, err on the side of not reporting it. A review with 5 real issues is far more valuable than one with 5 real issues buried in 20 false positives.
climpred-forecast-verification
Verify weather and climate forecasts using climpred. Use when computing forecast skill metrics (RMSE, ACC, CRPS, etc.), comparing hindcasts to observations, bootstrapping significance, removing bias, or working with HindcastEnsemble/PerfectModelEnsemble objects. Triggers on: forecast verification, prediction skill, hindcast, climate prediction, skill score, predictability.
Verified Repo Memory
Stale-proof repository memory with citations + just-in-time verification + TTL (repo-scoped).
SettlementWitness
Deterministic verification gate for agent execution and x402 settlement.
runtime-version-check
Research and verify the latest versions of programming language runtimes (Node, Bun, Deno, Python, Go, etc.) using a two-phase verification process that prioritizes accuracy over speed.
Io.Github.Helm Protocol/Openttt Pot
Proof-of-Time transaction ordering verification for AI agents. 5 MCP tools.
symbiont
AI-native agent runtime with typestate-enforced ORGA reasoning loop, Cedar policy authorization, CommunicationPolicyGate for inter-agent governance, ToolClad declarative tool contracts, knowledge bridge, zero-trust security, multi-tier sandboxing, webhook verification, markdown memory, skill scanning, metrics, scheduling, symbi init/run/up CLI, and a declarative DSL
add-agent-target
Use when adding support for a new AI agent target to agentsmesh. Covers official format research, canonical mapping, importer/generator/linter work, realistic fixtures, unit/integration/e2e coverage, matrix/docs updates, and final verification. Includes both project and global mode from day one.
pi-statusbar-release
End-to-end release workflow for pi-statusbar, including mode selection, version/tag releases, formula-only revisions, tap sync, and post-release verification.
Com.636865636b73756d/Mcp V1
Sub-cent factual claim verification against live data sources.
specrail-diagnose-ci
Use when diagnosing or fixing CI failures in a SpecRail-governed repository. Collects fresh CI evidence, reproduces failures locally when possible, identifies root cause before fixing, and reports verification without claiming green CI from stale or missing data.
playwright-best-practices
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
code-change-verification
Verify code changes by identifying correctness, regression, security, and performance risks from diffs or patches, then produce prioritized findings with file/line evidence and concrete fixes. Use when reviewing commits, PRs, and merged patches before/after release.
brigade-work
Brigade only earns its keep if real work flows through it. Installed and never used, it is dead weight: the daily brief is empty, the outcome ledger never fills, and `outcome rank` says "ranking: none". This skill is the loop that feeds it. Check what is pending, run your verification *through* Brig
workflow-orchestration
Disciplined task execution with planning, verification, and self-improvement loops. Use when starting non-trivial tasks (3+ steps), fixing bugs, building features, refactoring code, or when rigorous execution with quality gates is needed. Includes subagent delegation, lessons tracking, and staff-engineer-level verification.
Verify Mcp
Sub-cent factual claim verification against live data sources.
Mcp Server
Browse property verification missions. Connect with Scouts for GPS-verified tours.
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.
orka-kind-deploy
Rebuild and redeploy the Orka controller and all worker images into a local kind cluster from an Orka repository checkout. Use when the user asks to rebuild Orka, redeploy all components, refresh the local cluster after code changes, or roll out the full local stack for verification.
change-verification
Use after code or configuration changes to prove the changed behavior with minimal sufficient commands, HTTP/browser checks, or static evidence. DO NOT USE FOR: purely speculative review without a concrete change.
firestore-better-auth
Use Firestore as the database adapter for Better Auth (Firebase Admin SDK). Use when storing Better Auth users, sessions, accounts, and verification tokens in Firestore, migrating from Auth.js/NextAuth Firebase adapter to Better Auth, setting up Better Auth with a Firebase/Firestore backend, or troubleshooting Firestore index errors and FIREBASE_PRIVATE_KEY issues.