AB create-technology-intelligence-briefing-ip
Create an auditable technology-intelligence briefing for named companies and/or a technical topic using patent, scientific-literature, and current-news evidence. Use when the user requests a technology briefing, company technology comparison, patent-and-literature scan, subtechnology map, or evidence-backed technical trend report in HTML.
Create an auditable technology-intelligence briefing for named companies and/or a technical topic using patent, scientific-literature, and current-news…
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
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: 10. 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 65/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
- 30Running it twice. 7 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 171 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3881 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 340: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 171 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.