DF bioinfo-engineer-skill
(no description)
Not recommendedlow grade D
将 Agent 塑造为遵循最佳实践的生信分析工程师:环境优先、工具复用、版本控制、文档驱动、密钥隔离、数据版本化、经验沉淀、相对路径规范。 Agent 不是从零开始写算法,而是像资深生信工程师一样:
As a process F 30/100 · Will not run — References files that are not bundled: scripts/run_{task_name}_{YYYYMMDD}.sh, scripts/\
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
read-dotenvSKILL.md:128Reads a .env file (detector / deny-list definition)- Shell: `source .env`
detector -
low Exfiltration
read-dotenvSKILL.md:206Reads a .env filesource .env
-
low Exfiltration
read-dotenvSKILL.md:604Reads a .env filesource .env
-
low Exfiltration
read-dotenvSKILL.md:869Reads a .env filecp .env.template .env
Files scanned: 2. 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 - warning
body-longSKILL.md body ≈ 5133 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/run_{task_name}_{YYYYMMDD}.sh - warning
missing-refreference to a missing file: scripts/\
Process rating: all ten parameters 30/100
Will not run. References files that are not bundled: scripts/run_{task_name}_{YYYYMMDD}.sh, scripts/\
- 0Tools and files. 2 referenced file(s) missing: scripts/run_{task_name}_{YYYYMMDD}.sh, scripts/\
- 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
- 30Running it twice. 12 mutating operations with no state check
- 70Execution cost. Instruction body is 5133 tokens
- 100Steps. 168 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 20 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 82 headings
- +3Step-by-step instructions: 168 items
- +4Has examples (22 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: clean
This skill is a coherent bioinformatics workflow guide, but users should tighten its example secret-handling and logging templates before using them with real credentials.
LLM: benign (high) · VirusTotal: · 20 Jun 2026