agentsclimarketplace
Sign in

Assess privacy security regulatory

Skill alexe-ev/product-plugins/risk-compliance/skills/assess-privacy-security-regulatory

Identify and assess privacy, security, and regulatory risks in product decisions and features. Use this skill when a product decision may have privacy, security, or compliance implications.From its SKILL.md

Install
npx -y skills add alexe-ev/product-plugins --skill assess-privacy-security-regulatory

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.6 KB, 471 tokens by cl100k_base, as published. Nobody here has run it

Assess Privacy, Security & Regulatory Risks

Purpose

Help product teams identify and evaluate privacy, security, and regulatory risks before they become problems.

Skill type

Conceptual skill

Use this skill when

  • A new feature collects, stores, or processes personal data
  • A product decision may have regulatory implications (GDPR, CCPA, HIPAA, etc.)
  • Security risks in a product area need to be assessed
  • A feature involves third-party data sharing or integrations
  • A market expansion brings new regulatory requirements

Do not use this skill when

  • The goal is a full legal or compliance audit (requires legal expertise)
  • The goal is technical security architecture (requires security engineering)

Required inputs

  • Feature or product decision being assessed
  • Data types involved (personal data, financial, health, etc.)
  • Target market/geography

Optional inputs

  • Existing privacy or compliance documentation
  • Known regulatory requirements
  • Third-party integrations involved
  • Data retention and access policies

Upstream context

Works best when:

  • Feature requirements are defined
  • Target market is known

Downstream handoff

Output can feed:

  • plan-risk-mitigation (risks identified here become the input for mitigation planning)
  • write-requirements-prd (privacy/security requirements feed product requirements)

Instructions

  1. Identify all personal, sensitive, or regulated data types involved.
  2. Identify applicable regulations by geography and data type.
  3. Assess privacy risks: data collection, storage, access, sharing, and retention.
  4. Assess security risks: attack surface, data exposure, access controls.
  5. Identify consent, transparency, and user rights requirements.
  6. Flag items that require legal or security engineering review.

Output

Provide:

  • Data types and classification
  • Applicable regulations
  • Privacy risk assessment
  • Security risk assessment
  • Consent and transparency requirements
  • User rights implications (right to access, delete, export)
  • Items requiring legal or security review
  • Recommended mitigations

Risks / caveats

  • This skill does not replace legal or security review — it surfaces risks, not final answers
  • Regulatory requirements vary by jurisdiction — always verify with legal
  • Privacy risks often emerge later in development when they're harder to fix — assess early

What ships with it: 4 files

8.9 KB alongside SKILL.md

examples/

Keep looking

Skills are one crate of 325,949. 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.