BB jiang-irac-opposition
商标异议·无效申请推理引擎(SJ-IRAC):基于法条要件、证据链与风险分级的专业级审查与攻防系统。
商标异议·无效申请推理引擎(SJ-IRAC):基于法条要件、证据链与风险分级的专业级审查与攻防系统。
As a process B 65/100 · Nearly there — weak spots: when it triggers, failures and branches, consistency
ProcedureSecurityWriting and documentsMarketingtype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 65/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (jiang-irac-opposition) differs from the folder (jiang-irac-opposition-invalidation)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 94 steps
- 100Execution cost. Instruction body is 1677 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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)
- +3Description length 50: 120–800 characters recommended
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 23 headings
- +3Step-by-step instructions: 94 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.