AC review-us-patent-claims-ip
Review supplied US patent application claims and relevant specification, drawings, Office-action, and prosecution context for claim quality, prosecution readiness, 35 U.S.C. 101/102/103/112 risk, BRI, 112(f), dependency/form, restriction/election, continuation/divisional strategy, infringement observability, and amendment options. Use for US claim review, drafting quality control, amendment strategy, or a structured claim issue list.
Review supplied US patent application claims and relevant specification, drawings, Office-action, and prosecution context for claim quality, prosecution…
As a process C 56/100 · Has gaps — weak spots: inputs and preconditions, running it twice, 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 56/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4290 tokens
- 85Steps. 190 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
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)
- +1No license
- +2Single-language instructions
- +3Description length 437: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 190 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.