Individual skill
openrouter-compliance-review
Review OpenRouter integration for regulatory compliance (SOC2, GDPR, HIPAA). Use when preparing for audits, evaluating data handling, or documenting compliance posture. Triggers: 'openrouter compliance', 'openrouter gdpr', 'openrouter soc2', 'openrouter data residency'.
plugins/saas-packs/openrouter-pack/skills/openrouter-compliance-review/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- openrouter Declared skill tag
- compliance Declared skill tag
- security Declared skill tag
- governance Declared skill tag
- legal Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,161 bytesSKILL.mdcore · 9,161 bytesSKILL.mdcore · 9,161 bytesSKILL.mdcore · 9,161 bytesSKILL.mdcore · 9,161 bytesSKILL.mdcore · 9,161 bytesSKILL.mdcore · 9,161 bytesreferences/compliance-checklist.mddoc · 3,436 bytesreferences/data-flow-documentation.mddoc · 2,770 bytesreferences/errors.mddoc · 478 bytesreferences/examples.mddoc · 4,655 bytesreferences/openrouter-integration-security-questionnaire.mddoc · 1,403 bytesreferences/security-assessment.mddoc · 3,052 bytesreferences/vendor-assessment.mddoc · 1,395 bytes
Read excerpt
# OpenRouter Compliance Review
## Overview
OpenRouter is a proxy that routes requests to upstream providers (OpenAI, Anthropic, Google, etc.). Compliance depends on both OpenRouter's data handling and the selected provider's policies. Key considerations: data transit through OpenRouter infrastructure, provider-specific data retention, model selection for regulated data, and audit trail requirements.
## Prerequisites
- An OpenRouter API key (`sk-or-v1-...`) exported as `OPENROUTER_API_KEY` — see the `openrouter-install-auth` skill for setup
- Python 3.8+ with the OpenAI SDK for provider-pinned requests and the automated checker in the references
- `curl` and `jq` to run the Compliance Audit Script
- An existing OpenRouter integration to review — the audit script scans its source tree for hardcoded `sk-or-v1-` keys
- Knowledge of which regimes apply (SOC2, GDPR, HIPAA) and how your data is classified
## Instructions