build-capability-catalog

Generate schema-validated FINOS CCC capability catalogs for AWS, Azure, and GCP services.

85|80|Updated Jul 26, 2023
One-click install
npx skills add https://github.com/finos/common-cloud-controls --skill build-capability-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-capability-catalog
Source: https://github.com/finos/common-cloud-controls/tree/main/skills/build-capability-catalog
Command: npx skills add https://github.com/finos/common-cloud-controls --skill build-capability-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating consistent, compliant capability catalogs for cloud services across AWS, Azure, and GCP is time-consuming and prone to errors, especially when aligning with the FINOS Common Cloud Controls (CCC) standard's taxonomy and schema requirements.

Core Features & Use Cases

  • Cross-Cloud Service Mapping: Automatically identifies equivalent cloud service offerings across AWS, Azure, and GCP for a given input service, pulling official documentation links for reference.
  • CCC Taxonomy Alignment: Automatically assigns the correct CCC category, generates compliant folder paths, and validates proposed taxonomy against existing CCC category definitions.
  • Schema-Compliant Catalog Generation: Creates validated metadata.yaml and capabilities.yaml files that map shared cross-cloud capabilities, reusing existing core CCC capabilities to avoid duplication.
  • Use Case: For example, if your team needs to onboard a new cloud service like AWS S3 to the CCC standard, this skill automates the entire catalog creation process to ensure consistency with existing FINOS CCC controls.

Quick Start

Use the build-capability-catalog skill to create a capability catalog for AWS S3.

Frequently Asked Questions about build-capability-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a FINOS CCC capability catalog for a new cloud service?

To generate a FINOS CCC capability catalog, you map equivalent cloud service offerings across AWS, Azure, and GCP to produce schema-validated metadata.yaml and capabilities.yaml files aligned with existing CCC taxonomy.

What is cross-cloud mapping for cloud controls compliance?

Cross-cloud mapping for cloud controls compliance identifies equivalent cloud service offerings across AWS, Azure, and GCP, pulling official documentation links to ensure consistent control mapping aligned with the FINOS CCC standard.

How do I ensure my cloud capability catalog aligns with CCC taxonomy and schema requirements?

To ensure your cloud capability catalog aligns with CCC taxonomy, you assign the correct CCC category, generate compliant folder paths, and validate proposed taxonomy against existing CCC category definitions and catalog schemas.

Can I reuse existing core CCC capabilities when onboarding an AWS S3 service?

Yes, when onboarding AWS S3 or other cloud services, the catalog generation process reuses existing core CCC capabilities to map shared cross-cloud functionality and avoid duplication within the FINOS CCC standard.

Does cross-cloud catalog generation work for AWS, Azure, and GCP simultaneously?

Yes, cross-cloud catalog generation works for AWS, Azure, and GCP simultaneously by automating the identification of equivalent service offerings across these three cloud providers for a given input service.

What are the limitations of automating CCC catalog creation for cloud services?

Automating CCC catalog creation is limited to mapping equivalent offerings across AWS, Azure, and GCP and relies on existing CCC taxonomy definitions, meaning custom cloud controls outside the standard schema require manual validation.