mcpField
C
compliance-evidence-room-review

compliance-evidence-room-review

github.com/sylphxaiSecurity140 installsUpdated today
Repository

About compliance-evidence-room-review

A skill for turning compliance evidence-room questions into plans for document access, approvals, expiry, audit trails, and buyer or security workflows. It defines ownership, controls, and escalation for stale evidence.

Key features

  1. 01Classifies compliance evidence
  2. 02Defines document metadata and access
  3. 03Plans approvals, expiry, and watermarking
  4. 04Establishes audit trails and update cadence
  5. 05Creates stale-document escalation

Use cases

  1. 01Designing a gated evidence room
  2. 02Managing buyer security reviews
  3. 03Controlling access to audit reports
  4. 04Handling expired compliance documents

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill compliance-evidence-room-review

After installing, type/compliance-evidence-room-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/compliance-evidence-room-patterns.md

Details

From the project README

Compliance Evidence Room Review

Use this skill to convert a compliance evidence rooms, gated documents, approvals, expiry, audit proof, and buyer security review question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify evidence consumers, document types, sensitivity, access rules, approval owners, expiry dates, NDA/terms path, and buyer workflow.
  2. Read references/compliance-evidence-room-patterns.md.
  3. Classify evidence as public summary, gated report, contract document, audit artifact, policy, subprocessor record, or customer-specific exception.
  4. Define document metadata, access control, watermark/expiry policy, audit trail, update cadence, request handling, and sales/security handoff.
  5. Produce evidence room plan, state machine, decision table, event schema, access checklist, and stale-document escalation.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not share SOC reports, pentests, architecture diagrams, or customer evidence by email when gated access is required.
  • Do not keep expired or superseded compliance documents available without warning.
  • Do not grant evidence access without requester identity, purpose, terms, expiry, and audit trail.
  • Do not let sales upload unapproved documents or alter evidence scope.

Output format

Evidence room context:
Consumer / document sensitivity / access boundary:

Evidence room plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Documents, metadata, and access rules:
- <item> -> <policy, metric, edge case, support note>

Expiry, revocation, and stale-document handling:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported