copilot_dev/.github/skills/engineering/devops-cloud/aks/SKILL.md
# AKS Troubleshooting ## When to use - AKS node pool issues, scheduling problems, cluster upgrades/regressions - Azure-related failures (identity, networking, load balancer) - You need a structured AKS-first diagnostic path ## Workflow 1) Confirm AKS context: - subscription, resource group, cluster name, node pool 2) Cluster access and basic health: - `az aks show -g <rg> -n <cluster> -o table` - `kubectl get nodes` 3) Node pool focus: - node readiness, capacity, taints, pressure
npx skillsauth add nist0/copilotdev-tmp-consumer copilot_dev/.github/skills/engineering/devops-cloud/aksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
az aks show -g <rg> -n <cluster> -o tablekubectl get nodeskubectl rollout undo, helm rollback, revert image tagtools
# Tech Watch (Weekly Digest) ## When to use - You want a weekly digest on selected topics (dotnet, k8s/aks, observability, security, LLM tooling). ## Workflow 1) Define topics and priority order. 2) Collect primary sources (release notes, official docs, papers). 3) Summarize: what changed + why it matters. 4) Propose 1–3 experiments to try next week. ## Outputs - Weekly digest (Markdown) - Experiments list (1–3) with expected payoff - Source list (primary preferred)
development
# Innovation Sprint ## When to use - You need new ideas or alternative designs. - You want a short, structured ideation session. ## Workflow 1) Clarify constraints and success criteria. 2) Generate 8–12 ideas quickly (no filtering). 3) Cluster similar ideas and pick top 3. 4) For top 3: define value, feasibility, risks, and a 1–2h spike plan. ## Outputs - Idea list - Top 3 shortlist + tradeoffs - Spike plan for each shortlisted idea
tools
# VS Code (Copilot Dev Framework Usage) ## When to use - You need to ensure Copilot Dev Framework is loaded correctly in VS Code. - You want best practices for working with prompts, agents, and skills. ## Workflow 1) Bootstrap integration - run `copilot_dev/bootstrap/bootstrap.ps1` or `.sh` 2) Reload - Reload window after bootstrap 3) Discoverability - use `/route` to select agent/prompt/skill - verify prompts appear in the slash command list 4) Multi-root workspaces - ensure
tools
# Postman (API Collections) ## When to use - You want repeatable API request collections with environments. - You want to validate API contract behavior manually or in CI. ## Workflow 1) Organize collections by domain 2) Use environments for base URLs and auth tokens 3) Add tests - status code assertions, schema checks where possible 4) Documentation - include examples and descriptions 5) Version control - export collections; keep in repo if required ## Outputs - Collection struct