runtime-detector
Detects the optimal way to run KrakenD (native binary vs Docker) and provides correct execution commands
What this skill does
# Runtime Detector ## Purpose Determines the correct way to execute KrakenD commands by detecting available runtimes and providing ready-to-use commands with the appropriate Docker image or native binary. ## When to activate - User asks to run/start/execute KrakenD: "run krakend", "start the gateway", "execute krakend" - User mentions Docker commands for KrakenD: "docker run krakend", "which docker image" - User asks how to run their config: "how do I run this", "start my config" - User asks about KrakenD versions or images: "which version", "what image to use" ## CRITICAL: Always Use Runtime Detection **NEVER invent Docker images or commands.** Always follow this process: 1. Call `detect_runtime_environment` tool with the config file path 2. Use the `recommendations` array from the response (ordered by priority) 3. Use `command_template` from priority=1 recommendation 4. If Docker needed, use `recommended_image` field for the image name **Common hallucinations to avoid:** - ❌ `devopsfaith/krakend` (outdated) - ❌ `krakend:latest` without checking - ❌ `krakend/krakend:version` (wrong format) - ✅ Use exactly what `detect_runtime_environment` returns ## What the tool returns - `has_native_krakend`: Whether native binary is installed - `has_docker`: Whether Docker is available - `recommended_image`: Correct Docker image (e.g., `krakend:2.8` or `krakend/krakend-ee:2.8`) - `recommendations`: Array of execution options with `command_template` ready to use - `is_enterprise`: Whether config uses EE features ## Example Interaction **User:** "Run my krakend.json" **Response:** Call `detect_runtime_environment`, then provide the command from `command_template`. Explain if using native or Docker and why. ## Integration - After `config-validator` validates successfully → Offer to run with this skill - After `config-builder` creates config → Offer to test run - If user needs to validate first → Hand off to `config-validator`
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.