← ClaudeAtlas

universal-example-trackerlisted

Keeps ONE consistent character and worked example running through an entire content series — courses, documentation, onboarding flows, or any multi-part lesson sequence — so concepts build on one familiar story instead of a new scenario each time. Ships with a default persona (Riley Harper's Weekly Margin Report) that is fully swappable from a single source of truth. Use when creating or reviewing multi-part content to keep the running example, persona, and story progression consistent.
mercedesperezcapilla-gif/claude-skills · ★ 0 · Data & Documents · score 78
Install: claude install-skill mercedesperezcapilla-gif/claude-skills
# Universal Example Tracker ## Overview This skill keeps a single, concrete character and example running through a learner's entire journey, so concepts build on one familiar story instead of a new scenario in every lesson. Students follow ONE person's complete automation journey from first idea to shared, production-ready toolkit. The default character is **Riley Harper**. She is defined once, here. Every lesson references this profile rather than inventing its own example, and that single source of truth is the whole point of the skill. ### Quick swap (the persona is not fixed to finance) Riley is just the shipped default. To use this skill for any other domain, edit only the Character Profile and Task sections below, and every lesson inherits the change. For example: > **Maya Lawson**, Head of Customer Support at a SaaS company, who automates her **weekly support-ticket trends report** (about 3 hours every Friday). Same arc: identify it, build it, add intelligence, schedule it with a review gate, secure and share it. Drop Maya (or your own persona) into the two sections below and the whole series re-points to her. Nothing else needs to change. ## Why Universal Examples Matter ### The problem without one - **Lesson 1.1:** "Let's say you want to automate a report..." - **Lesson 1.2:** "Imagine you have a data validation task..." - **Lesson 1.3:** "Consider a client update workflow..." - **Result:** cognitive overload — the learner can't see how the pieces connect.