No external URLs in skill definition
Vettd coreOWASP LLM07SKILL.md and references/ files do not reference external URLs
Build a joint customer success plan for a specific account. Use when asked to create a success plan, joint success plan, mutual action plan, or customer onboarding plan. Produces a structured success plan with business goals, milestones, success metrics, ownership, and a 90-180 day roadmap.
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.Skill passed all structure and security checks.
Link points to the repository’s default branch (current HEAD). Certification reflects the state of the repo on Jun 23, 2026. Scanned at c6b34909.
/ coming soon
/ coming soon
/ coming soon
/ coming soon
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
No repository field found in SKILL.md frontmatter. Skills without a verifiable source repository cannot be externally audited.
Scanned all files for credentials, private keys, and code-level risks (eval, shell exec, destructive ops)
SKILL.md — Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.
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
Consider adding numbered steps or a structured procedure for the agent to follow
196 lines (recommended: under 500)
description
Good: description explains when to activate the skill
291/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 "customer-success-plan" follows spec (lowercase, hyphens, ≤64 chars)