DD opentangl-plugin
(no description)
Not recommendedlow grade D
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
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
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:25High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-1ad+Sc/0sCt…16I+aF+Ywdi…k1d+8oE3C4ZEw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:56High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…3wH+jfWB…yfN+lFri…oov+PzfnxxD5g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:154High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wIN//F77/IADDSs58i+MDaO…jeo+YFg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:538High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…psA+/vCJp…GbA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:662High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…f6T/DOpi…2wA+rbww…Pnw+zSR8yxJ5Q==",
detector
Files scanned: 11. 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 49/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 820 tokens
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
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: clean
This plugin exposes powerful OpenTangl automation, including repository changes and merges, but those capabilities are disclosed, purpose-aligned, and gated as optional tools.
LLM: benign (high) · VirusTotal: · 29 May 2026