skill-compliance-auditor

Measure trigger-compliance of skills in the pmo-platform catalog across strictness levels.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/cody-hutson/pmo-platform --skill skill-compliance-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-compliance-auditor
Source: https://github.com/cody-hutson/pmo-platform/tree/main/core/skills/skill-compliance-auditor
Command: npx skills add https://github.com/cody-hutson/pmo-platform --skill skill-compliance-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies whether the correct skills are triggered for the intended requests, closing the gap between output quality and structural audits.

Core Features & Use Cases

  • Trigger Compliance Measurement: Evaluates if the right skill is triggered for the requests it should serve.
  • Scenario-based Testing: Runs scenarios at three strictness levels (explicit, neutral, competing) to ensure skill triggering.
  • Compliance Reporting: Reports compliance rates and identifies potential issues with skill descriptions or trigger surfaces.
  • Use Case: For a PMO practitioner, use this Skill to ensure that the correct skills are being triggered for daily status updates, RAID Log maintenance, and stakeholder communications.

Quick Start

Run the skill-compliance-auditor to measure trigger compliance for the skill 'daily-status'.

Frequently Asked Questions about skill-compliance-auditor

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

FAQPage Schema
How do I measure trigger compliance for skills in a PMO platform catalog?

Trigger compliance measurement evaluates if the correct skill fires for intended requests by running scenarios at explicit, neutral, and competing strictness levels. It classifies traces and reports compliance rates to identify potential issues with skill descriptions.

Why does the wrong skill trigger for my daily status update requests?

The wrong skill may trigger due to issues with skill descriptions or trigger surfaces. Running scenario-based compliance audits at neutral and competing strictness levels classifies these traces to isolate where the trigger logic fails.

What is the best way to audit skill trigger surfaces for stakeholder communication tasks?

The best way to audit trigger surfaces is running scenario-based tests across explicit, neutral, and competing strictness levels. This measures trigger compliance rates and identifies structural gaps between output quality and skill descriptions.

Can I test trigger compliance using different strictness levels for RAID Log maintenance?

Yes, you can test trigger compliance by running scenarios at explicit, neutral, and competing strictness levels. This evaluates whether the correct skill fires for RAID Log maintenance requests and reports the overall compliance rate.

When do I need to run a trigger compliance audit for my PMO skills?

You need a trigger compliance audit when ensuring the correct skills fire for daily status updates, RAID Log maintenance, and stakeholder communications. It closes the gap between output quality and structural audits by evaluating trigger accuracy.

How do I fix skill trigger compliance issues after identifying failed traces?

Failed traces identify potential issues with skill descriptions or trigger surfaces. You fix compliance issues by adjusting the trigger surfaces of the incorrectly firing skills and re-running the scenario-based compliance measurement.