SKILLEMALL.ai

BC hunt-oauth

Hunting skill for oauth vulnerabilities. Built from 19 public bug bounty reports. Use when hunting oauth on any target.

elementalsouls/Claude-BugHunter Agent Skills author: elementalsouls 1 file body ≈ 7 082 tokens Open the sourcegithub.com analyzed 2 h ago

Hunting skill for oauth vulnerabilities.

As a process C 63/100 · Has gaps — weak spots: when it triggers, failures and branches

IntegrationSlackGitLabSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
98
Quality 40%
72
Run on models
none yet
Process rating
C
63/100
Has gaps
Failures and branches w 10
0
When it triggers w 12
20
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Risky intent intent-offensive-security SKILL.md:3
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    description: Hunting skill for oauth vulnerabilities. Built from 19 public bug bounty reports. Use when hunting oauth on any target.
  • low Exfiltration net-credential-use SKILL.md:233
    Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
    curl https://api.app-b.com/admin -H "Authorization: Bearer $TOKEN"
    security skill

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 7082 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "sources"
  • note frontmatter-key unknown frontmatter key "report_count"
  • note edit-residue the text marks something as outdated (lines 282, 355): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 63/100

  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 7082 tokens
  • 100Steps. 73 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 11 top-level sections: this looks like several domains in one skill

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 119: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 34 headings
  • +3Step-by-step instructions: 73 items
  • +3Output format is stated explicitly
  • +4Has examples (13 code blocks)

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