AGENT SKILL
kubernetes-platform-reviewer
Describe what this skill helps an agent do.
- License 许可
- MIT
- 所属仓库
- domehahn/skil
- 最近更新
- 2026-11-11
- Stars
- ★ 1
- Forks
- 2
01 前言 Front Matter
- name
- kubernetes-platform-reviewer
- since
- 2026-07-28
- authors
- [ "platform-engineering" ]
- version
- 0.1.0
- replaces
- null
- changelog
- [ { "date": "2026-07-28", "change": "Initial generated production-ready SDLC / DevSecOps skill", "version": "0.1.0" } ]
- stability
- experimental
- supersedes
- []
- description
- Describe what this skill helps an agent do.
- last_modified
- 2026-07-28
- deprecated_since
- null
- min_platform_version
- { "pi": "unknown", "bob": "unknown", "kimi": "unknown", "kiro": "unknown", "qwen": "unknown", "cline": "unknown", "codex": "unknown", "crush": "unknown", "iflow": "unknown", "junie": "unknown", "qoder": "unknown", "auggie": "unknown", "cursor": "unknown", "lingma": "unknown", "ollama": "unknown", "factory": "unknown", "amazon-q": "unknown", "continue": "unknown", "costrict": "unknown", "kilocode": "unknown", "opencode": "unknown", "roo-code": "unknown", "windsurf": "unknown", "codebuddy": "unknown", "forgecode": "unknown", "openhands": "unknown", "gemini-cli": "unknown", "gitlab-duo": "unknown", "antigravity": "unknown", "claude-code": "unknown", "github-copilot": "unknown" }
02 资源文件 9
- 资产文件assets/README.md149 B
- 参考文档CHANGELOG.md49 B
- 许可证LICENSE214 B
- 参考文档README.md404 B
- 参考文档references/README.md182 B
- 脚本scripts/README.md217 B
- 参考文档skill.yaml244 B
- 参考文档tests/README.md104 B
- 其他VERSION6 B
03 SKILL.md 正文
Kubernetes Platform Reviewer
Purpose
Review clusters, namespaces, RBAC, NetworkPolicies, Pod Security, admission controllers, resource limits, secrets, ingress, multi-tenancy, and upgrade readiness. Treat regulatory, security, and operational references as review and evidence guidance, not legal advice.
When to use
- Kubernetes platform decisions, controls, or operating practices need independent review.
- A change affects Kubernetes platform artifacts such as cluster baseline, namespace model, RBAC binding, NetworkPolicy, Pod Security setting, admission controller.
- The user needs evidence-oriented findings for risks such as cluster-admin sprawl, namespace escape, missing network isolation, privileged pod, unbounded resource use, stale cluster version.
- Audit, security, operations, or platform stakeholders need a concise readiness position.
- Existing documentation, tickets, tests, or logs must be turned into actionable remediation items.
Operating model
- Identify the relevant Kubernetes platform artifacts, owners, systems, environments, and review boundary.
- Compare the available artifacts against expected signals such as kubectl manifest, policy report, secret reference, ingress rule, resource quota, upgrade plan.
- Separate confirmed gaps from assumptions, missing evidence, and advisory improvement opportunities.
- Rate findings by operational, security, compliance, customer, and auditability impact.
- Recommend minimal remediation steps, validation evidence, owners, and review cadence.
Spec-Driven Change Context
- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.
- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal/design/tasks record before implementation begins.
- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.
- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.
- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.
- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.
- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal/spec/tasks outline instead of relying on chat-only intent.
Skill-Specific Review Scope
- Primary artifacts: cluster baseline, namespace model, RBAC binding, NetworkPolicy, Pod Security setting, admission controller.
- Risk themes: cluster-admin sprawl, namespace escape, missing network isolation, privileged pod, unbounded resource use, stale cluster version.
- Evidence signals: kubectl manifest, policy report, secret reference, ingress rule, resource quota, upgrade plan.
- Ownership, approvals, review cadence, exception handling, and residual-risk decisions.
- Traceability from requirement or control intent to implementation, validation, and retained evidence.
Skill-Specific Checklist
- [ ] Confirm the review boundary covers the right Kubernetes platform systems, teams, and environments.
- [ ] Inventory and inspect the current cluster baseline.
- [ ] Check whether namespace model is current, approved, versioned, and owned.
- [ ] Verify that RBAC binding has test, ticket, log, or approval support.
- [ ] Look for cluster-admin sprawl and record concrete repository or process evidence.
- [ ] Look for namespace escape and identify affected assets, services, or stakeholders.
- [ ] Look for missing network isolation and classify the operational or audit impact.
- [ ] Use kubectl manifest to validate that the control or practice is operating.
- [ ] Use policy report to confirm ownership, timing, and reproducibility.
- [ ] Check exception, risk-acceptance, and expiry handling for Kubernetes platform.
- [ ] Confirm remediation items have owners, due dates, validation steps, and evidence expectations.
- [ ] Identify missing artifacts separately from weak artifacts so the next action is unambiguous.
- [ ] Review whether logging, reporting, or retained evidence exposes sensitive data unnecessarily.
Decision Rules
- If cluster baseline is missing for a critical service, raise at least a high-severity readiness gap.
- If policy report cannot be tied to an owner and approval, treat the outcome as unauditable until corrected.
- If NetworkPolicy is present but expired or untested, require validation before accepting residual risk.
- If the only support is verbal or chat-only context, request durable ticket, document, log, or test evidence.
- If remediation would require a process or architecture decision, assign a decision owner instead of prescribing legal conclusions.
- If compensating measures reduce likelihood but not impact, keep the residual-risk statement explicit.
Finding Categories
- Missing or stale Kubernetes platform artifact.
- Unclear ownership, approval, review cadence, or accountability.
- Insufficient validation, test proof, logs, ticket trail, or retained audit material.
- Unreviewed exception, residual risk, expiry, or compensating measure.
- Policy, architecture, operational, or platform implementation drift.
- Sensitive-data exposure in logs, reports, prompts, artifacts, or evidence packages.
Severity Guidance
- Critical: a gap in Kubernetes platform creates immediate outage, data-loss, privilege, regulatory-reporting, or irreversible business risk.
- High: cluster baseline is missing, unowned, untested, or unauditable for a critical service or material change.
- Medium: namespace model exists but is stale, incomplete, inconsistently enforced, or weakly evidenced.
- Low: wording, metadata, formatting, link freshness, or minor traceability improvements are needed.
DevSecOps Guardrails
- Do not read secrets,
.envfiles, private keys, production credentials, masked CI/CD variables, database dumps, or sensitive logs unless explicitly required. - Do not push, deploy, publish, merge, or create releases unless explicitly asked.
- Prefer merge requests, reviewable diffs, and auditable validation evidence.
- Prefer least privilege, minimal changes, and explicit rollback notes.
- Do not fabricate test results, repository state, commands, security findings, or validation outcomes.
- Report assumptions, uncertainty, residual risk, and validation gaps clearly.
Output Requirements
- Findings ordered by severity with affected Kubernetes platform artifacts and evidence references.
- Coverage note for reviewed artifacts: cluster baseline, namespace model, RBAC binding, NetworkPolicy, Pod Security setting, admission controller.
- Risk note covering relevant themes: cluster-admin sprawl, namespace escape, missing network isolation, privileged pod, unbounded resource use, stale cluster version.
- Evidence request list using expected signals: kubectl manifest, policy report, secret reference, ingress rule, resource quota, upgrade plan.
- Deliverables or updates needed: Kubernetes platform review, RBAC and tenancy findings, policy remediation list, upgrade readiness notes, runtime hardening recommendations.
- Residual-risk, assumptions, missing-context, and validation-gap summary.
Acceptance Criteria
- Relevant Kubernetes platform artifacts are identified, current, owned, and versioned where applicable.
- Each high-impact finding includes evidence, impact, likelihood, owner, and remediation guidance.
- Missing evidence is separated from failed controls or weak implementation.
- Exceptions and risk acceptances include owner, rationale, expiry, and compensating measures.
- Recommendations are review-oriented and avoid presenting regulatory interpretation as legal advice.
- Final output states pass, conditional pass, or blocked readiness with validation gaps.
Anti-Patterns
- Treating a policy title or control name as proof that the practice operates effectively.
- Collapsing missing evidence and failed implementation into one vague finding.
- Accepting open-ended exceptions without owner, expiry, impact, likelihood, and compensating measures.
- Making legal, regulatory, or audit conclusions beyond the available evidence and review scope.
- Recommending broad process rewrites when a targeted owner, test, ticket, or evidence fix is enough.
- Copying sensitive production data into examples, evidence packages, prompts, or reports.
Changelog
0.1.0 - 2026-07-28
- Initial generated production-ready SDLC / DevSecOps skill.