adoption-funnel

adoption-funnel is a skill for Claude Code, Codex from uthumany/uthy-legacy-os. It costs 28 tokens per session (1,087 once invoked), scanned A, original, MIT.

A framework for finding where users stop adopting a product feature, from first learning about it to using it repeatedly.

In plain words
What is it for?
Use it to measure each adoption stage, locate drop-offs, design activation flows, and improve engagement with an existing feature.
Why use it?
It separates problems such as poor discoverability, unclear value, low motivation, and feature mismatch instead of treating low usage as one issue.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to measure each adoption stage, locate drop-offs, design activation flows, and improve engagement with an existing feature.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uthumany/uthy-legacy-os/adoption-funnel
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 uthumany/uthy-legacy-os --skill adoption-funnel
Clone the repo
git clone --depth 1 https://github.com/uthumany/uthy-legacy-os

Made for: Claude Code, Codex.

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 adoption-funnel

README.md
[![agentmods](https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/adoption-funnel/github.svg)](https://agentmods.dev/skills/uthumany/uthy-legacy-os/adoption-funnel)
Your own site
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/adoption-funnel"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/adoption-funnel/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 adoption-funnel

Your own site · 80×15
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/adoption-funnel"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/adoption-funnel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,087 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.00028 $0.01087
Opus 5 $0.00014 $0.00544
Sonnet 5 $0.00006 $0.00217
Haiku 4.5 $0.00003 $0.00109

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

Security

Grade A, and why

adoption-funnel 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/improve/adoption-funnel/SKILL.md · 110 lines

How it starts

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

Adoption Funnel

Overview

You shipped it, but nobody's using it. Feature adoption analysis helps you understand why — is it discoverability, comprehension, motivation, or the wrong feature? This skill covers funnel analysis, activation metrics, and adoption improvement tactics.

When to Use

  • A shipped feature has < expected usage
  • You need to understand where users drop off in the adoption journey
  • Designing activation flows for new features
  • You want to improve feature engagement systematically
  • Don't use for: core product adoption (broader analysis needed), one-day-old features (too early to measure)

Instructions

1. Define the Adoption Funnel

Map the user's journey from awareness to ongoing use:

  1. Awareness: User knows the feature exists
  2. Discovery: User finds the feature
  3. Understanding: User knows what it does and why to use it
  4. First use: User tries the feature for the first time
  5. Value realization: User gets value from the feature
  6. Continued use: User comes back and uses it again

2. Measure Each Stage

For each stage, instrument and measure:

  • Awareness: % of users who saw the announcement/in-app notification
  • Discovery: % who navigated to the feature's location
  • Understanding: % who clicked/opened the feature
  • First use: % who completed the primary action
  • Value realization: % who reached a success milestone
  • Continued use: % who used it again within 7 days

3. Identify the Drop-off

Where do most users disappear?

  • 🔴 Awareness → Discovery: Visibility problem (need better placement/announcement)
  • 🔴 Discovery → Understanding: Comprehension problem (need better labeling/onboarding)
  • 🔴 Understanding → First use: Motivation problem (need better value prop or lower friction)
  • 🔴 First use → Value realization: UX problem (feature is hard to use)
  • 🔴 Value → Continued use: Retention problem (feature doesn't deliver ongoing value)

4. Design Improvements

Based on the drop-off:

  • Visibility: In-app announcement, badge/tooltip, email campaign
  • Comprehension: Better copy, short video, tooltip on first hover
  • Motivation: Value prop showcase, "users who do X get Y% better results"
  • UX: Reduce steps, add defaults, improve feedback
  • Retention: Email reminders, progress tracking, social proof

Read the full file on GitHub · 110 lines

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 · 110 lines · 28 tokens per session scan A 8afab01287e7

Subscribe to this mod's changes

adoption-funnel is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,087 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens