smithery/gtmagents

versioning-dashboard

Dashboard pattern for tracking doc coverage across product versions, locales, and channels.

Installation

$ npx skills add smithery/gtmagents --skill versioning-dashboard

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,393 B
  • docs SUMMARY.md 119 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Versioning Dashboard Skill

When to Use

  • Managing multiple product versions, editions, or deployment models.
  • Coordinating deprecations, migrations, and long-term support documentation.
  • Reporting readiness and gaps to leadership during launches.

Framework

  1. Version Inventory – list active versions, release dates, support windows, and owners.
  2. Artifact Coverage – matrix of docs/tutorials/guides per version + locale + channel.
  3. Change Log Hooks – tie version changes to release notes, migration guides, and alert cadence.
  4. Risk & Action Log – highlight outdated assets, missing locales, or compliance needs.
  5. Reporting Layer – KPIs (coverage %, SLA adherence, reader metrics) with filters for audience or product area.

Templates

  • Dashboard sheet with pivoted coverage views and status chips.
  • Migration tracker linking deprecated features to comms + doc updates.
  • Executive summary slide with version highlights and asks.

Tips

  • Integrate with source control metadata to auto-update coverage status.
  • Highlight dependencies (SDKs, integrations) when versions shift.
  • Pair with plan-documentation-roadmap, publish-release-documentation, and update-api-reference workflows.