Legal Ip Portfolio Audit Guide

Provides structured checklists and templates to organize IP assets, ownership, registrations, licenses, and enforcement risks for legal portfolio audits.

Security Scan

This is a document-only IP-audit guidance skill whose stated purpose matches its files and runtime instructions; it requests no credentials or installs no code — but because the source is unknown, avoid pasting privileged/confidential client data and verify the publisher before relying on outputs for legal decisions.

Purpose & Capability

The name/description (IP portfolio audit checklists/templates) align with the package contents: SKILL.md, README.md and skill.json provide descriptive guidance. There are no unrelated requirements (no binaries, env vars, or external APIs) that would be incoherent with the stated purpose.

Instruction Scope

SKILL.md stays within descriptive workflow guidance and explicitly disclaims legal advice and automation (no network calls, no filings). It asks the agent to collect facts, documents, dates and other context from the user — appropriate for an audit but creates the real-world risk that users may be prompted to disclose privileged or sensitive client data. The skill itself does not instruct reading system files, accessing hidden endpoints, or transmitting data externally.

Install Mechanism

No install spec and no code files are present (instruction-only). This is the lowest-risk install surface: nothing will be written to disk or executed by the agent as part of the skill.

Credentials

The package requires no environment variables, credentials, or config paths. There are no disproportionate secret or credential requests relative to the described functionality.

Persistence & Privilege

always:false and user-invocable:true (normal defaults). The skill does not request persistent presence, system-wide configuration changes, or access to other skills' credentials.

Assessment

This package is a text-only checklist/template guide and appears consistent with its stated purpose. Before installing or invoking it: (1) do not paste privileged or confidential client information into the skill — its outputs are informational and may be stored or logged by the agent; (2) verify the publisher/source if you need provenance or auditability (the package lists no homepage and the source is 'unknown'); (3) treat outputs as planning aids only and have a qualified attorney verify any legal conclusions, jurisdictional rules, deadlines, or filings; (4) if you require stronger guarantees (e.g., internal retention, non-disclosure, or provenance), prefer guidance from a known/trusted source or from your firm’s internal templates.

Overview

Helps organize intellectual property assets, ownership records, registrations, licenses, enforcement needs, and commercialization risks. This is a descriptive OpenClaw skill for legal-industry workflow support. It provides structured frameworks, checklists, templates, and issue-spotting prompts. It does not execute code, call external APIs, access legal databases, retrieve court records, automate filings, or perform legal services.

When to Use

• Preparing an IP audit
• Reviewing ownership before financing
• Organizing brand/patent/copyright assets

Target Users

• IP lawyers
• Startup counsel
• Product teams
• Technology companies

Inputs to Collect

• Matter or project context, including jurisdiction if known
• Relevant facts, documents, parties, dates, and constraints
• Desired output format, audience, and level of detail
• Known deadlines, risk concerns, or review priorities

Core Modules

1. IP asset inventory — provides structured prompts, checklists, and review fields for this area.
2. Ownership and chain-of-title checklist — provides structured prompts, checklists, and review fields for this area.
3. Registration and renewal tracker — provides structured prompts, checklists, and review fields for this area.
4. License and encumbrance map — provides structured prompts, checklists, and review fields for this area.
5. Enforcement/commercialization issue list — provides structured prompts, checklists, and review fields for this area.

Workflow

1. Confirm the user's legal workflow goal and the relevant practice context.
2. Ask for missing facts, documents, dates, parties, jurisdiction, and audience where needed.
3. Apply the modules below as a structured thinking framework.
4. Produce checklists, templates, matrices, memos, or planning aids tailored to the user's context.
5. Flag uncertainty, verification needs, deadlines, ethics concerns, confidentiality issues, and attorney-review points.

Expected Outputs

• IP inventory table
• Ownership gap list
• Renewal tracker
• License issue map

Example Prompts

• "Create an IP portfolio audit checklist for a software startup."
• "Help organize trademarks, patents, and copyrights before fundraising."

Safety and Legal Limitations

• This skill provides informational workflow support only and is not legal advice.
• It does not create an attorney-client relationship and does not replace review by a qualified attorney.
• Laws, court rules, deadlines, ethics duties, privilege, confidentiality, and professional responsibility rules vary by jurisdiction and matter.
• Users must verify all legal authorities, filing requirements, deadlines, facts, citations, and strategic decisions with qualified counsel.
• The skill must not be used to fabricate evidence, coach false testimony, evade regulation, access data unlawfully, or bypass confidentiality obligations.
• Specific limitation for this skill: Does not file IP rights or determine validity; users must consult qualified IP counsel.

Acceptance Criteria

• Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.
• SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.
• Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.
• Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.
• skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.