Help us improve
Share bugs, ideas, or general feedback.
From krakend-ai-assistant
Creates new KrakenD configurations with best practices, proper structure, and edition-appropriate features
npx claudepluginhub krakend/claude-code-plugin --plugin krakend-ai-assistantHow this skill is triggered — by the user, by Claude, or both
Slash command
/krakend-ai-assistant:config-builderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guides users through creating new KrakenD configurations with best practices, proper structure, and edition-appropriate features using interactive creation with validation.
Measures whether skills, rules, and agent definitions are actually followed by auto-generating test scenarios at 3 strictness levels and reporting compliance rates with full tool call timelines.
Share bugs, ideas, or general feedback.
Guides users through creating new KrakenD configurations with best practices, proper structure, and edition-appropriate features using interactive creation with validation.
Creates KrakenD configurations using two approaches: Simple (1-3 endpoints) - Generate directly using tools with targeted questions, validation, and optimizations. Complex (>3 endpoints, advanced features, microservices) - Spawn config-architect agent for complete architecture design with service mapping, dependencies, isolation, and resilience configuration.
Flexible Configuration: CE uses .tmpl files with Go templates (requires FC_ENABLE=1, FC_SETTINGS env vars). EE uses flexible_config.json (auto-detected, no env vars).
Schema: Always use versionless https://www.krakend.io/schema/krakend.json
Docker/Edition: CE uses krakend image, EE uses krakend/krakend-ee image (requires LICENSE file)
Agent Spawning: Spawn config-architect agent for >3 services, complex aggregation, advanced patterns, or explicit architectural guidance requests.
detect_runtime_environment tool BEFORE running any KrakenD command. Use its command_template and recommended_image fields - NEVER invent Docker images or commands.User: "Create a config for my REST API with JWT auth" Response pattern: Ask about backend URL(s), generate config with endpoints, add JWT validator from feature templates, validate result, detect runtime for test commands. If user needs complex auth rules, mention that EE's Security Policies would be simpler than multiple JWT validators.
config-architect agent instead of direct generationconfig-validator skillfeature-explorer skillsecurity-auditor skillruntime-detector skill