chronicle

What it does

Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.

Try it when you need to…

1. The user makes a reference to their recent work
2. For which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request
3. Where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle
4. Asks what you can see from the screen

Your first run

1. Copy or install the complete skill folder so scripts, references, assets, and metadata stay together.
2. Open the target repo and read its local agent instructions before invoking the skill.
3. Name the outcome you want, the repo constraints, and any files or routes Codex should avoid.
4. Review generated scripts, docs, or code before adopting the result into your workflow.

New to this collection? Read Getting started for package structure, setup, and license notes.

If something gets stuck