eu-ai-act-fria
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. Use when asked about FRIA obligations, Article 27 scope, fundamental rights and AI, or deployer assessment duties.
npx skills add lawve-ai/awesome-legal-skills --skill fundamental-rights-impact-assessment-eu-ai-act-art-27-werner-plutat --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: 1. Has the system already been classified as high-risk under Annex III or as a produ
- 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?
- Step 3 - Timing: when must the FRIA be done?
- Step 4 - Define the use case and operational context precisely
- Step 5 - Map affected persons, groups, and rights at stake
- Step 6 - Assess specific risks of harm
- Step 7 - Evaluate safeguards, human oversight, and data quality measures
- Step 8 - Determine residual risk, proportionality, and go/no-go recommendation
- Step 9 - Notification analysis under Article 27(3)
- Step 10 - Check whether a combined FRIA + DPIA is appropriate
- Step 11 - Add the DACH overlay where relevant
- Quick Question Set
- Reference Files
What does the eu-ai-act-fria skill do?
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. Use when asked about FRIA obligations, Article 27 scope, fundamental rights and AI, or deployer assessment duties.
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill fundamental-rights-impact-assessment-eu-ai-act-art-27-werner-plutat --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.