CtrlK
BlogDocsLog inGet started
Tessl Logo

update-legal-pdfs

Regenerate the downloadable PDF copies of Remotion's Terms, Privacy Policy, DPA Statement, and DPIA Statement after editing their docs pages.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary short-form skill body: a precise executable command with environment guidance, an explicit verification step with a concrete checklist, and lean notes covering genuinely non-obvious generator behaviors. The only minor gap is the absence of an explicit fix-and-regenerate loop after the review step.

DimensionReasoningScore

Conciseness

The 14-line body is lean and every token earns its place: source-of-truth path with a "do not edit the PDFs directly" guard, the exact command, the Python environment note, the commit scope, and two non-obvious generator behaviors. No padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

Fully executable guidance: the exact command "python3 .agents/skills/update-legal-pdfs/scripts/generate.py" run from the repository root, how to obtain a reportlab environment, a concrete per-file review checklist (title, notices, headings, tables, links, contact details), and the redirect mapping file. Nothing is left as vague direction.

5 / 5

Workflow Clarity

A clear three-step sequence (generate, review, commit) with an explicit validation step: "Confirm each PDF retains the source title, notices, headings, tables, links, and final contact details. Render the pages to check wrapping and page breaks." It falls short of 5 only because there is no explicit error-recovery loop saying what to do when the review fails (fix the MDX source and re-run the generator).

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references; the body is well organized as a numbered workflow plus notes, and the one bundle file it relies on (scripts/generate.py) exists and is invoked by an exact path rather than duplicated inline.

5 / 5

Total

19

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-scoped description that names the exact action and all four target documents with an explicit when-condition. The main improvement would be converting the trailing condition into an explicit trigger clause ("Use when...") and broadening natural keyword variants such as "legal documents" or ".pdf".

Suggestions

Add an explicit trigger clause, e.g. "Use when the Terms, Privacy Policy, DPA, or DPIA MDX docs pages in packages/docs/docs are edited and the downloadable legal PDFs need to be refreshed."

Include a few more natural trigger variants users might say, such as "legal PDFs", "legal documents", or the .pdf file extensions (/terms.pdf, /privacy.pdf).

DimensionReasoningScore

Specificity

"Regenerate the downloadable PDF copies of Remotion's Terms, Privacy Policy, DPA Statement, and DPIA Statement" names a concrete action and every target document explicitly. It falls short of 5 because it describes a single regeneration action rather than a comprehensive set of specific actions.

4 / 5

Completeness

Both "what" (regenerate the PDF copies of the four named legal documents) and "when" ("after editing their docs pages") are present. Not 5 because the trigger is stated as a sequencing condition rather than an explicit "Use when..." phrase with concrete trigger wording; not 3 because the when-clause is genuinely explicit.

4 / 5

Trigger Term Quality

Natural terms users would say are present ("PDF", "Terms", "Privacy Policy", "DPA Statement", "DPIA Statement", "docs pages"), giving good keyword coverage. A few natural variants are missing, e.g. "legal documents" or the .pdf file extensions themselves.

4 / 5

Distinctiveness Conflict Risk

"Remotion's Terms, Privacy Policy, DPA Statement, and DPIA Statement" carves out a clear niche with distinct triggers; virtually no other skill would fire on this phrasing.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
remotion-dev/remotion
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.