Skip to content
Skills Library
Data & analytics · Planning

tracking-schema

/tracking-schema

Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

Licence
Apache-2.0
Last repository change
29.04.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.04.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

Original author description

Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

How it works

  1. Inputs
  2. Workflow
  3. Role And Quality Bar
  4. Required Output
  5. Closeout Style
  6. Stop Boundary
  7. References
Original SKILL.md headings · 96 lines, 493 words
SKILL.md preview
---
name: tracking-schema
description: Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
---

# Tracking Schema

Use this skill for Step 3 work only.

## Inputs

One of:

- confirmed `<artifact-dir>/site-analysis.json`
- existing `<artifact-dir>/event-schema.json`

## Workflow

## Role And Quality Bar

During schema work, act as an expert in event tracking design.

Your job is not to list generic events. Your job is to produce a tracking plan that is:

- aligned with common GA4 / GTM industry standards
- comprehensive enough to cover the site's meaningful business journeys
- accurate enough to be implemented and verified without guesswork
- disciplined enough to avoid noisy, redundant, or low-signal events
- easy for the user to review, approve, QA, and maintain

Favor event definitions that are business-meaningful, implementation-ready, and analytically useful.
Do not preserve weak legacy patterns just for continuity.
Do not inflate the schema with events that add little reporting or decision value.

If the telemetry consent prompt appears and no prior choice is recorded, stop and follow [../../references/telemetry-consent.md](../../references/telemetry-consent.md) before continuing.

If schema context is not prepared yet:

```bash
./event-tracking prepare-schema <artifact-dir>/site-analysis.json
```

If the site has a live GTM container installed, make sure `tracking-live-gtm` has already produced `<artifact-dir>/live-gtm-analysis.json` before running `prepare-schema`.

Then:

`validate-schema --check-selectors` launches a real Chromium via Playwright to test each schema selector against the live site. Run it in an environment that permits outbound network and local browser execution; environments that restrict either tend to cause Playwright to hang or fail silently rather than return a clean error.

```bash
./event-tracking validate-schema <artifact-dir>/event-schema.json --check-selectors
./event-tracking generate-spec <artifact-dir>/event-schema.json
./event-tracking confirm-schema <artifact-dir>/event-schema.json
```

During review:

- explain what live tracking problems the schema fixes when `live-gtm-analysis.json` is present
- explain what benefits the new schema brings compared with the current live baseline
- default to a compact tracking-plan summary in this order: `Event Table`, `Common Properties`, `Event-specific Properties`
- keep long parameter inventories out of the main event table
- stop for user approval before GTM generation
- a broad request such as "full workflow" or "全流程" does not count as schema approval
- do not run `./event-tracking confirm-schema <artifact-dir>/event-schema.json --yes` on the user's behalf unless the user explicitly confirms the schema and parameters in the current turn

## Required Output

Produce and share:

- `<artifact-dir>/event-schema.json`
- optional `<artifact-dir>/event-spec.md`
- optional `<artifact-dir>/tracking-plan-comparison.md` when `live-gtm-analysis.json` is present
- `<artifact-dir>/schema-decisions.jsonl` after schema confirmation
- `<artifact-dir>/schema-restore/` restore snapshots after schema confirmation
- updated `<artifact-dir>/workflow-state.json`

## Closeout Style

- default to a decision-ready tracking-plan summary before listing files
- keep the chat structure in this order: `Event Table`, `Common Properties`, `Event-specific Properties`
- if a live baseline comparison exists, keep it as a compact appendix rather than replacing the tracking-plan structure
- list files and next steps only after the summary

## Stop Boundary

Stop after schema approval.

Do not continue into `generate-gtm` from a broad workflow request alone. The user must explicitly approve the current `event-schema.json` and its parameters first.

Default next phase:

```bash
./event-tracking generate-gtm <artifact-dir>/event-schema.json --measurement-id <G-XXXXXXXXXX>
```

## References

- [../../references/event-schema-guide.md](../../references/event-schema-guide.md)
- [../../references/ga4-event-guidelines.md](../../references/ga4-event-guidelines.md)
- [../../references/output-contract.md](../../references/output-contract.md)
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named tracking-schema.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version a64754750ea3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100tracking-design
    Design event tracking schemas, entities, and event specifications following Snowplow conventions. Use when the user wants to track new events, create schemas, or design their tracking plan. Use this skill whenever a user mentions schemas, event design, or instrumentation…
  • 100schema-spec
    Write a data schema specification document. Use when the user says "schema spec", "document this schema", "schema design doc", "data model spec", "table spec", "field definitions", "schema contract", "data dictionary", "define these fields", or needs to formally document a…
  • 95register-event-schema
    Register a JSON Schema for an event type on an EventSourcingDB instance. Use when the user wants to add validation, define a schema, or enforce structure for an event type.
  • 100event-tracking-plan
    Design an analytics instrumentation plan — define key events, properties, naming conventions, and produce a tracking spec document that engineers can implement. Use when setting up analytics for a new product, redesigning a tracking schema, or onboarding engineers to instrumentation work.
  • 100lumen-instrument
    Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Use when asked to "what should we track", "instrumentation plan", "set up analytics events", "analytics event schema", "tracking plan", or "instrument this feature".
  • 100schema-design
    Design an API schema — OpenAPI spec, GraphQL schema, or gRPC proto for a feature. Use when asked to "design an OpenAPI spec", "write a GraphQL schema", or "define the proto for this".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.