[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E2V5MZJAC6E159P53RTYG2":3,"skill-same:01M6E2V5MZJAC6E159P53RTYG2":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6E2V5MZJAC6E159P53RTYG2","lumen-instrument",null,"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\".","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Flumen-instrument\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"lumen","lumen instrument","instrument","edit","when","track","websearch","events","feature","instrumentation","up","schema","design","write","read","plan","Bash","taxonomy","Tools","SET","product","code","analytics","hello","2026-11-10 10:12:30",false,"---\nname: lumen-instrument\ndescription: 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\".\nallowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion\nversion: 0.6.4\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [product, analytics, instrument]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Instrumentation Plan\n\nYou are Lumen — the product analyst on the Product Team. Design tracking before any code is written.\n\n## Steps\n\n### Step 0: Detect Environment\n\nScan for existing analytics setup:\n\n```bash\nfind . -name \"package.json\" | xargs grep -l \"posthog\\|mixpanel\\|segment\\|amplitude\\|heap\\|rudderstack\" 2>\u002Fdev\u002Fnull\nfind . -name \"*.ts\" -o -name \"*.tsx\" -o -name \"*.py\" 2>\u002Fdev\u002Fnull | xargs grep -rn \"analytics\\.track\\|posthog\\.capture\\|mixpanel\\.track\\|identify(\" 2>\u002Fdev\u002Fnull | head -20\n```\n\nIdentify analytics platform and existing event naming convention.\n\n### Step 1: Establish Event Taxonomy\n\nUse one of these two naming conventions (match existing if found):\n\n**Object-Action (recommended):**\n`[object]_[action]` → `user_signed_up`, `file_exported`, `payment_completed`\n\n**Screen-Action:**\n`[screen]_[action]` → `onboarding_completed`, `dashboard_viewed`, `settings_saved`\n\nRules:\n\n- Snake case, always\n- Past tense for completed actions (`signed_up`, not `sign_up`)\n- Present tense for views (`page_viewed`, `modal_opened`)\n- No PII in event names\n\n### Step 2: Map the User Journey to Events\n\nWalk critical user journey and define every event to capture:\n\n| Stage       | Event Name                | Trigger                    | Priority |\n| ----------- | ------------------------- | -------------------------- | -------- |\n| Acquisition | `user_signed_up`          | On successful registration | P0       |\n| Activation  | `[aha_moment_event]`      | On first [core action]     | P0       |\n| Engagement  | `[core_action]_completed` | On each [core action]      | P0       |\n| Retention   | `session_started`         | On each return visit       | P1       |\n| Revenue     | `upgrade_started`         | On paywall view            | P0       |\n| Revenue     | `subscription_created`    | On successful payment      | P0       |\n| Referral    | `invite_sent`             | On referral initiated      | P1       |\n\nPriority: **P0** = must ship with feature, **P1** = nice-to-have on launch, **P2** = backlog.\n\n### Step 3: Define Property Schema\n\nFor each P0 event, define properties to capture:\n\n```\nEvent: [event_name]\nTrigger: [when exactly does this fire?]\nProperties:\n  - [property_name]: [type] — [description] — [example value]\n  - [property_name]: [type] — [description] — [example value]\nUser properties to identify:\n  - [property]: [when to set it]\n```\n\n**Always include on every event:**\n\n- `timestamp` — automatic\n- `user_id` — set at identify() call\n- `session_id` — set at session start\n- `platform` — web \u002F iOS \u002F Android\n\n**Never include in events (PII):**\n\n- Email addresses, full names, phone numbers, payment details, passwords\n\n### Step 4: Write the Identify Call\n\nEvery analytics platform needs an `identify()` call on login\u002Fsign-up:\n\n```typescript\n\u002F\u002F Example for PostHog \u002F Mixpanel \u002F Segment\nanalytics.identify(userId, {\n  created_at: user.createdAt, \u002F\u002F ISO8601\n  plan: user.plan, \u002F\u002F free | pro | enterprise\n  company_id: user.companyId, \u002F\u002F for B2B products\n  \u002F\u002F Add product-specific traits below\n});\n```\n\nDefine which user traits to set on identify, and when to update them (e.g., on plan upgrade).\n\n### Step 5: Define the Tracking Plan Document\n\nProduce tracking plan table for engineering team:\n\n| Event Name | Trigger | Properties | Platform      | Priority | Owner |\n| ---------- | ------- | ---------- | ------------- | -------- | ----- |\n| [event]    | [when]  | [props]    | [web\u002FiOS\u002Fall] | [P0\u002FP1]  | [eng] |\n\n### Step 6: Implementation Checklist\n\nBefore shipping:\n\n- [ ] All P0 events implemented and verified in dev environment\n- [ ] `identify()` call fires on sign-up and login\n- [ ] No PII in event properties or names\n- [ ] Event names follow naming convention\n- [ ] Events verified in analytics platform (live event stream)\n- [ ] Lumen notified when tracking is live (to validate data quality)\n\n### Step 7: Present Instrumentation Plan\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\nList all P0 events first, then P1, then note what is deliberately out of scope for this release.\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-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.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Instrumentation Plan\n\nYou are Lumen — the product analyst on the Product Team. Design tracking before any code is written.\n\n## Steps\n\n### Step 0: Detect Environment\n\nScan for existing analytics setup:\n\n```bash\nfind . -name \"package.json\" | xargs grep -l \"posthog\\|mixpanel\\|segment\\|amplitude\\|heap\\|rudderstack\" 2>\u002Fdev\u002Fnull\nfind . -name \"*.ts\" -o -name \"*.tsx\" -o -name \"*.py\" 2>\u002Fdev\u002Fnull | xargs grep -rn \"analytics\\.track\\|posthog\\.capture\\|mixpanel\\.track\\|identify(\" 2>\u002Fdev\u002Fnull | head -20\n```\n\nIdentify analytics platform and existing event naming convention.\n\n### Step 1: Establish Event Taxonomy\n\nUse one of these two naming conventions (match existing if found):\n\n**Object-Action (recommended):**\n`[object]_[action]` → `user_signed_up`, `file_exported`, `payment_completed`\n\n**Screen-Action:**\n`[screen]_[action]` → `onboarding_completed`, `dashboard_viewed`, `settings_saved`\n\nRules:\n\n- Snake case, always\n- Past tense for completed actions (`signed_up`, not `sign_up`)\n- Present tense for views (`page_viewed`, `modal_opened`)\n- No PII in event names\n\n### Step 2: Map the User Journey to Events\n\nWalk critical user journey and define every event to capture:\n\n| Stage       | Event Name                | Trigger                    | Priority |\n| ----------- | ------------------------- | -------------------------- | -------- |\n| Acquisition | `user_signed_up`          | On successful registration | P0       |\n| Activation  | `[aha_moment_event]`      | On first [core action]     | P0       |\n| Engagement  | `[core_action]_completed` | On each [core action]      | P0       |\n| Retention   | `session_started`         | On each return visit       | P1       |\n| Revenue     | `upgrade_started`         | On paywall view            | P0       |\n| Revenue     | `subscription_created`    | On successful payment      | P0       |\n| Referral    | `invite_sent`             | On referral initiated      | P1       |\n\nPriority: **P0** = must ship with feature, **P1** = nice-to-have on launch, **P2** = backlog.\n\n### Step 3: Define Property Schema\n\nFor each P0 event, define properties to capture:\n\n```\nEvent: [event_name]\nTrigger: [when exactly does this fire?]\nProperties:\n  - [property_name]: [type] — [description] — [example value]\n  - [property_name]: [type] — [description] — [example value]\nUser properties to identify:\n  - [property]: [when to set it]\n```\n\n**Always include on every event:**\n\n- `timestamp` — automatic\n- `user_id` — set at identify() call\n- `session_id` — set at session start\n- `platform` — web \u002F iOS \u002F Android\n\n**Never include in events (PII):**\n\n- Email addresses, full names, phone numbers, payment details, passwords\n\n### Step 4: Write the Identify Call\n\nEvery analytics platform needs an `identify()` call on login\u002Fsign-up:\n\n```typescript\n\u002F\u002F Example for PostHog \u002F Mixpanel \u002F Segment\nanalytics.identify(userId, {\n  created_at: user.createdAt, \u002F\u002F ISO8601\n  plan: user.plan, \u002F\u002F free | pro | enterprise\n  company_id: user.companyId, \u002F\u002F for B2B products\n  \u002F\u002F Add product-specific traits below\n});\n```\n\nDefine which user traits to set on identify, and when to update them (e.g., on plan upgrade).\n\n### Step 5: Define the Tracking Plan Document\n\nProduce tracking plan table for engineering team:\n\n| Event Name | Trigger | Properties | Platform      | Priority | Owner |\n| ---------- | ------- | ---------- | ------------- | -------- | ----- |\n| [event]    | [when]  | [props]    | [web\u002FiOS\u002Fall] | [P0\u002FP1]  | [eng] |\n\n### Step 6: Implementation Checklist\n\nBefore shipping:\n\n- [ ] All P0 events implemented and verified in dev environment\n- [ ] `identify()` call fires on sign-up and login\n- [ ] No PII in event properties or names\n- [ ] Event names follow naming convention\n- [ ] Events verified in analytics platform (live event stream)\n- [ ] Lumen notified when tracking is live (to validate data quality)\n\n### Step 7: Present Instrumentation Plan\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\nList all P0 events first, then P1, then note what is deliberately out of scope for this release.\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-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.\n",{"name":5,"tags":61,"author":62,"license":15,"version":63,"description":7,"allowed-tools":64,"compatibility":65},[52,54,34],"tonone-ai \u003Chello@tonone.ai>","0.6.4","Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","skills\u002Flumen-instrument",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add tonone-ai\u002Ftonone --skill lumen-instrument",{"tool":82,"command":83},"bunx","bunx skills add tonone-ai\u002Ftonone --skill lumen-instrument",{"tool":85,"command":86},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill lumen-instrument","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Flumen-instrument\u002FSKILL.md",true,[],[91,99,106,111,116,123],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":98},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":98},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":107,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":98},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":112,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":98},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":98},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":98},"01M72NE7AS597YW6999C56CESR","helm-init","Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[]]