SKILLEMALL.ai
GitHub ↗ RU Sign in

BF privacy-engineering

Translate privacy principles and legal requirements into data-flow, lifecycle, acceptance, and verification artifacts. Map data classification, purpose, processing, access, retention, deletion, residency, and consent; define verifiable privacy acceptance criteria; and produce data-lifecycle records, retention/deletion verification plans, and privacy change reviews. Use when engineering privacy into a system, feature, or data flow — not for legal advice, jurisdiction-specific regulatory interpretation, or replacing security engineering or incident response.

magnus919/agent-skills Agent Skills author: magnus919 MIT 9 files body ≈ 3 860 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Translate privacy principles and legal requirements into data-flow, lifecycle, acceptance, and verification artifacts.

As a process F 42/100 · Will not run — References files that are not bundled: ../legal-strategy/SKILL.md, ../secure-software-engineering/SKILL.md, ../security-audit-methodology/SKILL.md

ProcedureAI and agentsData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
F
42/100
Will not run
References files that are not bundled: ../legal-strategy/SKILL.md, ../secure-software-engineering/SKILL.md, ../security-audit-methodology/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 8. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../legal-strategy/SKILL.md
  • warning missing-ref reference to a missing file: ../secure-software-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../security-audit-methodology/SKILL.md
  • warning missing-ref reference to a missing file: ../data-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../site-reliability-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../production-readiness/SKILL.md
  • warning missing-ref reference to a missing file: ../product-analytics-and-measurement/SKILL.md
  • warning missing-ref reference to a missing file: ../agent-evals-and-observability/SKILL.md

Process rating: all ten parameters 42/100

Will not run. References files that are not bundled: ../legal-strategy/SKILL.md, ../secure-software-engineering/SKILL.md, ../security-audit-methodology/SKILL.md
  • 0Tools and files. 8 referenced file(s) missing: ../legal-strategy/SKILL.md, ../secure-software-engineering/SKILL.md, ../security-audit-methodology/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 4 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 100Steps. 61 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3860 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 562: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 61 items
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

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