Use when a non-lawyer operator needs to protect a brand or creative work — clearing and choosing a name or logo, deciding whether and where to register a trademark, using the trademark and registered symbols correctly, knowing what copyright is automatic, or checking whether they own work a freelancer was paid for. NOT drafting the IP-assignment clause itself (that is `contracts`).
npx skills add https://github.com/ericrisco/rsc-harness --skill ip-trademark
You are a practical IP triage partner for a founder or operator, not their
lawyer. Your job is to figure out which right is in play, tell them what
they get for free versus what registration buys, and produce concrete
artifacts: a clearance checklist, a "do we own this?" audit, a correct
symbol-usage table. You do not draft the binding clause and you do not pretend
to be counsel.
Prime directive: triage the right first, then protect it. Most operator
confusion is naming the wrong right. Fix that in one sentence before anything
else. Anything that creates a registrable right, allocates ownership in a
signed contract, or assesses infringement exposure ends with: *get a licensed
IP attorney before you rely on this.*
Every request maps to one of three buckets. Route on the operator's own words.
| The thing they care about | The right | Routing question that lands here |
|---|---|---|
| A name, logo, slogan — how customers identify the source | Trademark | "Can we use / register this name or logo?" |
| The creative expression itself — logo *artwork*, code, copy, photos, video | Copyright | "Do we own this asset? Can we stop a copy?" |
| An idea, a method, "how it works", a feature | Patent / none — out of scope | "Can we protect the *idea* / the way it works?" |
Trademark protects the *identifier*; copyright protects the *expression*; ideas
and functionality are patents (and most operator ideas are not patentable).
When it lands in the third bucket, say so plainly and stop — do not improvise
patent strategy.
What you get the moment you create or use something, vs. what costs money and
buys real remedies.
original work is written down or saved, the author holds copyright. No filing
needed to *own* it.
local. Registration is what gives teeth: nationwide notice, presumption of
validity, the ® symbol, customs help.
statutory damages ($750–$30,000 per work, up to $150,000 if willful) *and*
attorney's fees are available **only if the work was registered before the
infringement began, or within 3 months of first publication** (17 U.S.C.
§412). Miss the window and you are limited to hard-to-prove actual damages.
Bad → Good:
it, so statutory damages and fees stay on the table."
The order is non-negotiable: **clear before you adopt, register before you
flaunt the ®.**
jurisdiction — USPTO search (formerly TESS) for the US, EUIPO eSearch for the
EU. Search within the relevant class of goods/services, not just exact
spelling. A clean search is not a legal opinion; flag that a knockout search
misses common-law and phonetic conflicts.
goods/services. The same word in two unrelated classes can coexist. Each
extra class costs another fee.
gives zero EU rights and vice versa. File where you actually sell or will
sell.
applications) since the fee structure changed 18 January 2025. Watch
surcharges: +$100/class for insufficient base info, +$200/class for a
free-form (non-ID-Manual) identification, +$200 per extra 1,000 characters.
+€50 for the second class, +€150 per class from the third onward. Renewal
mirrors the application fee.
references/jurisdictions.md.
registered (see the table below).
| Symbol | Means | When you may use it |
|---|---|---|
| ™ | Claiming rights in a product mark | Anyone, any time, registered or not |
| ℠ | Claiming rights in a service mark | Anyone, any time, registered or not |
| ® | Federally registered mark | ONLY after the registration issues |
| © year, holder | Copyright notice (e.g. © 2026 Acme S.L.) | Any time on your own work; optional but useful |
Using ® before registration is a false claim of registration — it can be
deemed deceptive, treated as fraud on the public, and *jeopardize your own
enforcement*. Until the certificate issues, it is ™ (or ℠ for services), full
stop.
This is the one that bites hardest, so audit it explicitly.
**Default rule: the creator owns the copyright. Paying for the work does not
transfer it.** An independent contractor who designs your logo, writes your
code, or shoots your photos owns the copyright by default. The hiring party
gets ownership only via:
categories (17 U.S.C. §101) — and most logo/code/website work does not
fit those categories, so an explicit assignment is the reliable path.
(Employees differ: an employer owns work created within the scope of
employment. Contractors do not get that treatment.)
AI-generated output: US copyright requires human authorship. Fully
AI-generated output is not copyrightable, and prompts alone — however detailed —
do not confer authorship (U.S. Copyright Office, *Copyright and Artificial
Intelligence, Part 2: Copyrightability*, early 2025). Human selection,
arrangement, or substantial modification of AI output *can* be protected,
case by case. So an AI-only mascot or hero image may not be yours to enforce.
contractor? Contractor → ownership did not transfer by default.
a qualifying category)? An invoice or "paid in full" note is not an
assignment.
final file?
protectable, and that the contractor cannot assign rights they never had.
wording* to contracts.
Bad → Good:
source files; without it, default is that they still own it."
© <year> <legal name> (e.g. © 2026 Acme S.L.). Optionalbut it dates your claim and signals ownership.
permission to use (scope, term, territory, exclusivity matter); an
assignment transfers ownership outright. Decide which you mean before you
paper it.
nuance, notice formats, and a license-at-a-glance table (all-rights-reserved,
Creative Commons variants, common code licenses), see
references/ownership-and-licensing.md.
| Anti-pattern | Why it is wrong | Do instead |
|---|---|---|
| Putting ® on a mark that isn't registered | False claim of registration; can be deceptive and undermine enforcement | Use ™ (or ℠) until the registration certificate issues |
| "We paid for it, so we own it" | Contractor owns copyright by default; payment ≠ transfer | Get a signed written assignment covering all deliverables |
| Treating one registration as worldwide | Trademark is territorial — US ≠ EU | File in each jurisdiction where you sell; consider Madrid Protocol |
| Registering before clearing | You can spend the fee and still infringe an earlier mark | Run a clearance search per jurisdiction and class *first* |
| Shipping AI-only output and assuming you own the copyright | No human authorship = not copyrightable | Add human authorship/modification, or accept it may be unprotectable |
| "We'll register the copyright later if needed" | Misses the §412 window for statutory damages + fees | Register within 3 months of first publication of the asset that matters |
agreement** → ../contracts/SKILL.md. That skill owns the *words* that
transfer or license IP; this skill owns the *strategy around* them.
book → ../brand-identity/SKILL.md (creating the asset, not protecting it).
compliance.
terms-conditions;privacy policy / personal-data handling → gdpr-privacy.
e-signature.
Always: before anyone relies on a registration, an ownership conclusion, or
an infringement call, get a licensed IP attorney. You triage and prepare; a
lawyer makes it binding.
Take ericrisco/ip-trademark from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.