SKILLEMALL.ai

DC github-bounty-finder-lvjunjie

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: lvjunjie-byte v1.0.2 MIT-0 8 files body ≈ 1 125 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

ProcedureGitHubInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
58/100
safety, quality, tests
Safety 60%
97
Quality 40%
0
Run on models
none yet
Process rating
C
62/100
Has gaps
When it triggers w 12
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

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

✓ No critical or high findings

Medium and low: 3
  • low Risky intent intent-offensive-security README.md:91
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    --query "bug bounty" \
    detector
  • low Exfiltration read-dotenv RELEASE.md:86
    Reads a .env file
    cp .env.example .env
  • low Risky intent intent-offensive-security SKILL.md:60
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    github-bounty-finder scan --query "bug bounty"
    detector

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

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 62/100

  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 39 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1125 tokens
  • low 12 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 0: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 39 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

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

External checks

ClawHub: clean
This skill appears to do the advertised bounty search, but users should protect the GitHub and Algora credentials it requires.
LLM: benign (high) · VirusTotal: · 29 May 2026