Some checks failed
check agents / check (push) Failing after 12s
azure-discovery, aws-discovery and gcp-discovery collect read-only metadata on servers, workloads, Kubernetes clusters, networks, data stores, policies and provider recommendations. Credentials arrive per call from the vault. Replies are paged, scrubbed of secrets and anonymised, and throttled calls back off. cloud-knowledge searches each provider's Well-Architected guidance from fixed lists only, so no customer detail can leave the platform. Adds shared skills, the render and test tooling, a public Python Dockerfile until the hardened base image is reachable, the customer access guide, the implementation plan and the Vault Service platform issue. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Shared skills
Well-Architected guidance for KAB agents, one skill per hyperscaler. Each is a summary in Kyndryl's words plus how to apply it to discovery evidence. It needs no credential and no network call.
| Skill | Framework |
|---|---|
| well-architected-azure | Azure Well-Architected Framework |
| well-architected-aws | AWS Well-Architected Framework |
| well-architected-gcp | Google Cloud Well-Architected Framework |
Using one
- Publish the skill to the platform's catalog, at an exact version. This hasn't been done yet.
- Pin it in the agent's
agent.yaml, such asshared_skills: [well-architected-azure@1.0.0]. - Run
python -m kyndryl_agent_runtime.skills lockin the agent's folder to writeshared_skills.lock.
Sub-agents can't load skills. In the sub-agent pattern, the orchestrator loads them.
Keeping them current
No owner has been agreed yet. Compare each skill with its framework at every published version, and whenever the framework's pillars change. The pillar names were checked against the providers' own pages on 2026-10-30.