SKILLEMALL.ai
GitHub ↗ RU Sign in

CC smoke-test

End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke test deployment", "verify installation", "test service availability", "end-to-end test", or similar.

bytedance/deer-flow Agent Skills author: bytedance MIT 12 files · 7 scripts body ≈ 2 378 tokens Open the sourcegithub.com↗ analyzed 6 d ago

End-to-end smoke test skill for DeerFlow.

As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions

ProcedureDockerInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
87
Quality 40%
84
Run on models
none yet
Process rating
C
64/100
Has gaps
Inputs and preconditions w 11
0
Result and completion w 14
40
Tools and files w 18
60
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

    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 · 5

    ✓ No critical or high findings

    Medium and low: 5
    • medium Dangerous commands cmd-pipe-to-shell-known-host references/troubleshooting.md:77
      Pipe-to-shell installer from a well-known host (still executes remote code)
      curl -fsSL https://get.pnpm.io/install.sh | sh -
    • medium Dangerous commands cmd-pipe-to-shell-known-host references/troubleshooting.md:97
      Pipe-to-shell installer from a well-known host (still executes remote code)
      curl -LsSf https://astral.sh/uv/install.sh | sh
    • low Exfiltration read-dotenv scripts/deploy_docker.sh:26
      Reads a .env file
      cp .env.example .env
    • low Exfiltration read-dotenv scripts/deploy_docker.sh:40
      Reads a .env file
      cp frontend/.env.example frontend/.env
    • low Exfiltration read-dotenv scripts/deploy_local.sh:26
      Reads a .env file
      cp .env.example .env

    Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulli… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value

    Process rating: all ten parameters 64/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 40Result and completion. Does not say what the result is
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 65Failures and branches. 3 branches
    • 70When it triggers. States when to use, but not when not to
    • 85Steps. 91 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2378 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +3Description length 416: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 91 items
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)
    • +3All 7 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.