How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

technical-change-tracker - Skill

Name: technical-change-tracker
Author: sickn33

Imported from sickn33/agentic-awesome-skills (skills/technical-change-tracker/SKILL.md). Install upstream with npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker. Copyright stays with the author.

Technical Change Tracker

Overview

Track every code change with structured JSON records and accessible HTML output. Ensures AI bot sessions can resume seamlessly when previous sessions expire or are abandoned.

When to Use This Skill

Use when you need structured change tracking across AI coding sessions
Use when a bot session expires mid-task and the next session needs full context to resume
Use when onboarding a project with undocumented change history

How It Works

State Machine

planned -> in_progress -> implemented -> tested -> deployed
             |
             +-> blocked

Commands

Session Handoff

Each TC stores: progress summary, next steps, blockers, key context, and files in progress — so the next bot session picks up exactly where the last left off.

Non-Blocking

This entrypoint bundles no runtime, commands or background agents. Use an already reviewed installation only after inspecting its current interface; delegation and scheduling require explicit authorization.

Features

Structured JSON records with append-only revision history
Test cases with log snippet evidence
WCAG AA+ accessible HTML output (dark theme, rem-based fonts)
CSS-only dashboard with status filters
Python stdlib only — zero external dependencies
Retroactive bulk creation from git history via /tc retro

Full Repository

https://github.com/Elkidogz/technical-change-skill — MIT License

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Execution boundaries

The listed features describe the external project, not capabilities installed by this file. Do not invent /tc execution or accessibility certification. Track only observed status transitions; implemented, tested and deployed require different evidence. Keep private paths and logs out of shared reports, and preserve existing records.

Install technical-change-tracker and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "sickn33-agentic-awesome-skills-technical-change-tracker", "kind": "skill", "name": "technical-change-tracker", "description": "Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity", "publisher": "sickn33", "version": "1.0.0", "capabilities": { "domains": [ "coding", "hr" ], "tags": [ "skill-md", "change-tracking", "session-handoff", "documentation", "accessibility", "state-machine", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity" ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/sickn33/agentic-awesome-skills", "path": "skills/technical-change-tracker/SKILL.md", "ref": "HEAD", "url": "https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/skills/technical-change-tracker/SKILL.md", "key": "sickn33/agentic-awesome-skills/skills/technical-change-tracker/SKILL.md" }, "tools": [ "claude", "cursor", "gemini", "codex" ] }, "instructions": "# Technical Change Tracker\n\n## Overview\n\nTrack every code change with structured JSON records and accessible HTML output. Ensures AI bot sessions can resume seamlessly when previous sessions expire or are abandoned.\n\n## When to Use This Skill\n\n- Use when you need structured change tracking across AI coding sessions\n- Use when a bot session expires mid-task and the next session needs full context to resume\n- Use when onboarding a project with undocumented change history\n\n## How It Works\n\n### State Machine\n\n```\nplanned -> in_progress -> implemented -> tested -> deployed\n |\n ", "cost": { "context_tokens": 566 } }

technical-change-tracker

About

Technical Change Tracker

Overview

When to Use This Skill

How It Works

State Machine

Commands

Session Handoff

Non-Blocking

Features

Full Repository

Limitations

Execution boundaries

Install technical-change-tracker and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews