legal-expert

Assess licensing, privacy, and regulatory risks in OSS-enabled software.

1|Updated Apr 13, 2026

Search Tags:#audit #compliance #licensing #risk-assessment #privacy #regulations #OSS

Ready to run

npx skills add https://github.com/felixgeelhaar/skills --skill legal-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legal-expert
Source: https://github.com/felixgeelhaar/skills/tree/main/legal-expert
Command: npx skills add https://github.com/felixgeelhaar/skills --skill legal-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Senior tech legal and compliance thinking partner to identify licensing, privacy, and regulatory risks in OSS-enabled software and provide actionable guidance.

Core Features & Use Cases

Licensing risk analysis for OSS dependencies and distribution models
Privacy and data protection mapping (GDPR/CCPA) for product workflows
Regulatory readiness and audit documentation for SaaS, on-prem, and embedded deployments
Use Case: A product team evaluates a new OSS library and vendor contracts to ensure license compatibility and data handling compliance before release
Use Case: An OSS-involved feature is evaluated for GDPR and export control implications during design reviews

Quick Start

Assess the licensing, privacy, and regulatory risks for a given OSS-enabled feature and outline actionable mitigations.

Frequently Asked Questions about legal-expert

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

FAQPage Schema

How do I assess open source software license compliance for SaaS and on-prem deployments?▼

To assess open source software license compliance, identify and evaluate licensing risks for OSS dependencies across SaaS, on-prem, and embedded deployment models. This process maps applicable regulations to technical controls and generates an actionable remediation plan with audit artifacts.

What is the best way to map GDPR and CCPA privacy requirements to technical controls?▼

Mapping GDPR and CCPA privacy requirements involves analyzing product workflows for data protection risks and translating regulatory obligations into specific technical controls. This approach ensures privacy compliance is integrated directly into the software design and generates audit-ready documentation.

Can I use this to evaluate vendor contracts and OSS libraries before a product release?▼

Yes, you can evaluate new OSS libraries and vendor contracts before release. It identifies license compatibility issues and data handling compliance gaps, allowing product, legal, and compliance teams to address regulatory and privacy risks early in the development cycle.

How do I generate audit documentation for regulatory readiness and risk assessment?▼

To generate audit documentation for regulatory readiness, assess licensing, privacy, and regulatory risks across your deployment models. The analysis produces actionable remediation plans and audit artifacts that demonstrate compliance with applicable regulations and internal policies.

When do I need to evaluate export control implications for OSS-involved features?▼

You need to evaluate export control implications for OSS-involved features during design reviews. Assessing regulatory readiness at this stage identifies potential export control restrictions and privacy impacts before the feature is finalized, ensuring compliance across all deployment models.