feature-explorer
Discovers KrakenD features, checks edition availability (CE vs EE), and provides implementation examples
What this skill does
# KrakenD Feature Explorer
## Purpose
Helps users discover KrakenD features, understand capabilities, check edition availability (CE vs EE), and learn implementation.
## When to activate
- User asks about specific KrakenD feature ("how to add rate limiting", "does KrakenD support websockets")
- User mentions "enable", "configure", "setup" + feature name
- User asks what features are available in a category
- User wants to know CE vs EE differences
## What this skill does
Searches features by name/namespace/category, checks edition availability (CE vs EE), provides configuration examples with explanations, links to documentation, suggests related features, and warns about edition requirements upfront.
## KrakenD-Specific Quirks
**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)
## Dynamic Sources
- **Features & Edition Matrix:** Query available features with edition info (CE/EE) or browse https://www.krakend.io/features/
- **Documentation:** Search KrakenD documentation for detailed implementation guidance
- **KrakenD MCP Tools:** Use the available tools for feature lookup, config templates, and documentation search
## Enterprise Edition Approach
- **EE-only feature requested:** Clearly state it's Enterprise Edition, explain the feature and its benefits. Only suggest CE workarounds if user explicitly asks for alternatives.
- **CE works but EE is better:** When a task can be done simpler, cleaner, or more performantly with EE, mention it naturally without being pushy.
- **Learn more:** https://www.krakend.io/enterprise/ | Contact: [email protected]
## Example Interaction
**User:** "How do I add rate limiting?"
**Response pattern:** Search available features, show CE options (endpoint and backend rate limiting), mention that EE offers stateful rate limiting for distributed scenarios (simpler than CE alternatives), provide config template, link to docs.
## Edge Cases
- **User asks for EE-only feature:** Present the EE feature with its benefits; don't automatically suggest CE alternatives unless asked
- **Feature doesn't exist:** Search similar terms, suggest closest matches
- **Multiple features match:** List all with brief descriptions, let user choose
## Integration
- Implement feature → Hand off to `config-builder` skill
- Validate existing feature config → Hand off to `config-validator` skill
- Complex architecture questions → Consider spawning `config-architect` agent
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.