CtrlK
BlogDocsLog inGet started
Tessl Logo

invention-structuring

Structure a raw invention idea into a formal invention disclosure. Use when user says "构建发明", "structure invention", "发明构建", "invention disclosure", or wants to formalize a rough idea into a patent-ready structure.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and highly actionable with concrete patent-specific templates and a reviewer prompt, but the workflow's refinement loop is declared as a constant yet never operationalized as an explicit validate-revise-retry cycle, and its one external reference points to a file that does not exist.

Suggestions

Make the refinement loop explicit in the workflow: after Step 6, add 'If the reviewer identifies issues, revise the flagged layer (Step 1/2/4) and re-run validation, up to MAX_REFINEMENT_ROUNDS; only proceed to Step 7 when no major issues remain.'

Either create ../shared-references/patent-writing-principles.md with the referenced Problem-Solution-Advantage framework, or inline the essential parts and drop the dangling reference so the body is self-contained.

Move the claimable-subject-matter and drawing-plan tables into a references/ file if they grow, keeping SKILL.md an overview that links one level deep — this would lift progressive_disclosure toward the score-3 anchor.

DimensionReasoningScore

Conciseness

The body gives domain-specific patent guidance (Problem-Solution-Advantage framing, claim-category and drawing-plan tables, a concrete reviewer prompt and output template) without explaining concepts Claude already knows, and is structured rather than padded — matching the lean, score-3 anchor; only minor redundancy between Step 1 and Key Rules keeps it from being flawless.

3 / 3

Actionability

Provides concrete executable guidance: a fixed problem-statement format, claimable-subject-matter and drawing-plan tables, a copy-paste mcp__codex__codex prompt with explicit config, and a complete output template — fully actionable for an instruction-only skill, matching the score-3 anchor.

3 / 3

Workflow Clarity

The 7 steps are clearly sequenced and Step 6 is a validation checkpoint, but the feedback loop is only implicit: MAX_REFINEMENT_ROUNDS=3 is declared yet the workflow never states what to do with reviewer findings (revise which step, re-run, stop) — matching the score-2 anchor of steps present with checkpoints missing or implicit.

2 / 3

Progressive Disclosure

Sections are well-organized, but all content is inline (~180 lines) and the single external reference '../shared-references/patent-writing-principles.md' does not exist on disk (no bundle files present; /research-refine also missing), so the reference is not a real navigable path — matching the score-2 anchor of structure present but references not clearly signaled / content that could be separate is inline.

2 / 3

Total

10

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it clearly states a niche purpose and provides explicit, natural bilingual trigger terms covering both what and when. Its only weakness is that the action framing is a single operation restated rather than a list of distinct concrete capabilities.

Suggestions

Enumerate the distinct concrete actions the skill performs (e.g., 'derive the technical problem, decompose features into core/supporting/optional, and plan claim categories') to lift specificity from a single restated action to multiple concrete actions.

DimensionReasoningScore

Specificity

Quotes 'Structure a raw invention idea into a formal invention disclosure' and 'formalize a rough idea into a patent-ready structure' — these name the domain and an action, but are two framings of a single structuring action rather than multiple distinct concrete actions as in the score-3 anchor (extract, fill, merge).

2 / 3

Completeness

Explicitly answers what ('Structure a raw invention idea into a formal invention disclosure') and when (an explicit 'Use when...' clause with concrete triggers), matching the score-3 anchor for both what AND when.

3 / 3

Trigger Term Quality

Quotes natural bilingual triggers '构建发明', 'structure invention', '发明构建', and 'invention disclosure' — good coverage of terms a user would actually say, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The patent/invention-disclosure niche is distinct and the triggers are specific to invention structuring, making conflict with other skills unlikely — matches the score-3 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.