agentsclimarketplace

Continuous monitoring

Skill bromso/metapowers/plugins/compliance/skills/continuous-monitoring

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install
npx -y skills add bromso/metapowers --skill continuous-monitoring

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design continuous compliance monitoring

SKILL.md

3.6 KB, 786 tokens by cl100k_base, as published. Nobody here has run it

Continuous Monitoring

Design a continuous compliance monitoring program for "$ARGUMENTS" with automated checks, dashboard metrics, alerting thresholds, and GRC tooling integration.

Prerequisites

Read .metapowers/compliance/$ARGUMENTS/00-scope.md. If this file does not exist, tell the user:

Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run /compliance:regulatory-landscape $ARGUMENTS first, or use --skip-checks to bypass.

If --skip-checks is present in $ARGUMENTS, skip this check.

Process

  1. Read context files:

    • Read plugins/compliance/shared/grc-lifecycle-guide.md for GRC methodology reference
    • Read .metapowers/compliance/$ARGUMENTS/00-scope.md for scope and applicable regulations
    • Read .metapowers/compliance/$ARGUMENTS/02-remediate.md for control mapping and evidence plan
    • Read .metapowers/compliance/$ARGUMENTS/03-certify.md for certification status

  2. Define monitoring scope:

    • For each regulation: identify checks that can be automated vs. manual
    • Automated checks: configuration scanning, access reviews, vulnerability scanning, policy acknowledgments, training completion tracking, encryption verification
    • Manual checks: policy reviews, risk assessments, vendor assessments, physical security inspections
    • Define check frequency — continuous, daily, weekly, monthly, quarterly

  3. Design automated compliance checks:

    • Configuration scanning — infrastructure-as-code compliance, cloud security posture
    • Access reviews — periodic user access certification, privileged access monitoring
    • Policy acknowledgments — employee policy acceptance tracking
    • Training completion — security awareness, role-specific training
    • Vulnerability management — scan frequency, remediation SLAs
    • Change management — deployment tracking, approval verification

  4. Dashboard metrics:

    • Compliance score per regulation (percentage of controls passing)
    • Open findings count and aging
    • Days to remediate (average, P95)
    • Evidence freshness — percentage of evidence current vs. stale
    • Control effectiveness rate — percentage of controls operating as designed
    • Trend lines — compliance posture over time

  5. Alerting and escalation:

    • Define alerting thresholds (e.g., compliance score drops below 90%)
    • Set escalation paths — who gets notified at each severity level
    • Define response SLAs for compliance alerts
    • Integration with incident management (PagerDuty, Slack, email)

  6. GRC tooling integration:

    • Assess current GRC tooling (Vanta, Drata, Secureframe, or manual)
    • Map monitoring requirements to tool capabilities
    • Identify gaps requiring custom integration or manual processes
    • Recommend tooling improvements if applicable

  7. Write the artifact to .metapowers/compliance/$ARGUMENTS/04-monitor.md with sections:

    • Monitoring Scope — automated vs. manual checks per regulation
    • Automated Checks — check descriptions, frequency, tools
    • Dashboard Design — metrics, visualizations, and data sources
    • Alerting Framework — thresholds, escalation paths, SLAs
    • GRC Tooling — current state and integration plan
    • Operational Cadence — daily/weekly/monthly compliance activities

Output

The continuous monitoring design written to .metapowers/compliance/$ARGUMENTS/04-monitor.md. Present a summary to the user highlighting:

  • Percentage of controls with automated monitoring
  • Key dashboard metrics recommended
  • Critical alerting thresholds
  • GRC tooling recommendations

Gives 0 of the 12 instructions most monitoring observability skills give in 786 tokens

Counted across 481 of the 483 authors here whose files we hold, read 2026-08-06

  • link every alert to a runbookin 43 of 481, across 35 files
  • use structured json loggingin 36 of 481, across 31 files
  • alert on user-facing symptomsin 20 of 481, across 15 files
  • emit structured JSON logs with stable event namesin 18 of 481, across 13 files
  • propagate trace context across boundariesin 16 of 481
  • use histograms for latency trackingin 14 of 481, across 9 files
  • use OpenTelemetry for distributed tracingin 13 of 481, across 8 files
  • include a correlation ID on every log linein 13 of 481, across 8 files
  • Define service level objectivesin 10 of 481, across 7 files
  • Call useAzureMonitor before importing other modulesin 9 of 481, across 2 files
  • stop and ask for clarification if inputs are missingin 9 of 481, across 2 files
  • define on-call questions before adding telemetryin 9 of 481, across 4 files

Said here and by no other author read

  • Verify Phase 0 scope exists unless skipped
  • Instruct user to run regulatory-landscape if scope is missing
  • Skip scope verification if bypass flag is present
  • Read GRC lifecycle guide and prior phase artifacts
  • Classify checks as automated or manual per regulation
  • Define check frequencies for automated and manual checks

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.