compliance-matrix

Generate and update compliance matrices for each stack.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/marvelousempire/ai-skills-library --skill compliance-matrix-marvelousempire
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compliance-matrix
Source: https://github.com/marvelousempire/ai-skills-library/tree/main/skills/methodology/compliance-matrix
Command: npx skills add https://github.com/marvelousempire/ai-skills-library --skill compliance-matrix-marvelousempire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides detailed compliance snapshots for each stack, ensuring that no component drifts from the established contract, thereby maintaining adherence to label schemas, frontmatter, and doctor presence.

Core Features & Use Cases

  • Compliance snapshots: Generates detailed compliance tables for each stack.
  • Update triggers: Automatically updates upon changes to ensure no stack drift.
  • Use Case: For instance, you can use this Skill to verify that all stacks in your system comply with security standards and regulatory requirements by triggering a "compliance check".

Quick Start

Run the command compliance-matrix to initiate a compliance check.

Frequently Asked Questions about compliance-matrix

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

FAQPage Schema
What is a compliance matrix and how does it track regulatory adherence?

A compliance matrix tracks regulatory adherence by generating markdown table snapshots for each stack, verifying label schemas, frontmatter, and doctor presence to prevent component drift from established contract requirements.

How do I automate compliance checks for label schemas and frontmatter across multiple stacks?

Automate compliance checks by triggering per-stack matrix generation, which systematically verifies frontmatter formats and label schemas against defined standards to ensure no stack drifts from contract requirements.

Does the compliance matrix require specific documentation directories to function?

Yes, the compliance matrix requires the `docs/standards/` directory and `docs/improvement/recurring-wins.md` file to provide context for verifying stack adherence and generating accurate compliance snapshots.

When should I generate a compliance snapshot to verify stack security standards?

Generate a compliance snapshot when stack changes occur to automatically update the matrix, ensuring components continuously adhere to security standards, regulatory requirements, and established contract schemas without drift.

What is the best way to identify which stacks have specific compliance features like doctor presence?

Trigger a query like 'which stacks have X' to generate a compliance matrix, checking all stacks for specific features like doctor presence and label schema adherence in markdown tables.