CI/CD

Conduct comprehensive, systematic literature reviews using multiple databases (PubMed, bioRxiv, Semantic Scholar, OpenAlex). Creates documented searches, synthesizes findings thematically, verifies citations, and generates professional markdown reports with multiple citation styles (APA, Nature, Vancouver). Use when the user needs thorough literature research or types /deep_research.

Use the screenshot workflow to pick, verify, replace, and verify CI.

Decision forest ensemble classifier for robust predictions

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

Clean Architecture design guide for Spring Boot. Use when reviewing code architecture, designing solutions, discussing layer separation, dependency rules, or project structure. Applies Uncle Bob's Clean Architecture principles.

GitHub workflow patterns for Orchestrator AI. Branch naming, PR process, code review, CI/CD. CRITICAL: Use conventional branch names (feature/, fix/, chore/). PRs require quality gates to pass. Use GitHub Actions for CI/CD.

Python development best practices, patterns, and conventions. Use when writing Python code, reviewing .py files, discussing pytest, asyncio, type hints, pydantic, dataclasses, or Python project structure. Triggers on mentions of Python, pytest, mypy, ruff, black, FastAPI, Django, Flask.

Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges

Core architecture principles (SSOT, DRY, Anti-Spaghetti) for maintainable code design. Use when planning features, implementing code, or reviewing architecture to prevent duplication and technical debt.

Deploys applications to Vercel including serverless functions, edge functions, environment variables, and CI/CD. Use when deploying Next.js applications, frontend projects, or serverless APIs.

Guide for spec-based agent-driven development using structured requirements (EARS notation), technical design documentation, and implementation planning. Use when users want to build features using a specification-first approach, need to document requirements formally, want to generate implementation plans from specs, or when working on projects that benefit from clear requirement-to-code traceability.

Creates BDD feature files for Golang Clean Architecture projects using Gherkin syntax. Use when users need to write .feature files for integration tests, create test scenarios for APIs, or generate Cucumber/Godog test specifications. Specifically for projects that follow Clean Architecture patterns with existing step definitions.

General documentation standards for README, AsciiDoc, and technical documentation

Expert knowledge of Docker containerization including Dockerfile best practices, docker-compose configuration, Alpine Linux specifics, multi-stage builds, security, health checks, and container optimization. Use when working with Dockerfile, docker-compose.yml, container builds, debugging container issues, or deploying to container platforms.

Customer-facing documentation

Design and implement RESTful API endpoints following REST principles with proper HTTP methods, status codes, and URL conventions. Use this skill when creating or modifying API routes, route handlers, API endpoint files, controller files that handle HTTP requests and responses, or any server-side files that define RESTful endpoints. Use this when working on API versioning, implementing rate limiting, designing resource-based URLs, handling query parameters for filtering/sorting/pagination, or structuring nested resource endpoints. Use this when writing code in files like routes.js, api.js, controllers/, handlers/, endpoints/, or any file that defines HTTP API routes and responses.

Surgeon Captain - Master debugger, problem diagnostician, and fix validator

Update the repository root ChangeLog and keep the root release version metadata in sync. Use when updating the root version or syncing subsystem/package version lists in ChangeLog; touches ChangeLog at repo root and the release version in rebar.config. If you are not sure which changelog-* skill to read, read this first.

Specialized skill for designing AWS DynamoDB single-table schemas with optimized access patterns. Use when modeling data, designing table structure, or optimizing DynamoDB queries for production applications.

Systematic debugging approach using parallel investigation and test-driven validation. Use when debugging issues, when stuck in a loop of trying different fixes, or when facing complex bugs that resist standard debugging approaches.