Files
Jonathan Boniface f659564208 Platform scripts, MCP servers, deployment and docs for the KAB runs
- 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>
2026-11-05 22:13:25 +00:00
..

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

  1. Publish the skill to the platform's catalog, at an exact version. This hasn't been done yet.
  2. Pin it in the agent's agent.yaml, such as shared_skills: [well-architected-azure@1.0.0].
  3. Run python -m kyndryl_agent_runtime.skills lock in the agent's folder to write shared_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.