k8s-awareness
ALWAYS check before using kubectl commands. Guide for Kubernetes-related skills.
What this skill does
# Kubernetes Skills Guide You have specialized Kubernetes debugging skills. Use these instead of raw kubectl commands for consistent, well-documented workflows. ## Decision Tree ### Skills vs Agents **Simple, single kubectl command query?** → Use `kubernetes` skill - Better than: Running raw `kubectl get pods` commands - Example: "Check pod status in production namespace" - Use when: Quick resource check, single namespace, no correlation needed **Complex investigation requiring multiple steps?** → Use Task tool with K8s agents (conserves context) - `k8s-locator` - Find and list resources across namespaces - `k8s-analyzer` - Diagnose pod/deployment issues, check logs/events - `k8s-pattern-finder` - Find patterns across resources, detect infrastructure issues - Use when: Multi-namespace investigation, pattern detection, cluster-wide issues **Specific pod crashing or failing?** → Use `k8s-debug` skill - Launches ephemeral debug container in running pod - Example: "Debug the failing pod api-gateway-xyz" ### When to Use Which Agent **Just need to find resources broadly?** → Use `k8s-locator` agent only - Lists pods, deployments, services across namespaces - Saves to /tmp for later analysis - Example: "Get all pods in production, staging, development namespaces" **Investigating single pod/service issue?** → Use `k8s-locator` + `k8s-analyzer` agents - Locator: Find relevant pods/resources - Analyzer: Diagnose health, check events, analyze logs - Example: "Debug service-b CrashLoopBackOff" **Need to find patterns or cluster-wide issues?** → Use all three: `k8s-locator` + `k8s-analyzer` + `k8s-pattern-finder` - Locator: Fetch resources from all namespaces - Analyzer: Diagnose specific pod failures - Pattern-finder: Correlate across resources, detect node issues, cascade failures - Example: "Find why multiple pods are ImagePullBackOff across namespaces" ## Available Kubernetes Tools | Type | Name | Purpose | |------|------|---------| | Skill | kubernetes | Simple queries (single kubectl command) | | Skill | k8s-debug | Launch ephemeral debug container | | Agent | k8s-locator | Find and list resources across namespaces | | Agent | k8s-analyzer | Diagnose pod/deployment issues | | Agent | k8s-pattern-finder | Find patterns, cluster-wide issues | ## When to Use Raw kubectl Only use kubectl directly when: - Running one-off commands not covered by skills - User explicitly requests a specific kubectl command - Debugging the skill itself For systematic Kubernetes work, use the specialized skills above. ## Common kubectl Commands **Covered by skills**: - `kubectl get` → Use `kubernetes` - `kubectl describe` → Use `kubernetes` - `kubectl logs` → Use `kubernetes` - `kubectl debug` → Use `k8s-debug` **Not covered yet** (use directly): - `kubectl apply`, `kubectl delete`, `kubectl edit` (destructive operations) - `kubectl port-forward`, `kubectl exec` (interactive operations) ## Authentication Check context before any kubectl operation: ```bash kubectl config current-context kubectl config view --minify ```
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.