BF jz-research-target-software-project
调研指定的某一款开源或商业闭源软件项目。
调研指定的某一款开源或商业闭源软件项目。
As a process F 33/100 · Will not run — References files that are not bundled: 链接,如果为实体书籍则填`
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: 链接,如果为实体书籍则填`
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: 链接,如果为实体书籍则填`
- 0Tools and files. 1 referenced file(s) missing: 链接,如果为实体书籍则填`
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 326 tokens
- 100Running it twice. No mutating operations
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 20: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.
External checks
ClawHub: clean
This is a simple research-report skill that asks the agent to investigate a specified software project and produce a structured Markdown report.
LLM: benign (high) · VirusTotal: · 24 Aug 2026