DD paper-recommendation
(no description)
A Clawdbot skill for AI research paper discovery, review, and recommendation.
As a process D 47/100 · Unfinished process — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 47/100
- 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
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 42 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2544 tokens
- low 10 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 0: 120–800 characters recommended
- -4Absolute local paths (C:\Users, /home/…): not portable
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 32 headings
- +3Step-by-step instructions: 42 items
- +3Output format is stated explicitly
- +4Has examples (19 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
In the sandbox The scripts try to reach the network
The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.
Grade capped: no higher than C. A skill whose scripts reach outside or for secrets cannot wear an A or a B, however well the text is written.
Запущено 4 скрипта; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
Из них 3 не дошли до работы, и об их поведении мы ничего не узнали.
scripts/daily_workflow.py | не запустился: FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/skills/paper-recommendation' |
scripts/fetch_papers.py | запускает curl |
scripts/read_pdf.py | не запустился: read_pdf.py: error: the following arguments are required: pdf_path |
scripts/review_papers.py | не запустился: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) |
31 Oct 2026