DD twenty-oauth-mastery
(no description)
Not recommendedlow grade D
As a process D 37/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenREADME.md:133High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `ses_…is4` | Frontend token fix | Backend source not compiled, cookie attributes |
table -
low Secrets in code
secret-high-entropy-tokenREADME.md:134High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; documentation table row)| `ses_…ywW` | Enrichment testing | Container networking, environment variables |
detectortable -
low Secrets in code
secret-high-entropy-tokenREADME.md:135High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `ses_…gfY` | OAuth 500 error RCA | Endpoint validation, error handling |
table -
low Secrets in code
secret-high-entropy-tokenREADME.md:136High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `ses_…6tn` | OAuth codebase exploration | Comprehensive file analysis |
table
Files scanned: 3. 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 37/100
- 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
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 4140 tokens
- 85Steps. 77 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
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: 29 headings
- +3Step-by-step instructions: 77 items
- +4Has examples (24 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This OAuth troubleshooting skill is coherent, but it gives unsafe token-handling guidance that could expose user sessions and OAuth credentials.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026