AC create-company-patent-profile-ip
Create an evidence-backed executive company patent-strategy report in a continuous-scroll HTML format. Use when a CEO, general manager, board, strategy team, R&D leader, or IP team needs an eight-part profile covering executive findings, company and product context, technical strengths, competitive landscape, market opportunities, core risks, strategic recommendations, and—only when approved current materials are supplied—an aligned PatSnap solution section. Bind every material claim to patent, literature, standard, policy, company, or market evidence and label unsupported claims Unverified.
Create an evidence-backed executive company patent-strategy report in a continuous-scroll HTML format.
As a process C 62/100 · Has gaps — weak spots: failures and branches, 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: 2. 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 62/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 16 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 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 4519 tokens
- 85Steps. 175 steps, 1 vague phrases
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- low 19 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 598: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 175 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.