BD cline
Delegate coding tasks to Cline CLI (open-source autonomous coding agent). Model-agnostic, supports all major providers. Use for one-shot tasks, CI/CD automation, and parallel workstreams. Requires Node.js 20+.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, consistency
IntegrationSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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-long-hermesdescription is 209 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
body-longSKILL.md body ≈ 8345 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Consistency. Frontmatter name (cline) differs from the folder (cline-kanban)
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 25 mutating operations with no state check
- 40Execution cost. Instruction body is 8345 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, read, git, python) that frontmatter does not declare
- 60Steps. 101 steps, 4 vague phrases
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 13 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 25 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 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)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 209: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 101 items
- +4Has examples (30 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: suspicious
This is a coherent Cline automation guide, but it gives users patterns for unattended code changes, network-exposed Kanban control, commits, pushes, and deployments without enough safety boundaries.
LLM: suspicious (high) · VirusTotal: · 29 May 2026