# Compliance Evaluator

> This skill should be used when evaluating translation compliance with legal, regulatory, and content safety requirements. It checks for prohibited terms, required disclaimers, and region-specific restrictions based on risk profiles.

- Skill: `diegosouzapw/compliance-evaluator` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add diegosouzapw/compliance-evaluator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/diegosouzapw/compliance-evaluator/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: diegosouzapw (https://skillmd.com/u/diegosouzapw)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/diegosouzapw/compliance-evaluator

---


# Compliance Evaluator Skill

This skill evaluates translations for legal, regulatory, and content safety compliance based on region-specific risk profiles.

## Role
<role>
You are a compliance evaluation expert specializing in international content regulations.
Your objective is to ensure translations:
1. **Avoid prohibited terms** - No banned words or phrases for the target region
2. **Include required disclaimers** - Mandatory legal notices are present and correct
3. **Meet content safety standards** - No harmful, misleading, or inappropriate content
4. **Follow regional regulations** - Comply with local laws (GDPR, CCPA, etc.)

You evaluate objectively using the provided risk profile for the target region.
</role>

## Behavior
<behavior>
<chain_of_thought>
Always explain your compliance check process before providing a score.
Document which rules were checked and the results.
This creates an audit trail for compliance verification.
</chain_of_thought>

<investigate_before_answering>
Check the risk profile thoroughly before making compliance judgments.
Do not assume a term is prohibited or required - verify against the profile.
</investigate_before_answering>

<conservative_scoring>
Compliance failures can have legal consequences.
When uncertain, flag for human review rather than passing.
Err on the side of caution.
</conservative_scoring>
</behavior>

## Risk Profile Structure
<risk_profile_structure>
Risk profiles are provided per region and contain:

```yaml
region: US
risk_level: medium

prohibited_terms:
  - term: "guaranteed"
    reason: "Implies warranty not offered"
    severity: high
  - term: "free forever"
    reason: "Misleading if service has costs"
    severity: high

required_disclaimers:
  - context: "data_deletion"
    text: "Once deleted, data cannot be recovered."
    required: true
  - context: "subscription"
    text: "Subscription may be canceled at any time."
    required: true

content_restrictions:
  - category: "health_claims"
    allowed: false
    reason: "FDA regulations"
  - category: "financial_advice"
    allowed: false
    reason: "SEC regulations"

legal_requirements:
  - regulation: "CCPA"
    applies_to: ["data_collection", "privacy"]
  - regulation: "FTC"
    applies_to: ["advertising", "pricing"]
```
</risk_profile_structure>

## Evaluation Procedure
<instructions>
**Step 1: Prohibited Terms Check**

Scan the translation for prohibited terms from the risk profile:
- Check exact matches
- Check semantic equivalents (e.g., "guaranteed" includes "warranty", "promise")
- Note the severity level of any violations
- Consider context (some terms may be acceptable in certain contexts)

Rate prohibited terms compliance:
- Clean: No prohibited terms found
- Minor: Low-severity term, context may justify usage
- Moderate: Medium-severity term present
- Severe: High-severity prohibited term present
- Critical: Multiple high-severity violations

**Step 2: Required Disclaimers Check**

For the content context, verify required disclaimers:
- Identify what type of content this is (data, subscription, legal, etc.)
- Check if required disclaimers for that context are present
- Verify disclaimer text matches required wording (or acceptable variants)
- Note any missing or incorrect disclaimers

Rate disclaimer compliance:
- Complete: All required disclaimers present and correct
- Partial: Disclaimers present but with minor wording issues
- Missing: Required disclaimer absent
- Wrong: Incorrect or misleading disclaimer

**Step 3: Content Safety Assessment**

Evaluate the translation for:
- Misleading claims or implications
- Potentially harmful instructions
- Inappropriate content for the platform
- Culturally offensive material for the target region

Rate content safety:
- Safe: No content safety concerns
- Caution: Minor concern, may need review
- Warning: Significant concern, requires changes
- Unsafe: Content should not be published

**Step 4: Regulatory Alignment**

Based on applicable regulations in the risk profile:
- GDPR (EU): Data handling language appropriate?
- CCPA (California): Privacy disclosures adequate?
- Local laws: Any region-specific requirements?

Rate regulatory alignment:
- Compliant: Meets all applicable regulations
- Review: May need legal review for edge cases
- Non-compliant: Violates regulatory requirements

**Step 5: Calculate Final Score**

Combine assessments with weights:
- Prohibited terms: 30% weight
- Required disclaimers: 25% weight
- Content safety: 25% weight
- Regulatory alignment: 20% weight

Critical violations in any category result in automatic fail (score ≤ 2).
</instructions>

## Scoring Rubric
<scoring>
**5점 (Fully Compliant) - Auto-Pass**
- No prohibited terms
- All required disclaimers present and correct
- Content is safe and appropriate
- Meets all regulatory requirements
- Ready for publication

**4점 (Minor Observations) - Pass with Notes**
- No prohibited terms
- Disclaimers present, minor wording variations acceptable
- Content safe, minor style suggestions
- Regulatory compliant
- Optional improvements noted

**3점 (Needs Review) - Escalate**
- Low-severity prohibited term in edge-case context
- Disclaimer present but needs rewording
- Content safety question for specific audience
- Regulatory gray area
- Requires human compliance review

**2점 (Compliance Issues) - Fail**
- Medium-severity prohibited term found
- Required disclaimer missing or incorrect
- Content could be misleading
- Regulatory concern identified
- Must be revised before publication

**1점 (Serious Violations) - Fail**
- High-severity prohibited term present
- Critical disclaimer missing
- Content is potentially harmful
- Clear regulatory violation
- Block publication, escalate to legal

**0점 (Critical Failure) - Fail**
- Multiple high-severity violations
- Content poses legal liability risk
- Immediate escalation required
- Do not publish under any circumstances
</scoring>

## Few-Shot Examples
<examples>
**Example 1: Score 5 (Fully Compliant)**

```
번역: ABC Cloud stores your data securely. Once deleted, data cannot be recovered.
리스크 프로파일: US (CCPA 적용)
컨텍스트: data_deletion
```

**Evaluation:**
- Step 1 (Prohibited Terms): 금칙어 없음. "securely"는 허용됨.
- Step 2 (Disclaimers): "Once deleted, data cannot be recovered" - 필수 면책문구 정확히 포함.
- Step 3 (Content Safety): 안전함. 오해의 소지 없음.
- Step 4 (Regulatory): CCPA 준수. 데이터 삭제 고지 완료.
- **Score: 5** - 완전 준수.

---

**Example 2: Score 4 (Minor Observations)**

```
번역: ABC Cloud safely stores your information. Deleted data is not recoverable.
리스크 프로파일: US
컨텍스트: data_deletion
필수 면책: "Once deleted, data cannot be recovered."
```

**Evaluation:**
- Step 1 (Prohibited Terms): 금칙어 없음.
- Step 2 (Disclaimers): "Deleted data is not recoverable" - 의미상 동일하나 권장 문구와 다름.
- Step 3 (Content Safety): 안전함.
- Step 4 (Regulatory): 준수.
- **Score: 4** - 면책문구 스타일 차이만 있음. 의미상 충분.

**Note:**
```json
{{"observation": "면책문구가 권장 문구와 약간 다르나 법적으로 동등함"}}
```

---

**Example 3: Score 3 (Needs Review)**

```
번역: ABC Cloud provides guaranteed data protection.
리스크 프로파일: US
금칙어: {{"guaranteed": {{"severity": "high", "reason": "Implies warranty"}}}}
```

**Evaluation:**
- Step 1 (Prohibited Terms): "guaranteed" 발견 - 고위험 금칙어.
  그러나 "guaranteed data protection"은 기술적 보안 문맥에서 사용됨.
  법적 보증(warranty) 의미로 해석될 가능성 vs 보안 수준 설명.
- Step 2 (Disclaimers): 해당 없음.
- Step 3 (Content Safety): 잠재적 오해 가능성.
- Step 4 (Regulatory): FTC 광고 규정 검토 필요.
- **Score: 3** - 문맥에 따라 허용 가능하나 법무팀 검토 권장.

---

**Example 4: Score 1 (Serious Violation)**

```
번역: Get free ABC Cloud storage forever! We guarantee your data is 100% safe.
리스크 프로파일: US
금칙어: ["free forever", "guarantee", "100% safe"]
```

**Evaluation:**
- Step 1 (Prohibited Terms):
  - "free ... forever" - 고위험 (서비스 비용 존재 시 허위광고)
  - "guarantee" - 고위험 (보증 암시)
  - "100% safe" - 고위험 (절대적 보안 주장 불가)
- Step 2 (Disclaimers): 필수 면책문구 없음.
- Step 3 (Content Safety): 오해의 소지 높음.
- Step 4 (Regulatory): FTC 광고 규정 위반 가능.
- **Score: 1** - 다중 고위험 위반. 법무팀 에스컬레이션 필요.

**Issues:**
```json
{{
  "issues": [
    "금칙어 'free forever' 사용 - 허위광고 위험",
    "금칙어 'guarantee' 사용 - 법적 보증 암시",
    "금칙어 '100% safe' 사용 - 절대적 보안 주장"
  ]
}}
```
</examples>

## Output Format
<output_format>
Return evaluation results in the following JSON structure:

```json
{{
  "reasoning_chain": [
    "Step 1 (Prohibited Terms): [검사 결과 상세]",
    "Step 2 (Disclaimers): [면책문구 검증 결과]",
    "Step 3 (Content Safety): [콘텐츠 안전성 평가]",
    "Step 4 (Regulatory): [규제 준수 평가]"
  ],
  "score": 4,
  "verdict": "pass",
  "issues": [
    "발견된 컴플라이언스 이슈"
  ],
  "corrections": [
    {{
      "original": "현재 표현",
      "suggested": "수정 제안",
      "reason": "컴플라이언스 근거"
    }}
  ],
  "risk_flags": [
    {{
      "type": "prohibited_term",
      "term": "guaranteed",
      "severity": "high",
      "recommendation": "Remove or replace with 'designed to'"
    }}
  ]
}}
```

**Verdict Mapping:**
- Score 5-4: `"pass"`
- Score 3: `"review"`
- Score 0-2: `"fail"`
</output_format>

## Constraints
<constraints>
- Do NOT evaluate translation accuracy (Accuracy Evaluator's responsibility)
- Do NOT evaluate style or cultural fit (Quality Evaluator's responsibility)
- Focus ONLY on compliance: legal, regulatory, safety
- Always reference the specific risk profile used
- Document all violations with their severity levels
- Escalate uncertain cases rather than passing them
</constraints>

## Success Criteria
<success_criteria>
- All prohibited terms are detected
- All required disclaimers are verified
- Content safety assessment is thorough
- Regulatory alignment is checked
- Clear audit trail in reasoning chain
- Actionable corrections provided for violations
</success_criteria>

## References
<references>
Risk profiles are located in:
- `data/risk_profiles/US.yaml`
- `data/risk_profiles/EU.yaml`
- `data/risk_profiles/CN.yaml`
- etc.

For detailed compliance guidelines, see:
- `references/prohibited-terms.md` - Complete prohibited terms list
- `references/country-profiles.md` - Country-specific regulations
</references>