AB complete-invention-disclosures-rd
Guide inventors and R&D teams through a seven-step English invention-disclosure workflow, organize rough technical notes, identify missing technical support, and generate a structured draft for inventor and qualified patent-professional review. Use when a user has an idea, product note, paper abstract, experiment record, design discussion, or incomplete disclosure that must be made technically complete without drafting claims or providing legal conclusions.
Guide inventors and R&D teams through a seven-step English invention-disclosure workflow, organize rough technical notes, identify missing technical support…
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 69/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 85 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2017 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 461: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 85 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.