Skip to content

ip-legal clearance skill improvements - #31

Open
anseljh wants to merge 7 commits into
anthropics:mainfrom
anseljh:main
Open

ip-legal clearance skill improvements#31
anseljh wants to merge 7 commits into
anthropics:mainfrom
anseljh:main

Conversation

@anseljh

@anseljh anseljh commented May 15, 2026

Copy link
Copy Markdown

This PR makes a few small improvements to the trademark clearance skill. Main changes:

  • Adds context about trademark classes
  • Trademark lingo tweaks (e.g., prefer "register" to "registry")
  • Replace references to USPTO's retired TESS system

More feedback here: https://www.linkedin.com/posts/anseljh_trademark-activity-7460335624298971137-PtvF?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAAFgNwB2iV_vrsS14-GPfSGwog7uqnT0P4

🚀

anseljh added 2 commits May 15, 2026 10:24
- replace TESS references (it's retired)
- prefer "register" to "registry" (more common lingo among trademark professionals)
- cite 9th Cir. model jury instruction on likelihood of confusion
- add short section explaining classes in SKILL.md
- add Nice class headings from WIPO to `references` folder (source url: https://nclpub.wipo.int/enfr/pdf-download.pdf?lang=en&tab=class_headings&dateInForce=20260101)
@github-actions

github-actions Bot commented May 15, 2026

Copy link
Copy Markdown

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@anseljh anseljh mentioned this pull request May 15, 2026
@anseljh

anseljh commented May 16, 2026

Copy link
Copy Markdown
Author

I see there's a new note about no per-skill references directories, so I can move the WIPO class file to conform to that, but please let me know if I misinterpreted that. I will convert it from PDF to Markdown while I'm at it.

4d55f53#diff-6ebdb617a8104a7756d0cf36578ab01103dc9f07e4dc6feb751296b9c402faf7R128-R130

anseljh added 2 commits May 15, 2026 17:13
- Convert WIPO's Nice class headings PDF to Markdown
- move it to the top-level `references` folder of the plugin
@tobinsouth

Copy link
Copy Markdown
Collaborator

Thanks for this — as the report in #29 came from you, this is clearly the right set of corrections, and we'd like to take it (we closed #40 in favour of this PR). Three things to get it over the line:

  1. CLA — apologies, the CLA document link has been broken since launch (Missing CLA.md file #18); the file is being added in Add CLA.md referenced by CONTRIBUTING.md and the CLA Assistant workflow #72. Once that lands, signing is just posting the standard comment the bot asks for.
  2. Nice Classification reference file — could you say a word on the source/licensing of the bundled class-headings list? If it's reproduced from WIPO's published list we likely need an attribution note in the file header; if it's your own summary, say so. Also happy for it to live at ip-legal/skills/clearance/references/ (per-skill references directories are the pattern we've been converging on) rather than the top-level references/.
  3. Version bump — bump ip-legal's plugin.json (1.0.2 → 1.1.0 given the scope of the change).

Happy to handle 2 and 3 ourselves if you'd rather — just say so.

@anseljh

anseljh commented May 30, 2026

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

github-actions Bot added a commit that referenced this pull request May 30, 2026
@anseljh

anseljh commented May 30, 2026

Copy link
Copy Markdown
Author

Thanks, @tobinsouth. All 3 points should be addressed in my new commits.

  1. Nice Classification reference file — could you say a word on the source/licensing of the bundled class-headings list? If it's reproduced from WIPO's published list we likely need an attribution note in the file header; if it's your own summary, say so. Also happy for it to live at ip-legal/skills/clearance/references/ (per-skill references directories are the pattern we've been converging on) rather than the top-level references/.

I sourced this from WIPO. I agree, it looks like an attribution would be necessary per the WIPO general TOU, which sets a default CC BY 4.0 license for what they publish. I added a license field with notes on this, but let me know if you'd like any edits.

Another alternative would be to re-source it from the US Code of Federal Regulations, which is either public domain under the government edicts doctrine or a fair use (see "Court Rules in Favor of Public Access to Information", https://www.arl.org/blog/court-rules-in-favor-of-public-access-to-information/, archived at https://perma.cc/QV9N-4BSN), but the CFR version lacks the explanatory notes, which are quite helpful in practice. My preference as a practitioner would be to include the notes from the WIPO version.

I hear you have some smart in-house counsel, so I'd recommend running this by them before merging, to make sure they're happy with everything. 😄

@anseljh

anseljh commented Jun 24, 2026

Copy link
Copy Markdown
Author

hi @tobinsouth, giving this the gentlest of bumps. I don't think there was anything else needed from me to get this in, right? you'd just need to bump the version again for the next release. let me know if you need anything. thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants