client-legal-safety

Evaluate client-facing diagnostics and feature exposure for compliance risks.

58|4|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/po4yka/RIPDPI --skill client-legal-safety
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-legal-safety
Source: https://github.com/po4yka/RIPDPI/tree/main/.github/skills/client-legal-safety
Command: npx skills add https://github.com/po4yka/RIPDPI --skill client-legal-safety

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a conservative client-legal safety review workflow for outcomes exposed to end users by the app, features, or built-in diagnostics, helping ensure compliance and risk-awareness before shipping.

Core Features & Use Cases

  • Review pipelines for domains, diagnostics targets, probes, workflows, and jurisdiction risk.
  • Enumerate touched hosts and data flows to classify risk levels and determine safe product actions.
  • Provide structured risk outputs (host, classification, legal basis, recommended action, sources) to guide product decisions.

Quick Start

Review the app's current diagnostics and feature exposure to identify jurisdictional or compliance risks before rollout.

Frequently Asked Questions about client-legal-safety

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess jurisdiction risk for diagnostics targets before shipping?

Assess jurisdiction risk for diagnostics targets by evaluating feature exposure and probe hosts to classify safety risks. This process identifies touched hosts and data flows, generating a structured risk matrix with legal basis and recommended actions before product rollout.

What is a conservative legal compliance review for service checks?

A conservative legal compliance review for service checks evaluates client-facing diagnostics to ensure risk-awareness. It enforces a strict decision framework that classifies touched hosts and data flows, producing a compact output with risk levels and recommended safe product actions.

Can I use this risk assessment workflow for editing probe hosts across multiple domains?

Yes, you can use this risk assessment workflow for editing probe hosts across multiple domains. It applies to shipping or editing diagnostics targets and service checks, evaluating jurisdiction risk and enumerating data flows to determine safe product actions.

What does the risk matrix output include for compliance diagnostics?

The risk matrix output for compliance diagnostics includes host, classification, legal basis, recommended action, and sources. It provides a compact, structured format to guide product decisions based on evaluated safety and compliance risks.

When do I need a structured risk assessment for client-facing diagnostics?

You need a structured risk assessment for client-facing diagnostics when shipping or editing diagnostics targets, probe hosts, or service checks. It ensures compliance and jurisdictional risk-awareness by enforcing a conservative decision framework before exposing features to end users.

Are there limitations to the conservative decision framework for jurisdiction risk?

The conservative decision framework for jurisdiction risk applies strictly to reviewing diagnostics targets, probe hosts, and service checks. It enforces cautious compliance evaluations, meaning it may recommend safer, more restrictive product actions than less stringent assessment methods.