patent-architect
Patent drafting and prior-art analysis
Turn the user's technical disclosure into a traceable working draft: identify the technical problem, solution elements, effects, variants, assumptions, and open questions; then compare those elements with retrieved sources. This skill supports drafting and research. A patent attorney or the relevant patent office must make legal, filing, novelty, inventive-step, enablement, and claim-scope decisions.
Route and authorization
Preserve the user's jurisdiction, language, output format, title, and requested scope. The bundled template and terminology reference are Chinese-oriented; read them for a Chinese draft and adapt rather than silently applying them to another jurisdiction.
If the user marks the disclosure confidential, says it contains unpublished trade-secret details, or restricts external sharing, use a redacted/local corpus or ask which safe search scope they want. Otherwise follow the user's request for retrieval. Do not expose credentials, private files, or unnecessary invention details in commands, logs, or citations. Do not make a filing, send a cloud document, or contact an attorney without explicit user authorization.
$ARGUMENTS may select:
| Argument | Mode |
|---|---|
--md or no mode |
Save a local Markdown draft when the user requested a file. Prefer an existing docs/ or patents/ directory. |
--lark |
Create or update a Feishu document only when the user requested that destination and the current Lark skill/CLI is available. |
In --lark mode accept at most one of --folder-token, --wiki-node, or --wiki-space, passing the selected token or URL through the current CLI. Verify the changed scope after writing and report the actual URL; never infer success from a command request alone. If a connector or permission is unavailable, provide the local draft or a clear blocked report instead.