Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Fundamental Rights Impact Assessment (FRIA) - EU AI Act Article 27 · lawve-ai | DecimalAI

legalby lawve-ai

Fundamental Rights Impact Assessment (FRIA) - EU AI Act Article 27

lawve-ai/eu-ai-act-fria

Source lawve-ai/awesome-legal-skills ↗License NOASSERTION

Assess whether a Fundamental Rights Impact Assessment (FRIA) is required under Article 27 EU AI Act, and structure or draft that assessment for a specific high-risk AI deployment. Covers deployer scope gating (public bodies and private entities providing public services), affected group mapping, Charter rights analysis, proportionality, safeguards evaluation, residual risk, DPIA/FRIA interaction, notification under Article 27(3), and DACH-specific considerations.

SkillScore82Maintained

Automatic

Legal & Contracts pack

Last verified 8/16/2026

What it changes

Passed 18 of 22 test cases with the skill, and 11 of 22 without it.

Without skill50%

With skill82%

Checks it passed that the model alone missed

Clarifies that high-risk classification is a prerequisite step prior to evaluating Article 27 deployer obligations.
Clarifies that proposed Digital Omnibus postponement dates remain political agreements and are not yet enacted law.
Identifies fundamental rights risks concerning access to essential services and due process in disconnection decisions.

and 4 more in the full report

7 fixed11 passed either way4 still failing0 broke

Pass-rate lift: +32 pp
Tokens: +108%
Agent turns: 0%
Response time: +6%

Model gemini-3.6-flashMeasured 8/16/2026v1 · latest is v218 of 22 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

This benchmark measured an earlier version of the skill.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/lawve-ai-eu-ai-act-fria/SKILL.md https://app.decimal.ai/s/lawve-ai-eu-ai-act-fria/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add lawve-ai-eu-ai-act-fria, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/lawve-ai-eu-ai-act-fria/ and pins it in .decimal/skills.lock

decimalai skills add lawve-ai-eu-ai-act-fria

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/lawve-ai-eu-ai-act-fria/SKILL.md https://app.decimal.ai/s/lawve-ai-eu-ai-act-fria/SKILL.md

Raw file: /s/lawve-ai-eu-ai-act-fria/SKILL.md ↗ · machine-readable summary at /s/lawve-ai-eu-ai-act-fria.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 7

Prompt

Our logistics firm uses a route optimization algorithm for delivery trucks in Spain. We want to know if this algorithm is classified as a high-risk AI system under Annex III of the EU AI Act or if it falls under the narrow exception in Article 6(3).

What was checked, without and with the skill
Checked	Without skill	With skill
Evaluates system classification criteria under Article 6 and Annex III of the EU AI Act.	Passed	Passed
Clarifies that high-risk classification is a prerequisite step prior to evaluating Article 27 deployer obligations.	Missed	Passed

case-05 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md281 lines7 files

Fundamental Rights Impact Assessment (FRIA) - EU AI Act Article 27

Assess whether a deployer must perform a Fundamental Rights Impact Assessment (FRIA) under Article 27 of the EU AI Act, and structure that assessment for a specific high-risk AI use case before the system is put into use.

Important: This skill supports a structured legal-compliance workflow. It does not replace legal judgment. A FRIA is inherently contextual and should never be treated as a box-ticking exercise. Always identify assumptions, open questions, and contested interpretations explicitly.

Before you start: If you have not yet confirmed that the system is a high-risk AI system, use the EU AI Act System Classifier first. Article 27 applies only in the context of high-risk AI systems and only for a subset of deployers.

FRIA Workflow

Follow this sequence in order. Do not skip the scope questions.

Step 1 - Confirm the threshold question: is this a high-risk AI system?

Article 27 only applies where the intended use concerns a high-risk AI system within the meaning of the AI Act.

Check:

Has the system been classified as high-risk under Art. 6(2), that is Annex III? Art. 27 applies only to Art. 6(2) systems. Art. 6(1) product-safety high-risk systems are outside Art. 27 entirely, and Annex III point 2 (critical infrastructure) is expressly excepted.
What is the concrete use case in which the deployer wants to use it?
Is the analysis tied to a specific deployment context, not just the tool in abstract?

If high-risk status is not yet confirmed: stop here and use the EU AI Act System Classifier first.

Step 2 - Scope: is this deployer actually required to perform a FRIA?

This is the most important gating step.

Article 27 does not apply to all deployers of high-risk AI. Art. 27(1) sets two alternative gates:

Gate A, status-based: the deployer is a body governed by public law or a private entity providing public services, deploying any in-scope Annex III system, or
Gate B, system-based: the deployer, public or private, deploys an Annex III point 5(b) system (creditworthiness evaluation or credit scoring) or point 5(c) system (risk assessment and pricing in life and health insurance). A bank scoring credit or an insurer pricing life or health cover owes a FRIA regardless of any public-service character.

In both gates, Annex III point 2 systems are excepted, and the system must be high-risk under Art. 6(2).

Assess carefully:

Is the entity a public authority, municipality, ministry, agency, public university, statutory body, or another body governed by public law?
If private: is it providing a public service in the relevant context, or is it deploying a point 5(b) or 5(c) system, which triggers the duty on its own?
Is the entity acting as deployer (using the system under its authority) rather than as provider/importer/distributor only?
Is the use case the deployer's own operational use, not a hypothetical downstream use by others?

If NO: document that Article 27 FRIA is not mandatory for this deployer, while separate deployer obligations under Article 26 may still apply.

Track record

Benchmark

18 / 22

test cases passed, vs 11 / 22 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan14 of 15 checks clean

0 critical · 0 warning · 1 info — scanner v5 — 9/9/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

No issues (informational notes only).

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

lawve-ai / awesome-legal-skills

skills/fundamental-rights-impact-assessment-eu-ai-act-art-27-werner-plutat/SKILL.md

View on GitHub ↗

License NOASSERTIONImported 9/9/2026Version v2Bundled 6 files

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Fundamental Rights Impact Assessment (FRIA) - EU AI Act Article 27

FRIA Workflow

Step 1 - Confirm the threshold question: is this a high-risk AI system?

Step 2 - Scope: is this deployer actually required to perform a FRIA?

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills