SKILLEMALL.ai
GitHub ↗ RU Sign in

BD test-red-team

Red-team a running web, React Native, or Capacitor app. Use when "red team this app", "attack my app", "break it", "pentest the app", or "pre-launch hardening". Monkey test → test-exploratory.

kensaurus/skills Agent Skills author: kensaurus MIT 2 files body ≈ 3 826 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Red-team a running web, React Native, or Capacitor app.

As a process D 43/100 · Unfinished process — References files that are not bundled: references/playwright-session-coordination.md

ProcedureSupabasePlaywrightData and analyticsSecuritytype 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
B
91/100
safety, quality, tests
Safety 60%
93
Quality 40%
87
Run on models
none yet
Process rating
D
43/100
Unfinished process
References files that are not bundled: references/playwright-session-coordination.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 7

✓ No critical or high findings

Medium and low: 7
  • low Risky intent intent-offensive-security references/owasp-attack-checklist.md:3
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    Reference for Phase 4 (Security red team) of `test-red-team`. Load this file
  • low Risky intent intent-offensive-security references/owasp-attack-checklist.md:31
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | A01 | Broken Access Control | IDOR, tenant-boundary, privilege escalation, RLS bypass |
  • low Risky intent intent-offensive-security SKILL.md:4
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
    Red-team a running web, React Native, or Capacitor app. Use when "red team
    quoted
  • low Risky intent intent-offensive-security SKILL.md:5
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    this app", "attack my app", "break it", "pentest the app", or "pre-launch
  • low Risky intent intent-offensive-security SKILL.md:187
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ## Phase 2: UI/UX red team (per matrix cell)  [HIGH freedom]
  • low Risky intent intent-offensive-security SKILL.md:208
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ## Phase 3: Data pipeline red team (per matrix cell)  [LOW freedom — 3-layer verify]
  • low Risky intent intent-offensive-security SKILL.md:247
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ## Phase 4: Security red team (per matrix cell, OWASP-mapped)  [HIGH freedom; payloads = LOW]

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/playwright-session-coordination.md
  • note frontmatter-key unknown frontmatter key "effort"

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: references/playwright-session-coordination.md
  • 0Tools and files. 1 referenced file(s) missing: references/playwright-session-coordination.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 11 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 33 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3826 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 15 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +3Description length 192: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 33 items
  • +4Has examples (9 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: 87.