No external URLs in skill definition
Vettd coreOWASP LLM07SKILL.md and references/ files do not reference external URLs
Create structured technical specification documents that bridge product requirements and engineering implementation. Use when writing a tech spec, engineering spec, system design doc, or API specification. Produces a complete spec with problem statement, proposed solution, data model, API design, alternatives considered, security considerations, testing plan, and rollout strategy.
This skill includes a SKILL.md descriptor. No security concerns were identified.
Vettd Verdict
The overall verdict combines pass, warning, and failure signals across our checks. Click to see how each check is computed.Driven by visible structure and security signals in the submitted skill files.
Link points to the repository’s default branch (current HEAD). Certification reflects the state of the repo on May 5, 2026. Scanned at bd38a364.
security
SKILL.md and references/ files do not reference external URLs
Scanned text content for instruction override, jailbreak framing, credential solicitation, and embedded injection markers
Scanned all files for credentials, private keys, and code-level risks (eval, shell exec, destructive ops)
/ coming soon
/ coming soon
/ coming soon
/ coming soon
best practices
Explicit checklists help agents track progress in multi-step workflows
Found code blocks, input/output samples, or an examples section — concrete samples help agents pattern-match effectively
145 lines (recommended: under 500)
Structured procedures improve reliability for complex tasks
description
Good: description explains when to activate the skill
383/1024 characters used
evals
Add an evals/ directory with test prompts and expected outputs to measure skill quality
structure
Consider bundling reusable scripts for validation and automation
Required skill definition file found
Name "technical-spec-template" follows spec (lowercase, hyphens, ≤64 chars)