AF analytics-tracking
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," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
As a process F 42/100 · Will not run — References files that are not bundled: ../../tools/REGISTRY.md, ../../tools/integrations/ga4.md, ../../tools/integrations/mixpanel.md
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../tools/REGISTRY.md - warning
missing-refreference to a missing file: ../../tools/integrations/ga4.md - warning
missing-refreference to a missing file: ../../tools/integrations/mixpanel.md - warning
missing-refreference to a missing file: ../../tools/integrations/amplitude.md - warning
missing-refreference to a missing file: ../../tools/integrations/posthog.md - warning
missing-refreference to a missing file: ../../tools/integrations/segment.md
Process rating: all ten parameters 42/100
- 0Tools and files. 6 referenced file(s) missing: ../../tools/REGISTRY.md, ../../tools/integrations/ga4.md, ../../tools/integrations/mixpanel.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (analytics-tracking) differs from the folder (abm-analytics-tracking)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 57 steps
- 100Execution cost. Instruction body is 1922 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
- medium 6 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 15 example trigger phrases
- +3Description length 577: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 57 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.