agentsclimarketplace

Intellectual property ownership technology

Skill scholarly360/contract-intelligence/skills/intellectual-property-ownership-technology

Agent skills for contract clause analysis with industry

Install
npx -y skills add scholarly360/contract-intelligence --skill intellectual-property-ownership-technology

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze, draft, and review Intellectual Property Ownership clauses for Technology contracts. Use when the user mentions IP ownership, intellectual property, work for hire, patent assignment, or asks to review, redline, or generate this clause type. Returns structured risk assessment, plain-language summary, and suggested alternative language.

SKILL.md

2.6 KB, 482 tokens by cl100k_base, as published. Nobody here has run it

Intellectual Property Ownership Clause -- Technology

This skill provides expert-level analysis and drafting assistance for Intellectual Property Ownership clauses in Technology contracts.

When to Activate

Activate this skill when the user:

  • Uploads or pastes a contract containing a Intellectual Property Ownership clause
  • Asks to draft, redline, or improve a Intellectual Property Ownership clause
  • Asks for a risk assessment of an existing Intellectual Property Ownership provision
  • Mentions keywords: IP ownership, intellectual property, work for hire, patent assignment

Workflow

Step 1 -- Intake

Ask the user (if not already provided):

  1. Which party are you representing? (e.g., vendor, client, buyer, seller)
  2. Jurisdiction governing the contract? (e.g., New York, California, England & Wales)
  3. Is this a draft for review or should I generate fresh language?

Step 2 -- Analysis

If reviewing existing language, output the following structure:

## Intellectual Property Ownership Clause Analysis

### Plain-Language Summary
[2-3 sentence plain-English description of what the clause does]

### Key Provisions Identified
- [Provision 1]
- [Provision 2]

### Risk Assessment
| Item | Risk Level | Notes |
|------|-----------|-------|
| [item] | High / Medium / Low | [explanation] |

### Recommended Redlines
[Specific suggested changes with rationale]

### Market Standard Comparison
[How this clause compares to typical Technology market standard]

Step 3 -- Drafting

If generating new language, produce:

  1. Balanced version (neither party-favored)
  2. Favorable to client version
  3. Negotiation notes -- what the other side will likely push back on

Intellectual Property Ownership Playbook -- Technology

See scripts/playbook.md for detailed clause-specific guidance, fallback positions, jurisdiction-specific notes, and precedent language.

Important Notes

  • Always caveat that output is not legal advice and should be reviewed by qualified counsel.
  • Flag any provisions that may be unenforceable or jurisdiction-specific.
  • When jurisdiction is unknown, apply general common-law principles and note assumptions.

What ships with it: 1 file

1.5 KB alongside SKILL.md

scripts/

Gives 0 of the 12 instructions most legal skills give in 482 tokens

Counted across 234 of the 234 authors here whose files we hold, read 2026-08-07

  • Use text operators for text fieldsin 11 of 234, across 6 files
  • Consult qualified counsel before usein 11 of 234, across 3 files
  • Use PatentSearch API for patent searchesin 10 of 234, across 5 files
  • Confirm jurisdiction, employment type, and required clausesin 9 of 234, across 2 files
  • Choose a document template and tailor role-specific termsin 9 of 234, across 2 files
  • Validate compensation, benefits, and compliance requirementsin 9 of 234, across 2 files
  • Add signature, confidentiality, and IP assignment terms as neededin 9 of 234, across 2 files
  • Open the implementation playbook for detailed templatesin 9 of 234, across 2 files
  • Use TSDR for trademark data retrievalin 9 of 234, across 4 files
  • Ask for clarification if required inputs are missingin 8 of 234, across 2 files
  • Set the USPTO_API_KEY environment variablein 8 of 234, across 3 files
  • Use the uspto-opendata-python library for PEDSin 8 of 234, across 3 files

Said here and by no other author read

  • ask for the governing jurisdiction
  • ask if reviewing an existing draft or generating new language
  • identify key provisions within the clause
  • assess risks of identified provisions
  • compare the clause to market standards
  • draft balanced and client-favored clause versions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.