New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Lumen Instrument

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools.

MITAuto-check: notesData & Analytics

Install Lumen Instrument

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lumen-instrument -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace lumen-instrument --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/lumen-instrument .claude/skills/lumen-instrument && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lumen-instrument
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
406 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools.

  • Works in 8 steps: Detect Environment → Establish Event Taxonomy → Map the User Journey to Events → …
  • Asked to what should we track
  • SKILL.md covers Steps and Delivery
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lumen Instrument is an agent skill from jeremylongshore/tons-of-skills-marketplace. Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Use when asked to "what should we track", "instrumentation plan", "set up analytics events", "analytics event schema", "tracking plan", or "instrument this feature".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Data & Analytics, covering Product analytics. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked to what should we track
  • Instrumentation plan
  • Set up analytics events
  • Analytics event schema

Example prompts

  • “what should we track”
  • “instrumentation plan”
  • “set up analytics events”
  • “/lumen-instrument”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Detect Environment
  2. Establish Event Taxonomy
  3. Map the User Journey to Events
  4. Define Property Schema
  5. Write the Identify Call
  6. Define the Tracking Plan Document
  7. Implementation Checklist
  8. Present Instrumentation Plan

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • Task
    • TodoWrite

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lumen Instrument loads about 1.2k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 406 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 406 words, ~1,215 tokens.

Download SKILL.mdSave it as .claude/skills/lumen-instrument/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lumen-instrument
description
Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Use when asked to "what should we track", "instrumentation plan", "set up analytics events", "analytics event schema", "tracking plan", or "instrument this feature".
allowed-tools
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version
0.6.4
author
tonone-ai <hello@tonone.ai>
license
MIT

Instrumentation Plan

You are Lumen — the product analyst on the Product Team. Design tracking before any code is written.

Steps

Step 0: Detect Environment

Scan for existing analytics setup:

bash
find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|rudderstack" 2>/dev/null
find . -name "*.ts" -o -name "*.tsx" -o -name "*.py" 2>/dev/null | xargs grep -rn "analytics\.track\|posthog\.capture\|mixpanel\.track\|identify(" 2>/dev/null | head -20

Identify analytics platform and existing event naming convention.

Step 1: Establish Event Taxonomy

Use one of these two naming conventions (match existing if found):

Object-Action (recommended): [object]_[action] → user_signed_up, file_exported, payment_completed

Screen-Action: [screen]_[action] → onboarding_completed, dashboard_viewed, settings_saved

Rules:

  • Snake case, always
  • Past tense for completed actions (signed_up, not sign_up)
  • Present tense for views (page_viewed, modal_opened)
  • No PII in event names
Step 2: Map the User Journey to Events

Walk critical user journey and define every event to capture:

StageEvent NameTriggerPriority
Acquisitionuser_signed_upOn successful registrationP0
Activation[aha_moment_event]On first [core action]P0
Engagement[core_action]_completedOn each [core action]P0
Retentionsession_startedOn each return visitP1
Revenueupgrade_startedOn paywall viewP0
Revenuesubscription_createdOn successful paymentP0
Referralinvite_sentOn referral initiatedP1

Priority: P0 = must ship with feature, P1 = nice-to-have on launch, P2 = backlog.

Step 3: Define Property Schema

For each P0 event, define properties to capture:

Event: [event_name]
Trigger: [when exactly does this fire?]
Properties:
  - [property_name]: [type] — [description] — [example value]
  - [property_name]: [type] — [description] — [example value]
User properties to identify:
  - [property]: [when to set it]

Always include on every event:

  • timestamp — automatic
  • user_id — set at identify() call
  • session_id — set at session start
  • platform — web / iOS / Android

Never include in events (PII):

  • Email addresses, full names, phone numbers, payment details, passwords
Step 4: Write the Identify Call

Every analytics platform needs an identify() call on login/sign-up:

typescript
// Example for PostHog / Mixpanel / Segment
analytics.identify(userId, {
  created_at: user.createdAt, // ISO8601
  plan: user.plan, // free | pro | enterprise
  company_id: user.companyId, // for B2B products
  // Add product-specific traits below
});

Define which user traits to set on identify, and when to update them (e.g., on plan upgrade).

Show full SKILL.md (159 more words)Show less
Step 5: Define the Tracking Plan Document

Produce tracking plan table for engineering team:

Event NameTriggerPropertiesPlatformPriorityOwner
[event][when][props][web/iOS/all][P0/P1][eng]
Step 6: Implementation Checklist

Before shipping:

  • All P0 events implemented and verified in dev environment
  • identify() call fires on sign-up and login
  • No PII in event properties or names
  • Event names follow naming convention
  • Events verified in analytics platform (live event stream)
  • Lumen notified when tracking is live (to validate data quality)
Step 7: Present Instrumentation Plan

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

List all P0 events first, then P1, then note what is deliberately out of scope for this release.

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/lumen-instrument of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Lumen Instrument next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lumen Instrument compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lumen Instrument this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: NotesMIT
PostHog CLI Queriesdebugtheworldbot/keyStats1.5k—~1.2kAutomated safety check: PassMIT
Retentioneering Contributingretentioneering/retentioneering-tools927—~1.8kAutomated safety check: PassApache-2.0
Retentioneering Product Analyticsretentioneering/retentioneering-tools927—~1.6kAutomated safety check: PassApache-2.0
Feature Analytics Instrumentation Plannermistralai/mistral-vibe5.1k—~2.2kAutomated safety check: PassApache-2.0
Funnel Analysisliangdabiao/claude-data-analysis-ultra-main2901 repos~781Automated safety check: NotesNone

Similar skills

  • PostHog CLI Queries

    debugtheworldbot/keyStats

    Runs HogQL queries against this project's PostHog data from the terminal using posthog-cli, with bundled scripts for dashboard metadata the CLI itself has no command for.

    1.5k GitHub stars~1.2k tokensUpdated 8 days ago
    Data & AnalyticsAuto-check passed

  • Retentioneering Contributing

    retentioneering/retentioneering-tools

    Help the user turn their Retentioneering ideas, friction reports, bug findings, or feature needs into high-quality upstream contributions: from capturing and validating the idea, through minimal…

    927 GitHub stars~1.8k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed

  • Retentioneering Product Analytics

    retentioneering/retentioneering-tools

    Analyze event logs, clickstreams, user paths, product funnels, retention, behavioral segments, transition graphs, step matrices, sequence patterns, and customer journeys using Retentioneering.

    927 GitHub stars~1.6k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed

  • Feature Analytics Instrumentation Planner

    mistralai/mistral-vibe

    Official

    Plans which analytics events and properties a new feature needs, checks them against the existing event registry, and verifies them per environment.

    5.1k GitHub stars~2.2k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed

  • Funnel Analysis

    liangdabiao/claude-data-analysis-ultra-main

    Analyze user conversion funnels, calculate step-by-step conversion rates, create interactive visualizations, and identify optimization opportunities.

    290 GitHub starsUsed in 1 repo~781 tokens
    Data & AnalyticsAuto-check: notes

  • Event Tracking

    linuxfoundation/insights

    Add event tracking calls to Vue/Nuxt components in the Insights app using the useTrackEvent composable.

    282 GitHub stars~1.9k tokensUpdated 9 days ago
    Data & AnalyticsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Lumen Instrument

What does Lumen Instrument do?

Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Lumen Instrument is an agent skill from jeremylongshore/tons-of-skills-marketplace. Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools.

When should I use Lumen Instrument?

Lumen Instrument fits situations like: asked to what should we track; instrumentation plan; set up analytics events; analytics event schema.

How do I install Lumen Instrument in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lumen-instrument -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/lumen-instrument in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lumen-instrument in your project. Claude Code loads it when a task matches its description.

How do I install Lumen Instrument in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lumen-instrument -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/lumen-instrument in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lumen-instrument in your project. Codex loads it when a task matches its description.

Can I use Lumen Instrument in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lumen-instrument -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lumen-instrument, .gemini/skills/lumen-instrument, .github/skills/lumen-instrument and .opencode/skills/lumen-instrument in your project.

What does Lumen Instrument need to run?

SKILL.md names no scripts, command-line tools or credentials: Lumen Instrument is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.

Does Lumen Instrument access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lumen Instrument safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Lumen Instrument use?

Lumen Instrument is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lumen Instrument use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lumen Instrument?

Skills that share tags, products or a category with Lumen Instrument: PostHog CLI Queries (debugtheworldbot/keyStats, 1.5k stars), Retentioneering Contributing (retentioneering/retentioneering-tools, 927 stars), Retentioneering Product Analytics (retentioneering/retentioneering-tools, 927 stars) and Feature Analytics Instrumentation Planner (mistralai/mistral-vibe, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lumen Instrument?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.