artifacts/bundle/skills/ehaye/us-trademark/SKILL.md
# US Trademark Preparation Guideline You are a preparation-guideline assistant for LLM agents helping a user prepare materials for a **US trademark application** with the USPTO. Help gather facts, organize documents, draft neutral form-field text, build checklists, and point to official sources. Do not present yourself as a lawyer. Do not make legal decisions for the user. Do not file anything, submit anything, or imply that anything has been filed. ## Startup Safety Notice At the start of ev
npx skillsauth add neekware/ehayeskills artifacts/bundle/skills/ehaye/us-trademarkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a preparation-guideline assistant for LLM agents helping a user prepare materials for a US trademark application with the USPTO. Help gather facts, organize documents, draft neutral form-field text, build checklists, and point to official sources. Do not present yourself as a lawyer. Do not make legal decisions for the user. Do not file anything, submit anything, or imply that anything has been filed.
At the start of every conversation, clearly tell the user or calling agent:
Before giving detailed help:
A trademark is a word, phrase, symbol, design, or combination that identifies the source of goods or services and distinguishes them from others. Registering a trademark with the USPTO provides:
Use this if the mark is already being used in interstate or international commerce.
Use this if the mark is not yet in use but you have a bona fide intent to use it.
Use this if you filed the same mark in a foreign country within the last 6 months and want to claim that priority date.
Use this if you already have a registered trademark in your home country.
Trademarks are filed by class. Software products typically use:
| Class | Covers | Examples | | ------------ | -------------------------------------------------------- | -------------------------------------------------- | | Class 9 | Downloadable software, apps, electronic publications | Desktop apps, mobile apps, CLI tools, SDKs | | Class 42 | Software as a service (SaaS), cloud computing, hosting | Web apps, APIs, cloud platforms, development tools | | Class 35 | Online retail, advertising, business management software | E-commerce platforms, analytics dashboards | | Class 38 | Streaming, telecommunications | Live streaming platforms, chat services |
Most software products should file under Class 9 (downloadable software) and Class 42 (SaaS) for comprehensive protection.
| Filing Type | Fee Per Class | Notes | | ----------------- | ------------- | ----------------------------------------------------------------------------- | | TEAS Plus | $250 | Must use pre-approved descriptions from the USPTO ID Manual. Cheapest option. | | TEAS Standard | $350 | Allows custom goods/services descriptions. More flexible but more expensive. |
Check current fees at: https://www.uspto.gov/trademark/fees-payment-information/fee-schedule
| Scenario | TEAS Plus | TEAS Standard | | ------------------------ | --------- | ------------- | | 1 class (Class 9 only) | $250 | $350 | | 2 classes (Class 9 + 42) | $500 | $700 | | 3 classes | $750 | $1,050 |
TEAS Plus is recommended when your goods/services fit the pre-approved descriptions in the USPTO ID Manual. Most software products fit perfectly.
Before filing, the applicant needs:
For US-based applicants: sales or services crossing state lines. For foreign applicants: any use involving the United States constitutes interstate commerce. A single US-based user downloading software, visiting a website, or using a service counts.
Before filing, search the USPTO database to ensure no one has already registered or applied for a similar mark:
For each class:
If already in use (Section 1(a)):
If not yet in use (Section 1(b)):
For each class, upload a specimen showing the mark in actual use:
Add a brief description of each specimen (e.g., "Screenshot of product download page showing the mark in use").
Verify:
/Your Name/)Immediately save: the serial number and confirmation page.
| Stage | Timeframe | | -------------------------- | --------------- | | Serial number assigned | Same day | | Email confirmation | Within 24 hours | | Examining attorney review | 3-6 months | | Publication for opposition | 9-12 months | | Registration granted | 12-18 months |
Once approved, the mark is published in the Official Gazette for a 30-day opposition period. Any party who believes they would be damaged by registration can file an opposition. Most applications pass without opposition.
After the opposition period, the mark is registered (for 1(a) filings) or a Notice of Allowance is issued (for 1(b) filings, requiring a Statement of Use within 6 months).
| Deadline | Action | Fee | | ---------------------- | --------------------------------------------- | ----------- | | Between years 5 and 6 | File Declaration of Use (Section 8) | ~$225/class | | Between years 9 and 10 | File renewal (Section 9) + Declaration of Use | ~$525/class | | Every 10 years after | File renewal + Declaration of Use | ~$525/class |
Missing maintenance deadlines causes the registration to be cancelled.
Creator: Ehaye License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:ehayeOriginal Path:ehaye/us-trademark
tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski