metrics-tagging

Solid

Analyze UI mockups, screenshots, or prototype frames to identify all trackable interactions and generate a complete analytics event taxonomy table, including multi-step task/flow completion events. Use this skill whenever a designer uploads a screen, mockup, prototype screenshot, or UI frame and wants to know what should be tagged, what events to fire, or how to document analytics for handoff. Also trigger when someone asks to "tag this screen," "identify events," "create a tagging spec," "what should we track," "build an event table," or "tag this flow/task" for any UI. If a designer shares any visual of a UI and mentions analytics, tracking, tagging, GTM, events, funnels, or metrics — use this skill.

Web & Frontend 20 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
44
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Metrics Tagging Skill Analyze a UI mockup or screenshot and produce a complete analytics event taxonomy, ready for handoff to a tag implementation team. ## Mental Model: Three Levels of Tagging Before generating the table, always frame the output across three levels. This helps designers understand *why* each tag matters — not just *what* it is. | Level | What it answers | Example | |-------|----------------|---------| | **Page** | What happened on screen | User clicked "Save" button | | **App** | What workflow is this part of | Account setup flow completion | | **Business** | Which KPI does this feed | Task completion rate, time-on-task, abandonment rate | ## Input Accept any of: - Screenshot or photo of a UI mockup - Prototype frame image - Annotated design screenshot - Description of a screen with listed components The designer may also provide: - The flow name (e.g. "Onboarding", "Checkout", "Settings", "Profile Edit") - The product type (e.g. SaaS, e-commerce, internal tool, consumer app) - Existing event naming conventions already in use - Business KPIs this flow relates to If the designer does not provide product or flow context, ask for it before generating the table. The "Purpose" column cannot be filled accurately without knowing what the flow is trying to accomplish. ## Naming Convention Use camelCase. Follow this pattern: `noun + Verb` **Format:** `[object/screen][Action]` **General examples:** - `checkoutViewed` — page load on checkout screen - `car...

Details

Author
ommakes
Repository
ommakes/Skills
Created
6 months ago
Last Updated
today
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

gtm-tag-audit

Audits tag management containers (Google Tag Manager, Matomo Tag Manager, Tag Commander/Commanders Act) into a structured Excel workbook, from client-side code found on a site (gtm.js, container_XXX.js, tc_*.js, i.e. pre-audit without container access) or from an interface/API export (full audit). Lists each tag with vendor, exact event and data sent, trigger, blocker, Tag Commander scope (périmètre), status and consent mechanism; several tools on one site go in one workbook. Use whenever the user shares or mentions a tag manager container, export or container code (`var data = {"resource"`, `MatomoTagManager.addContainer`, `tagContainer Generator`, `tC.launchTag`, a GTM-XXXXXXX ID), or asks for a tracking audit, pre-audit, full audit, "what does this site send to Meta/GA", "list the tags with their triggers", or in French "audit de tracking", "pré-audit", "audit complet", "liste-moi les tags avec leurs déclencheurs", even without naming the tool.

0 Updated yesterday
SW-Vincent
AI & Automation Listed

analytics-instrumentation

Use to make a product MEASURABLE — define the tracking plan / event taxonomy, instrument events (client + server), and tie dashboards to the PRD success metrics (North Star + inputs). Trigger on "how do we measure this", "add analytics/tracking", "instrument the funnel", "set up events/metrics/dashboards", "North Star", "A/B test measurement", or before any GA so the launch can be measured.

1 Updated 1 months ago
StielChancellor
AI & Automation Featured

analytics-strategy

Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.

906 Updated 1 weeks ago
rampstackco