fluxly Search skills… ⌘K 中文 Publish

patent-assistant

Other Verified v1.1.0
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
92 / 100 · audit passed
Author / version / license
@Demerzels-lab · v1.1.0 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview patent-assistant.preview 
---
name: patent-assistant
description: 帮助研发人员撰写专利技术交底书，并进行专利检索。 将口语化的技术描述转化为结构化的专利技术交底书。 帮我写一份专利交底书：[技术方案描述] 基于技术方案进行专利检索，分析新颖性。 帮我检索相关…
category: other
runtime: Python
---

# patent-assistant output preview

## PART A: Task fit
- Use case: 帮助研发人员撰写专利技术交底书，并进行专利检索。 将口语化的技术描述转化为结构化的专利技术交底书。 帮我写一份专利交底书：[技术方案描述] 基于技术方案进行专利检索，分析新颖性。 帮我检索相关专利：[技术关键词或交底书内容] runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “功能 / 1. 技术交底书生成 / 2. 专利检索” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “帮助研发人员撰写专利技术交底书，并进行专利检索。 将口语化的技术描述转化为结构化的专利技术交底书。 帮我写一份专利交底书：[技术方案描述] 基于技术方案进行专利检索，分析新颖性。 帮我检索相关专利：[技术关键词或交底书内容] runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “功能 / 1. 技术交底书生成 / 2. 专利检索” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 帮助研发人员撰写专利技术交底书，并进行专利检索。 将口语化的技术描述转化为结构化的专利技术交底书。 输出结构： 发明名称 技术领域 背景技术（现有技术及缺陷） 发明内容（技术问题、技术方案、有益效果） 具体实施方式 附图说明建议 基于技术方案进行专利检索…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “功能”, “1. 技术交底书生成”, “2. 专利检索”, “交底书生成流程”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name patent-assistant directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “功能 / 1. 技术交底书生成 / 2. 专利检索” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.