AF uniprot-database
Access protein metadata, function, taxonomy, and sequences across UniProtKB, UniParc, and UniRef. Use when searching for proteins, mapping identifiers, or retrieving functional annotations and publications. Don't use for sequence alignment, protein folding, or sequence similarity search (use specialized skills for those tasks).
Access protein metadata, function, taxonomy, and sequences across UniProtKB, UniParc, and UniRef.
As a process F 33/100 · No process to follow — References files that are not bundled: references/id_mapping_documentation.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/id_mapping_documentation.md
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: references/id_mapping_documentation.md
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (uniprot-database) differs from the folder (uniprot_database)
- 50When it triggers. No condition that starts the skill
- 60Steps. 49 steps, 4 vague phrases
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Execution cost. Instruction body is 2986 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 329: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (2 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.