Agent skill · magnus919
cncf-landscape
Use this skill when discovering and comparing cloud-native technologies from the CNCF Landscape for an architecture or engineering decision. Query the live public Landscape API, filter candidates by capability, category, maturity, license, and repository signals, then produce an evidence-backed shortlist with trade-offs, unknowns, and validation steps. Do not use it as a substitute for project documentation, production-readiness testing, legal review, or general architecture methodology.
What it needs
About 4k tokens when loaded.
What this skill does
CNCF Landscape technology selection Use this skill to turn a capability or architecture problem into a defensible shortlist of cloud-native technologies. The Landscape is a discovery and evidence source, not a recommendation engine. When to load Load this skill when someone: asks what projects or tools exist for a capability that is not in the current stack; wants to compare CNCF projects by maturity, category, repository signals, license, or ecosystem evidence; asks for a shortlist for an architecture decision, proof of concept, technology radar entry, or build-versus-buy discussion; needs to discover a CNCF project before reading its documentation or source repository. When not to use For operating or configuring a named technology, load its operational skill or use its authoritative documentation. For the general adoption/hold governance process, load technology-radar and use this skill only for candidate discovery and evidence. For broad platform architecture, data architecture, or API design without a Landscape discovery question, use the matching methodology skill. For procurement, contract, export-control, or licensing advice, treat this skill's license fields as discovery evidence and obtain qualified review. Decision workflow 1. Frame the decision before searching. Capture the capability, workload, interfaces, runtime and topology, scale and SLOs, data sensitivity, deployment model, team ownership, operational skills, budget, timeline, license constraints, and acceptable maturity risk. Separate hard constraints from preferences. If the user has not supplied these, ask for the smallest missing set rather than pretending that a category name is a requirement. 2. Discover candidates from the live API. Start with the bundled query tool: Load references/api.md when selecting an endpoint, interpreting a field, or diagnosing a response. Use the projects source for technology candidates. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/cncf-landscape