seo giffy
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only analytics tracking skill, with privacy and provenance details users should review before applying its tracking snippets.
This skill appears safe to use as an analytics implementation guide. Before installing or following its examples, verify the listing identity, review any local marketing context file it may read, and make sure GA4/GTM/Facebook Pixel tracking is configured with consent, PII minimization, and privacy-compliant event parameters.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user may need to verify that this is the analytics tracking skill they intended to install.
The registry-facing name and the skill's internal name/purpose do not match exactly, which may cause user confusion even though the description and content are analytics-focused.
Name: seo giffy ... name: analytics-tracking
Align the public name, slug, and SKILL.md name, or clearly explain the naming difference in the listing.
It is harder to independently verify the publisher or canonical version of the skill.
The listing lacks a source/homepage and the registry version differs from the SKILL.md metadata version shown as 1.1.0; there is no code to install, so this is a provenance note rather than a behavior concern.
Source: unknown; Homepage: none; Version: 1.0.0
Verify the owner/listing before installing, especially if relying on it for production analytics guidance.
Information in the marketing context file may influence the agent's recommendations and could expose project details within the conversation.
The skill directs the agent to use a persistent local context file. This is narrowly scoped and relevant to marketing analytics, but persistent context can contain sensitive or stale information.
If `.agents/product-marketing-context.md` exists ... read it before asking questions. Use that context
Keep the context file accurate, remove sensitive material that is not needed, and do not place instructions there that should override the current user request.
If implemented carelessly, tracking could expose personal or customer data to third-party analytics platforms.
The recommended analytics events may include user, account, purchase, and transaction identifiers that can be sent to analytics or advertising providers.
user_id: "12345" ... account_id: "acct_123" ... purchase_completed | Order placed | transaction_id, value, currency, items[]
Use consent controls, avoid PII, minimize identifiers, and confirm that event parameters comply with privacy laws and provider terms.
Deploying these snippets affects website visitors and may send browsing events to third-party services.
The guide includes user-directed website snippets that load third-party tracking JavaScript through GTM. This is expected for the stated analytics purpose and is not automatically executed by the skill.
Tag Type: Custom HTML ... t.src='https://connect.facebook.net/en_US/fbevents.js'); ... fbq('track', 'PageView');Review and test all GTM/custom HTML tags before publishing, and gate marketing/analytics tags behind appropriate consent settings.