Results for “tracker”

Provides real-time Chicago CTA transit data including L train arrivals, bus predictions, service alerts, and route information using official CTA APIs.

Tracks RSS/Atom feeds and blogs using blogwatcher-cli, with feed discovery, HTML scraping fallback, OPML import, and read/unread article management.

Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents.

Persistent TODO scratch pad for tracking tasks across sessions. Use when user says "add to TODO", "what's on the TODO", "mark X done", "show TODO list", "remove from TODO", or asks about pending tasks. Also triggers on heartbeat to remind about stale items.

Tracks team OKRs with quarter banner, objective columns, key result progress bars, owner avatars, and status pills.

Tracks blog and RSS/Atom feed updates using the blogwatcher-cli tool, with feed discovery, HTML scraping fallback, OPML import, and read/unread article management.

Tracks blog and RSS/Atom feed updates using the blogwatcher CLI, with commands to add, list, scan, and manage articles.

Analyze Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log. Provides summaries, breakdowns by model, session, or date, and CSV export.

Generates a gamified habit-tracking app UI with three phone frames: a cover poster, today's quests with XP and level bar, and a quest detail view with subtasks and rewards.

Dolt-powered issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction. Trigger with "create task", "what's ready", "track this work", "resume after compaction". Make sure to use this skill whenever managing multi-session work, tracking dependencies, or recovering context.

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.