clean-room-risk-screen

Screen business ideas for IP, regulatory, data, and claim risks and propose safer alternatives.

4|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/accolver/skill-maker --skill clean-room-risk-screen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-room-risk-screen
Source: https://github.com/accolver/skill-maker/tree/main/clean-room-risk-screen
Command: npx skills add https://github.com/accolver/skill-maker --skill clean-room-risk-screen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill checks for risks in business ideas, offers, and product plans by identifying employer IP/confidentiality concerns, regulatory overreach, sensitive-data misuse, and unsafe claims, then proposes safer clean-room alternatives. Use when a user's edge may depend on employer information, regulated workflows, customer data, or legally sensitive positioning.

Core Features & Use Cases

  • Risk classification across employer IP/confidentiality, customer data access, PHI or regulated data, and licensed authorities.
  • Produce concrete risk memo and a JSON risk screen using assets/risk-screen-template.json with sections Risk Summary, Allowed, Conditional, Blocked, Safer Path.
  • Provide safer adjacent paths based on public data, original assets, generalized workflows, and human-in-the-loop support.
  • Use with references/risk-categories.md and references/safer-alternatives.md for guidance.

Quick Start

Load the risk-screen template and risk categories from references and start with a memo describing risk and safer path.

Frequently Asked Questions about clean-room-risk-screen

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

FAQPage Schema
How do I screen a business idea for employer IP and confidentiality risks?

Idea risk screening evaluates business plans for employer IP, regulatory overreach, sensitive-data misuse, and unsafe claims. It generates a structured JSON risk memo classifying elements into Allowed, Conditional, Blocked, and Safer Path categories.

What is a clean-room alternative for a product plan using customer data?

A clean-room alternative for customer data usage is a safer path built on public data, original assets, generalized workflows, and human-in-the-loop support. It allows you to proceed without misusing sensitive employer or customer information.

When do I need a risk memo for my product plan?

You need a risk memo when an edge depends on employer information, regulated workflows, customer data, or legally sensitive positioning. It screens for IP ownership constraints and regulatory overreach before development.

How do I generate a structured risk screen in JSON for legal compliance?

Load the risk-screen template JSON and risk-categories reference, then classify your business idea against employer IP and regulatory risks. The output is a structured JSON risk memo with Risk Summary, Allowed, Conditional, Blocked, and Safer Path sections.

Can I use this risk screening approach for plans involving regulated workflows?

Yes, this approach specifically screens plans involving regulated workflows, PHI, and licensed authorities. It identifies regulatory overreach and sensitive-data misuse, proposing safer adjacent paths based on generalized workflows.

What are the limitations of using clean-room alternatives for sensitive-data misuse?

Clean-room alternatives require restructuring plans around public data and original assets, limiting competitive edge if strategy depends on employer data. They cannot validate unsafe claims or bypass licensed authorities.