agentsclimarketplace
Sign in

Privacy by design

Skill planifest/planifest-framework/planifest-framework/external-skills/privacy-by-design

Privacy-by-design workflow for embedding data minimization, lawful basis, retention, and user-rights readiness into product decisions. Use when a feature touches personal data and privacy controls must be defined before implementation; do not use for narrow infrastructure tuning that does not affect personal-data handling.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill privacy-by-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 361 tokens by cl100k_base, as published. Nobody here has run it

Privacy By Design

Overview

Use this skill to make privacy requirements explicit, enforceable, and testable before implementation.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Lawful basis and minimization rules:
    • references/lawful-basis-and-minimization-rules.md

Templates And Assets

  • Privacy control matrix template:
    • assets/privacy-control-matrix-template.csv
  • Data lifecycle map template:
    • assets/data-lifecycle-map-template.md

Inputs To Gather

  • Feature scope and personal-data touchpoints.
  • Applicable legal/policy obligations for target markets.
  • Data flow boundaries and third-party transfers.
  • Retention and user-rights operational capabilities.

Deliverables

  • Privacy control matrix with ownership.
  • Data lifecycle map from collection to deletion.
  • Consent/notice and user-rights requirements.
  • Residual privacy risk and approval record.

Workflow

  1. Map lifecycle with assets/data-lifecycle-map-template.md.
  2. Define controls in assets/privacy-control-matrix-template.csv.
  3. Validate decisions against references/lawful-basis-and-minimization-rules.md.
  4. Confirm operational feasibility for retention/deletion/rights handling.
  5. Publish controls and unresolved risks.

Quality Standard

  • Every data element has explicit purpose and legal basis/authorization.
  • Data collection is minimized and retention is bounded.
  • User-rights handling is operationally executable.

Failure Conditions

  • Stop when lawful basis or purpose limitation is undefined.
  • Stop when retention/deletion controls cannot be enforced.
  • Escalate when transfer safeguards or approvals are missing.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,506. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.