product-tracking-business-case

product-tracking-business-case is a skill for Claude Code from Accoil/product-tracking-skills. It costs 110 tokens per session (2,521 once invoked), scanned A, original, MIT.

A skill for writing a business case for adding product telemetry, meaning data collected about how people use a product. It explains what the team cannot currently see, what analytics could show, and what implementation would involve.

In plain words
What is it for?
Use it to create a concise stakeholder document at .telemetry/business-case.md before modelling, auditing, designing, or implementing product tracking.
Why use it?
It helps decision-makers understand why tracking is needed before technical work begins. It connects better data with the analytics tools the company already uses.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the product-tracking-skills plugin — 7 skills, 1 agent shipped together

Good fit Use it to create a concise stakeholder document at .telemetry/business-case.md before modelling, auditing, designing, or implementing product tracking.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/accoil/product-tracking-skills/product-tracking-business-case
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Accoil/product-tracking-skills --skill product-tracking-business-case
Clone the repo
git clone --depth 1 https://github.com/Accoil/product-tracking-skills

Made for: Claude Code.

Or install product-tracking-skills, the plugin that ships this one along with the rest of its 7 skills, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for product-tracking-business-case

README.md
[![agentmods](https://agentmods.dev/badge/skills/accoil/product-tracking-skills/product-tracking-business-case/github.svg)](https://agentmods.dev/skills/accoil/product-tracking-skills/product-tracking-business-case)
Your own site
<a href="https://agentmods.dev/skills/accoil/product-tracking-skills/product-tracking-business-case"><img src="https://agentmods.dev/badge/skills/accoil/product-tracking-skills/product-tracking-business-case/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for product-tracking-business-case

Your own site · 80×15
<a href="https://agentmods.dev/skills/accoil/product-tracking-skills/product-tracking-business-case"><img src="https://agentmods.dev/badge/skills/accoil/product-tracking-skills/product-tracking-business-case.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,521 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00110 $0.02521
Opus 5 $0.00055 $0.01260
Sonnet 5 $0.00022 $0.00504
Haiku 4.5 $0.00011 $0.00252

Measured 12d ago against content hash d823ca1d06e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

product-tracking-business-case scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/product-tracking-business-case/SKILL.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Business Case

You are a product telemetry engineer writing a business case for adding analytics instrumentation to a product. The goal is a short, compelling document that a decision-maker can read in 5 minutes and say yes.

Core framing: The business case is not about "adding tracking" — it's about unlocking the analytics tools the team is already paying for. Most B2B SaaS teams pay for analytics platforms but can't get answers out of them because the data going in is wrong. Instrumentation fixes the input so the analytics investment pays off.

This skill sits outside the main telemetry lifecycle. It's the "convince" step that precedes everything else:

business-case → model → audit → design → guide → implement ← feature updates

Goal

Produce .telemetry/business-case.md — a stakeholder-ready document that shows what the team can't currently see, what proper instrumentation unlocks for the analytics tools they're already paying for, and how little effort it takes with AI-assisted tooling.

Prerequisites

None required. This skill works standalone — it's often the first thing run, before any technical telemetry work.

Optional context: If .telemetry/product.md exists, read it to make the case concrete and specific to the product. If it doesn't exist, gather enough context through conversation.

Process

1. Understand the Product

If .telemetry/product.md exists, read it and extract: product category, primary value action, user types, entity model, tech stack. Present what you found: "Based on the product model, this is a [category] product where [value action] is the core action."

If no product model exists, ask:

  • "What does your product do, in one sentence?"
  • "Who is this business case for?" (engineering lead, founder, PM, board)
  • "Do you have any analytics today, or is this greenfield?"

Keep it to 2-3 questions. You don't need a full product model — just enough to make the arguments specific.

2. Identify Blind Spots

Read the full file on GitHub · 190 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 190 lines · 110 tokens per session scan A d823ca1d06e5

Subscribe to this mod's changes

product-tracking-business-case is a skill published in the GitHub repository Accoil/product-tracking-skills (39 stars, last pushed 6mo ago), licensed MIT. It adds 110 tokens to every session and 2,521 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

high-ticket-conversion-architect

You are a Senior Conversion Architect specialized in premium B2B and luxury service sectors with offers above $10,000. Your job is not to maximize clicks, traffic, or form submissions. Your job is to engineer the page so that the right sophisticated buyer self-qualifies, builds conviction, and applies — while the…

wavect/ai-skills · 6 tokens

icp-discovery

You are a relentless ICP (Ideal Customer Profile) interrogator. Your job is to destroy vague answers and replace them with a single, specific human being in a specific situation. You use the Forces of Progress (Alan Klement), behavioral segmentation (Steve Blank), the Minimum Viable Segment (Christoph Janz), and the…

wavect/ai-skills · 4 tokens

B2B Cold Email Sequence Builder

Write high-converting B2B cold email sequences that get replies. Research-backed templates, personalization frameworks, and A/B testing plans included.

demo112/yunqu-ai-skills · 36 tokens

happiness-skill

A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.

kangarooking/cangjie-skill · 136 tokens

docx-comment-reply

Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.

foryourhealth111-pixel/Vibe-Skills · 39 tokens

asc-subscription-localization

Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.

rorkai/app-store-connect-cli-skills · 60 tokens