SKILLEMALL.ai

AC eu-ai-act-report-oliver-schmidt-prietz

Generates a formal, structured AI Act compliance assessment report suitable for legal files, audit trails, and regulatory inquiries. This skill should be used when the user asks to "generate an AI Act report", "create a compliance assessment report", "document the AI Act analysis", "create a Prüfbericht", "export as Word document", or wants to consolidate prior AI Act skill outputs into a formal documented assessment.

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 12 files body ≈ 5 015 tokens Open the sourcegithub.com↗ analyzed 63 min ago

Generates a formal, structured AI Act compliance assessment report suitable for legal files, audit trails, and regulatory inquiries.

As a process C 62/100 · Has gaps — weak spots: consistency, running it twice, progress reporting

AnalyzerWordData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
62/100
Has gaps
Progress reporting w 2
0
Running it twice w 4
30
Consistency w 8
40
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5015 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 62/100

  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 6 mutating operations with no state check
  • 40Consistency. Frontmatter name (eu-ai-act-report-oliver-schmidt-prietz) differs from the folder (eu-ai-act-examination-report-generator-oliver-schmidt-prietz)
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5015 tokens
  • 85Steps. 41 steps, 2 vague phrases

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +3Description length 421: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 41 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (8 of 8)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.