compliance-expert

Routes cross-cutting compliance requests to focused security, privacy, and accessibility skill sets.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill compliance-expert-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compliance-expert
Source: https://github.com/pnewsam/skills/tree/main/archive/router-evicted/compliance-expert
Command: npx skills add https://github.com/pnewsam/skills --skill compliance-expert-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Compliance work often spans multiple domains at once — security, privacy, accessibility, vulnerability management — and it is unclear which guidance applies or whether a request is even in scope. This Skill acts as a router that maps a broad compliance request to the smallest relevant focused skill set and synthesizes the resulting guidance into concrete engineering controls. ## Core Features & Use Cases - Decision Rubric: Maps prompt signals (PII, CVEs, WCAG, HIPAA, audit evidence) to the right focused compliance-* or threat-model skill. - Applicability Discipline: Prevents premature GDPR/HIPAA labeling by requiring data, actors, and obligation analysis first. - Escalation Clarity: Distinguishes engineering guidance from legal advice and surfaces decisions needing legal, security, or policy owner review. - Use Case: A team building a health-data feature asks whether HIPAA applies and what controls are needed; the router directs them to compliance-hipaa plus compliance-security, then frames the legal review questions. ## Quick Start Use compliance-expert to route this request about storing EU customer data and determine which compliance obligations and controls apply.

Frequently Asked Questions about compliance-expert

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

FAQPage Schema
How do I handle a request that spans multiple compliance domains?▼

Use the router when a request touches two or more concerns such as security, privacy, and accessibility. It maps prompt signals to the relevant focused compliance-* skills and synthesizes their guidance into one coherent answer.

When should I use a single compliance skill instead of the router?▼

Go directly to one focused compliance-* skill when exactly one concern is clearly bounded, such as a pure WCAG accessibility question. The router adds value only when scope spans multiple domains or applicability is unclear.

Does this skill provide legal advice on GDPR or HIPAA?▼

No, it provides engineering guidance only. It identifies applicable controls, evidence, and escalation points, and explicitly surfaces questions that require legal, security, privacy, or policy owner review.

How do I know if GDPR or HIPAA actually applies to my feature?▼

Start by identifying the data involved, the actors, and the systems before applying any regulatory label. The skill requires an applicability review of data flows and obligations rather than assuming GDPR or HIPAA applies.

What evidence proves a compliance control actually works?▼

Evidence includes tests, scans, logs, approvals, and PR links demonstrating the control exists and functioned. The review checklist requires naming the control, the unacceptable outcome it prevents, and the proof it worked.