DB tesy
(no description)
Not recommendedlow grade D
As a process B 68/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
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 · 14
✓ No critical or high findings
Medium and low: 14
-
low Risky intent
intent-offensive-securityIntegration.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Red Team Integration Guide
-
low Risky intent
intent-offensive-securityPhilosophy.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Red Team Philosophy
-
low Risky intent
intent-offensive-securityPhilosophy.md:7Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Military red teaming - dedicated teams that attack plans, strategies, and assumptions to find vulnerabilities before the enemy does.
-
low Risky intent
intent-offensive-securityskill-card.md:39Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [Red Team Philosophy](artifact/Philosophy.md)
-
low Risky intent
intent-offensive-securityskill-card.md:40Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [Red Team Integration Guide](artifact/Integration.md)
-
low Risky intent
intent-offensive-securityskill-card.md:42Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [Red Team Parallel Analysis Workflow](artifact/Workflows/ParallelAnalysis.md)
-
low Risky intent
intent-offensive-securitySKILL.md:5Offensive-security / dual-use content (legitimate for authorised testing; review intended use)description: Adversarial analysis with 32 agents. USE WHEN red team, attack idea, counterarguments, critique, stress test. SkillSearch('redteam') for docs. -
low Risky intent
intent-offensive-securitySKILL.md:51Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Red team analysis (stress-test existing content) | `Workflows/ParallelAnalysis.md` |
-
low Risky intent
intent-offensive-securitySKILL.md:83Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)User: "red team this microservices migration plan"
quoted -
low Risky intent
intent-offensive-securityWorkflows/AdversarialValidation.md:167Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- **32-Agent Protocol:** "Red team this argument/idea" - stress-test existing content
detector -
low Risky intent
intent-offensive-securityWorkflows/ParallelAnalysis.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Red Team Parallel Analysis Workflow
-
low Risky intent
intent-offensive-securityWorkflows/ParallelAnalysis.md:117Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| PT-1 | **The Red Team Lead** - Thinks like an attacker 24/7. | "Here's how I'd exploit this logic." |
-
low Risky intent
intent-offensive-securityWorkflows/ParallelAnalysis.md:322Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# RED TEAM VERDICT
-
low Risky intent
intent-offensive-securityWorkflows/ParallelAnalysis.md:462Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Total: ~10-15 minutes for comprehensive red team
Files scanned: 6. 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 68/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
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 846 tokens
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 9 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
The skill is mostly a red-team analysis workflow, but it loads unreviewed local override files and automatically sends a local HTTP notification when invoked.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026