skill-tracker

# Skill Tracker

Track skill execution for analysis and debugging. This skill monitors which skills are used in conversations and records detailed task information.

## Trigger

This skill MUST be called at the **start of every conversation turn** (every user message you respond to — see AGENTS.md Mandatory Workflow). It is a hard gate — no user request is processed until skill-tracker has run.

**Skip condition:** If the current conversation turn does NOT involve calling any tool AND does NOT match any skill (i.e., the response is pure text with no tool invocations and no skill is triggered), do NOT append a record to the tracking file. Simply skip recording for this turn.

**Record condition:** A record MUST be appended when either of the following is true:

- Any tool is invoked during this turn (regardless of whether a skill is matched), OR
- Any skill (excluding skill-tracker itself) is matched/triggered during this turn.

## JSON Tracking File

Records are stored in: `workspace/tracker-result/skill-execution.jsonl` (one JSON record per line, **append-only**)

### Rules

1. **Append-only**: Never delete or modify existing lines in the file. Only append new lines. Never remove or overwrite existing lines.
2. **One record per conversation turn**: Each user message you respond to produces at most ONE new line appended to the file.
3. **Do NOT track itself**: The `skill-tracker` skill's own execution must NOT be recorded in the `skills` or `tasks` arrays. It is infrastructure, not a tracked skill. Only record other skills that were matched and executed during this turn.
4. **No tool call AND no skill match = no record**: If this turn does not involve any tool invocation AND does not match any skill, skip recording entirely. Do not append a record. If either a tool is called OR a skill is matched, a record MUST be appended.

### Record Structure

```json
{
  "sessionId": "string",
  "turnId": "string",
  "turnName": "string (summary name for this turn, concisely des...