- Scripts to run workflows from a YAML context or run inputs (kab_run_workflow.py, with --input name=@file), store per-project discovery connections, bootstrap agent MCP keys, refresh the KAB token, publish reports and build estate snapshots. - Hyperscaler discovery servers extended in place; cloud-knowledge folded into them. - deploy/crucible-kab-dev.yaml: the Discovery package agent and the Assessment agents. - Platform issue write-ups and current-wiring notes under docs/platform-issues/. 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.