skills.rest
lucadellanna
lucadellannaCOMMUNITY
Explore all skills by this author →
Website𝕏@DellAnnaLucaGitHub

legal-review-checklist

Identify legal and liability risks in open-source software projects.

Updated Feb 9, 2026
Search Tags:#open source#compliance#legal#risk assessment#privacy#liability
One-click install
npx skills add https://github.com/lucadellanna/luca-skills --skill legal-review-checklist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legal-review-checklist
Source: https://github.com/lucadellanna/luca-skills/tree/main/skills/legal-review-checklist
Command: npx skills add https://github.com/lucadellanna/luca-skills --skill legal-review-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify potential legal and liability risks associated with open-source software projects, providing a structured checklist to ensure compliance and mitigate exposure.

Core Features & Use Cases

  • Risk Identification: Walks through common legal categories like warranty, data privacy, and intellectual property.
  • Contextual Analysis: Asks targeted questions about the project to determine which risks are applicable.
  • Mitigation Suggestions: Provides common strategies to address identified risks.
  • Use Case: Before releasing a new open-source tool, use this Skill to systematically review potential legal pitfalls and ensure you've addressed critical areas like licensing and data handling.

Quick Start

Run the legal-review-checklist skill to identify potential legal risks in my project.

Frequently Asked Questions about legal-review-checklist

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

FAQPage Schema
How do I identify legal risks in an open-source software project?▼

Assess data privacy compliance by checking your project against GDPR and CCPA requirements through targeted questions about data handling. This evaluation determines applicable privacy risks and suggests common mitigation strategies.

What is the best way to assess personal liability and warranty disclaimers for open-source tools?▼

The best way to assess personal liability and warranty disclaimers is through a contextual analysis that asks targeted questions about your open-source tool. This structured approach identifies exposure and suggests mitigation strategies for warranty risks.

Do I need a legal compliance review for security vulnerabilities in my open-source project?▼

Yes, a legal compliance review is needed for security vulnerabilities because they create liability exposure. A question-based risk assessment identifies these security gaps and provides common mitigation strategies to reduce legal exposure.

How do I evaluate third-party intellectual property risks before releasing an open-source tool?▼

Evaluate third-party intellectual property risks by applying a comprehensive checklist that examines licensing and trademark concerns within your project. This contextual analysis identifies potential conflicts and suggests mitigation strategies.

Related Skills

Explore More Legal & Compliance Skills→
refactory-langrefactory-lang

speckit-workflows.baseline

Generate baseline-spec.md and current-state.md from codebase and git history.

Official
Advanced
olehsvyrydovolehsvyrydov
13

uk-legal-counsel

Assess UK legal risk and draft compliant business documents.

Community
Advanced
jrhueiuengjrhueiueng

oss-review

Classify dependency licenses and map copyleft obligations to deployment models.

Community
Advanced
rajyeole6rajyeole6

agency-legal-document-review

Score clause-level risk and compare versions in legal documents.

Community
Advanced