lumen-instrument

本条目收录公开技能“lumen-instrument”,按来源分类归入「分析数据与指标归因」使用场景、「产品与运营」职业。目录标签:ai-lab、埋点方案、事件分类、属性结构。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "lumen-instrument":https://skillpi.com/zh/skills/deepskill-35f0f88d11b031e5f480a06740b8832ceb1665e1c0e485e4e857964bbdfae3cc。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/lumen-instrument/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/lumen-instrument --skill lumen-instrument
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目收录公开技能“lumen-instrument”,按来源分类归入「分析数据与指标归因」使用场景、「产品与运营」职业。目录标签:ai-lab、埋点方案、事件分类、属性结构。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
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:

| Stage       | Event Name                | Trigger                    | Priority |
| ----------- | ------------------------- | -------------------------- | -------- |
| Acquisition | `user_signed_up`          | On successful registration | P0       |
| Activation  | `[aha_moment_event]`      | On first [core action]     | P0       |
| Engagement  | `[core_action]_completed` | On each [core action]      | P0       |
| Retention   | `session_started`         | On each return visit       | P1       |
| Revenue     | `upgrade_started`         | On paywall view            | P0       |
| Revenue     | `subscription_created`    | On successful payment      | P0       |
| Referral    | `invite_sent`             | On referral initiated      | P1       |

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).

### Step 5: Define the Tracking Plan Document

Produce tracking plan table for engineering team:

| Event Name | Trigger | Properties | Platform      | Priority | Owner |
| ---------- | ------- | ---------- | ------------- | -------- | ----- |
| [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.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值88/100
评分依据

解决产品团队埋点设计的高频刚需

触发精准92/100
评分依据

触发词覆盖全面,包含中英文变体

结构规范95/100
评分依据

7 个步骤逻辑清晰,从环境检测到交付闭环

执行可靠90/100
评分依据

Bash 命令包含错误处理机制

证据可验 (前四项均值)91/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。