seo-audit
Verdict safe, but 1 finding (1 low), mainly policy violation. Most recent scan 2026-01-30.
Second scanner: NVIDIA SkillSpector
SkillSpector found no issues but could not fully inspect the package, usually because SKILL.md refers to a file that is not present, so it fails closed to CAUTION instead of SAFE. Read it as "not fully checked", not as a finding. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
- Package
- 3 files, 24 KB
- SKILL.md
- 1277 words, 12+ sections
- Code
- None. Instructions only.
- Version
- 1.0.0
SKILL.md covers: SEO Audit · Initial Assessment · Audit Framework · Priority Order · Technical SEO Audit · Crawlability · Indexation · Site Speed & Core Web Vitals · Mobile-Friendliness · Security & HTTPS · URL Structure · On-Page SEO Audit
Findings
LOW Skill does not specify a license Policy Violationstatic
Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.
SKILL.md
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 8.7 KB |
references/aeo-geo-patterns.md | doc | 9.2 KB |
references/ai-writing-detection.md | doc | 6.1 KB |
Package contents recorded 2026-10-22 at commit a04cb61a577a. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/coreyhaines31/marketingskills
- Raw scan result: seo-audit-scan.json
- Badge for your README:
- Request a re-scan