SKILLEMALL.ai
GitHub ↗ RU Sign in

CC hunt-race-condition

Hunting skill for race condition vulnerabilities.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 5 663 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Hunting skill for race condition vulnerabilities.

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

ProcedureSecuritytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
98
Quality 40%
76
Run on models
none yet
Process rating
C
53/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: hunt-race-condition (sickn33/agentic-awesome-skills)

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:60
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **Privilege escalation** — racing role assignment or permission checks during user creation/upgrade flows
  • low Risky intent intent-offensive-security SKILL.md:282
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    A bug bounty platform's "popular reports" feature allowed upvotes to improve report visibility and researcher reputation scores. By sending ~15 parallel upvote requests for the same report using a sin

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5663 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "license_source"
  • 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 86): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 53/100

  • 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
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 5663 tokens
  • 100Steps. 66 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • low 13 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 49: 120–800 characters recommended
  • +2Single-language instructions
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 66 items
  • +3Output format is stated explicitly
  • +4Has examples (10 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

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