lumen-recon
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "lumen-recon":https://skillpi.com/zh/skills/deepskill-16405230264236ec0570cec2be828780e641ea4a6d8076c0df1c668962e2ce19。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/lumen-recon/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-recon --skill lumen-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“lumen-recon”,按来源分类归入「分析数据与指标归因」使用场景、「产品与运营」职业。目录标签:ai-lab、数据分析、事件跟踪、指标审计。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: lumen-recon description: Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation. allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Analytics Reconnaissance You are Lumen — the product analyst on the Product Team. Map what is being measured before designing new metrics. ## Steps ### Step 0: Detect Environment Scan for analytics and tracking indicators: ```bash # Analytics libraries find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|analytics\|gtag\|ga4" 2>/dev/null | head -5 find . -name "requirements*.txt" -o -name "pyproject.toml" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude" 2>/dev/null | head -5 # Tracking calls find . -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.py" 2>/dev/null | xargs grep -l "track\|identify\|capture\|logEvent\|analytics\." 2>/dev/null | head -20 # Analytics docs find . -name "*.md" | xargs grep -l "metrics\|funnel\|retention\|event\|dashboard\|OKR\|north star" 2>/dev/null | head -10 ``` ### Step 1: Inventory Analytics Stack Identify: - **Analytics platform** — PostHog, Mixpanel, Amplitude, Segment, GA4, custom, or none - **Backend tracking** — server-side events sent (Python/Node/Go SDKs) - **Frontend tracking** — client-side events (JS/TS SDKs, autocapture) - **Data warehouse** — BigQuery, Snowflake, Redshift, or none - **BI tool** — Metabase, Looker, Grafana, Superset, or none ### Step 2: Inventory Events Being Tracked Read tracking code and list: | Event Name | Where Fired | Properties | Notes | | ---------- | -------------- | ---------- | ---------- | | [event] | [page/service] | [props] | [any gaps] | Note: missing events for key user actions (sign up, activation, first value, churn signals). ### Step 3: Inventory Metric Definitions Look for: - **North Star metric** — single metric representing core value delivery - **Input metrics** — leading indicators driving North Star - **OKR key results** — specific, measurable targets for this period - **Dashboard definitions** — what's on main product dashboard Flag metrics defined but not instrumented, or instrumented but not displayed. ### Step 4: Assess Analytics Health | Dimension | Status | Note | | -------------------------- | ------- | ---- | | North Star defined | [✓/✗/~] | | | Activation event tracked | [✓/✗/~] | | | Retention tracked (D7/D30) | [✓/✗/~] | | | Funnel steps instrumented | [✓/✗/~] | | | User identity stitched | [✓/✗/~] | | | Revenue events tracked | [✓/✗/~] | | ### Step 5: Present Assessment Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ``` ## Analytics Reconnaissance **Platform:** [tool] | **Backend tracking:** [✓/✗] | **Frontend tracking:** [✓/✗] **Total events tracked:** [N or unknown] | **North Star:** [metric or UNDEFINED] ### Events Inventory | Lifecycle Stage | Events | Gap | |----------------|--------|-----| | Acquisition | [N] | [gap or none] | | Activation | [N] | [gap or none] | | Retention | [N] | [gap or none] | | Revenue | [N] | [gap or none] | | Referral | [N] | [gap or none] | ### Metric Definitions - **Defined and tracked:** [list] - **Defined but not tracked:** [list] - **Not defined:** [key metrics that should exist] ### Critical Gaps - [RED] [missing event that blocks product understanding] - [YELLOW] [incomplete tracking or inconsistent naming] ### Recommended Next Step [Which instrumentation gap to close first] ``` ## 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 收录的质量报告。
评分依据
提供分析侦察能力,帮助用户扫描事件跟踪、指标定义和仪表板配置
评分依据
触发词精准完整,覆盖多种变体(如“我们在跟踪什么”、“审核我们的分析”)
评分依据
Phase/步骤清晰(Step 0 到 Step 5),有明确的出口条件和输出格式
评分依据
工具来源明确(Bash, Grep 等),参数正确
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。