analytics-tracking
No security findings. Scanned 1 time, most recently 2026-02-01.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
- Package
- 4 files, 29 KB
- SKILL.md
- 1084 words, 12+ sections
- Code
- None. Instructions only.
- Version
- 1.0.0
SKILL.md covers: Analytics Tracking · Initial Assessment · Core Principles · 1. Track for Decisions, Not Data · 2. Start with the Questions · 3. Name Things Consistently · 4. Maintain Data Quality · Tracking Plan Framework · Structure · Event Types · Event Naming Conventions · Recommended Format: Object-Action
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 7.8 KB |
references/event-library.md | doc | 8.0 KB |
references/ga4-implementation.md | doc | 5.7 KB |
references/gtm-implementation.md | doc | 7.1 KB |
External hosts referenced
connect.facebook.net google.com support.google.com
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
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.
- Llm analyzer. A language model reads the skill and reports intent-level issues the rules cannot express.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
- Meta analyzer. A second model pass that validates, deduplicates and re-scores the other analyzers' findings.
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: analytics-tracking-scan.json
- Badge for your README:
- Request a re-scan