No external URLs in skill definition
Vettd coreOWASP LLM07SKILL.md and references/ files do not reference external URLs
mohitagw15856
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.
Security Summary
This skill includes a SKILL.md descriptor. No security concerns were identified.
Evidence Index
Category
No external URLs in skill definition
Vettd coreOWASP LLM07SKILL.md and references/ files do not reference external URLs
No prompt injection or jailbreak signals detected
Vettd coreScanned text content for instruction override, jailbreak framing, credential solicitation, and embedded injection markers
No secrets or unsafe code patterns detected
Vettd coreScanned all files for credentials, private keys, and code-level risks (eval, shell exec, destructive ops)
Category
Checklist pattern found
Vettd coreExplicit checklists help agents track progress in multi-step workflows
Examples included
Vettd coreFound code blocks, input/output samples, or an examples section — concrete samples help agents pattern-match effectively
SKILL.md body length is reasonable
Vettd core145 lines (recommended: under 500)
Step-by-step workflow found
Vettd coreStructured procedures improve reliability for complex tasks
Category
Description includes usage context
Vettd coreGood: description explains when to activate the skill
Description within character limit
Vettd core383/1024 characters used
Category
No evaluation test cases
Vettd coreAdd an evals/ directory with test prompts and expected outputs to measure skill quality
Category
No scripts/ directory
Vettd coreConsider bundling reusable scripts for validation and automation
SKILL.md present
Vettd coreRequired skill definition file found
Valid name field
Vettd coreName "technical-spec-template" follows spec (lowercase, hyphens, ≤64 chars)