# Let your coding agent complete the tracking story

Audit and improve tracking in a new game or one you have already shipped. The Ravensight Instrumentation Skill guides your agent through existing events, missing player journeys, failures, retries, choices and exits.

Choose audit-only for recommendations, expand for code changes to an existing integration, or initialize for a new one. Your agent preserves useful events, checks for duplicate or misleading tracking, and produces an event catalog and coverage report with verification evidence.

## 1. Choose your agent

The public [Ravensight Skills repository](https://github.com/Reality-Software-Entertainment/ravensight-skills) contains the skill and its references. Choose the installer flag for the agent you use in your game repository.

| Agent | Installer flag | How to start |
| --- | --- | --- |
| Codex | `--agent codex` | `$ravensight-instrumentation` |
| Claude Code | `--agent claude` | `/ravensight-instrumentation` |
| GitHub Copilot | `--agent copilot` | Ask it to use ravensight-instrumentation. |
| Other agents | `--agent generic` | Ask the agent to read the installed SKILL.md and its references. |

## 2. Install in your game repository

With Node 20 or later, open a terminal in your game directory and run the command below. Replace `codex` with your agent's flag value from the table.

```
npx ravensight-skills --agent codex --project .
```

This downloads and runs the public installer. It adds skill files, preserves existing content, and leaves game code alone. Add `--dry-run` to preview the destination. Reload your agent's skills or restart its session if it does not discover the new skill.

Without Node, copy the complete `skills/ravensight-instrumentation` folder from the repository into your agent's skill directory. Keep `references/` and `agents/` with `SKILL.md`. The [setup guide](https://github.com/Reality-Software-Entertainment/ravensight-skills#install) lists the exact directories, update and uninstall steps. To pin an installation to a published version, replace `` in `npx ravensight-skills@ --agent codex --project.`. The current skills package is `0.2.2`. Installing from Git or npm does not require marketplace listing.

## 3. Choose what the agent should do

Audit existing tracking without code changes

```
Use ravensight-instrumentation to audit our existing tracking.
Report missing, duplicate, or misleading events with source locations.
Do not edit application code.
```

Expand tracking in an existing product

```
Use ravensight-instrumentation to audit and expand our tracking.
Cover meaningful journeys, decisions, failures, retries and exits.
Preserve useful existing events, implement gaps, validate changes,
and update our event catalog and coverage report.
```

Start a new integration

```
Use ravensight-instrumentation to integrate Ravensight in this game.
Inspect the engine and SDK, then instrument the player journeys.
```

To work on selected code, name the subsystem or files in your request, for example: **Limit edits to inventory and crafting; follow callers and outcomes as needed.** Audit mode reviews existing choices. Expand mode implements missing coverage without duplicating useful events.

## 4. Review coverage and verify delivery

The agent produces an event catalog and coverage report, normally in `docs/analytics/events.md` and `docs/analytics/coverage.md`, or updates your existing documents. A chat-only audit can return its findings inline. Review the new events, retained tracking, deferred gaps, volume assumptions, and the checks the agent actually ran.

Code inspection, local execution, and events observed arriving are different evidence levels. Use a development environment for runtime verification. Installing the skill alone does not collect events, publish a build, or guarantee complete coverage of every possible player action.

## ChatGPT, access and costs

For a client without local skill discovery, provide [SKILL.md](https://github.com/Reality-Software-Entertainment/ravensight-skills/blob/main/skills/ravensight-instrumentation/SKILL.md) and its references, then explicitly ask it to follow the workflow. Supply the relevant source or a supported repository connection. Implementation requires editing tools; this pack does not install a connector or grant code access.

Local source is sufficient. Optional authorized MCP access can add live evidence and is metered; your agent provider may charge for its own work. Added events can increase event usage. The workflow respects existing collection controls and keeps event volume and payloads bounded.

## Updating or troubleshooting

If the installer reports different existing content, preserve your local edits before removing the old skill folder and reinstalling. To uninstall, remove that skill folder. If live data is unavailable, the agent can continue locally and must report delivery as unverified. See the repository setup guide for manual loading and supported installation paths.

Source: https://ravensight.io/docs/instrumentation-skill/
Last updated: 2026-11-15
