[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D8GCBVVG8FHE4G3QFPGMTZ":3,"skill-same:01M6D8GCBVVG8FHE4G3QFPGMTZ":86},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6D8GCBVVG8FHE4G3QFPGMTZ","onboarding-map",null,"Plan signup, setup, activation, first success, onboarding drop-offs, and time-to-value for each lifecycle persona","GeorgeQLe\u002Fagentic-skills","GeorgeQLe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21134126?v=4","01M6D2JP418S0VGJGF8M93EC3H","George Le","01M6D2JPBAKYD82TA5FS6HKQ3D",1,"MIT","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fcustomer-lifecycle\u002Fclaude\u002Fonboarding-map\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"onboarding","onboarding map","map","lifecycle","analysis","persona","plan","page","v0","alignment","activation","drop","first","time","visual","deep","signup","app","setup","2026-11-10 10:12:30",false,"---\nname: onboarding-map\ndescription: Plan signup, setup, activation, first success, onboarding drop-offs, and time-to-value for each lifecycle persona\ntype: analysis\nversion: v0.5\nrequired_conventions: [alignment-page]\nargument-hint: \"[optional: app, persona, or onboarding segment]\"\ncontext_intake: deep\nvisual_tier: visual\n---\n\n## Pack Availability Guard\n\nBefore telling the user to run a skill from another project-local pack, check `.agents\u002Fproject.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install \u003Cpack>` from the project shell, instead of the target skill.\n\n# Onboarding Map\n\n\n\nCreate the stage-level onboarding plan that expands `research\u002Fjourney-map.md`.\n\n## Process\n\n### 0. Product-Path Scope Resolution\n\nResolve research scope by product path before using code or app structure as a hint:\n\n1. If `$ARGUMENTS` names a non-archived `research\u002F{slug}\u002F` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product\u002Fapp name, not the ICP, audience, or segment label.\n2. If `$ARGUMENTS` names only `research\u002F_archive\u002F{slug}\u002F` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.\n3. Read `research\u002F.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research\u002F_archive\u002F` from active target selection.\n4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.\n5. If no active manifest target exists, list non-archived product directories under `research\u002F`, excluding `research\u002F_archive\u002F` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.\n6. If no product directories exist, use flat `research\u002F` single-product mode.\n7. Detect monorepo\u002Fapp\u002Fpackage structure only as a secondary hint. Suggest creating a missing `research\u002F{slug}\u002F` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research\u002F{slug}\u002F`.\n\nWhen product path `{slug}` is active, read and write research under `research\u002F{slug}\u002F`, specs under `specs\u002F{slug}\u002F`, and treat top-level `research\u002F*.md` files as flat-mode documents or cross-path summaries.\n\n1. Resolve product-path scope using the same `research\u002F{slug}\u002F` convention as `\u002Fjourney-map`.\n2. Read `research\u002F.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading; treat legacy `abandoned` as `archived` and exclude archived\u002Fdeferred\u002Frevisit\u002Fpromoted paths plus `research\u002F_archive\u002F` scopes from active target selection. Scope the onboarding map to the active product path by default.\n3. Require `research\u002Fjourney-map.md` or `research\u002F{slug}\u002Fjourney-map.md`; if missing, recommend `\u002Fjourney-map`.\n4. Load ICP, journey map, specs, customer feedback, metrics, and current product routes\u002Fcomponents when present.\n5. Interview and recommend around: signup entry points, account creation, required setup, imports\u002Fintegrations, team invites, empty states, first-session guidance, first 5 minutes\u002Fhour\u002Fday, aha threshold, drop-offs, recovery, and support touchpoints.\n6. Present the proposed onboarding model before writing.\n7. Write `research\u002Fonboarding-map.md` and `research\u002Fonboarding-map-interview.md` in flat mode, or `research\u002F{slug}\u002Fonboarding-map.md` and `research\u002F{slug}\u002Fonboarding-map-interview.md` when product-path scope is active, after validation.\n\n## Output Shape\n\n```markdown\n# Onboarding Map\n\n> Based on: research\u002Fjourney-map.md\n> Date: YYYY-MM-DD\n\n## Summary\n## Personas And Entry Points\n## Signup And Setup Flow\n## Activation Path\n## First Success\n## Drop-Offs And Recovery\n## Instrumentation Needs\n## Product Gaps\n## Next Steps\n```\n\n## Interview Protocol\n\n**Step 1 — Gather context.** Read `.agents\u002Fproject.json`, README, CLAUDE.md, existing research and specs, git history, and any argument-provided context. Build an internal evidence base before asking questions.\n\n**Step 2 — Assumptions manifest.** Present 3–7 assumptions about the user's situation, goals, and constraints. Tag each with source (`[from prompt]`, `[from repo]`, `[from research]`, `[inferred]`). Ask the user to confirm, correct, or flag before proceeding.\n\n**Step 3 — Focused interview.** Ask 1–3 questions per turn via `AskUserQuestion`. Research and recommend by default — present options with a recommended default. Continue until all areas are covered or the user signals enough.\n\n**Step 4 — Coverage checkpoint.** Present a summary of everything established. Ask the user to confirm completeness before building the alignment page.\n\n## Alignment Page\n\nFollow the shared alignment-page convention via the packaged convention resolver; output path is `alignment\u002Fonboarding-map-{topic}.html`.\n\n## Constraints\n\n- Stay stage-specific; do not rewrite the whole journey map.\n- Make onboarding steps concrete enough to drive specs, UX variations, and instrumentation.\n- End with `## Next Steps`, preferring `\u002Fconversion-map`, `\u002Flifecycle-metrics`, `\u002Fux-variations` as context dictates.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n\n","## Pack Availability Guard\n\nBefore telling the user to run a skill from another project-local pack, check `.agents\u002Fproject.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install \u003Cpack>` from the project shell, instead of the target skill.\n\n# Onboarding Map\n\n\n\nCreate the stage-level onboarding plan that expands `research\u002Fjourney-map.md`.\n\n## Process\n\n### 0. Product-Path Scope Resolution\n\nResolve research scope by product path before using code or app structure as a hint:\n\n1. If `$ARGUMENTS` names a non-archived `research\u002F{slug}\u002F` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product\u002Fapp name, not the ICP, audience, or segment label.\n2. If `$ARGUMENTS` names only `research\u002F_archive\u002F{slug}\u002F` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.\n3. Read `research\u002F.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research\u002F_archive\u002F` from active target selection.\n4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.\n5. If no active manifest target exists, list non-archived product directories under `research\u002F`, excluding `research\u002F_archive\u002F` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.\n6. If no product directories exist, use flat `research\u002F` single-product mode.\n7. Detect monorepo\u002Fapp\u002Fpackage structure only as a secondary hint. Suggest creating a missing `research\u002F{slug}\u002F` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research\u002F{slug}\u002F`.\n\nWhen product path `{slug}` is active, read and write research under `research\u002F{slug}\u002F`, specs under `specs\u002F{slug}\u002F`, and treat top-level `research\u002F*.md` files as flat-mode documents or cross-path summaries.\n\n1. Resolve product-path scope using the same `research\u002F{slug}\u002F` convention as `\u002Fjourney-map`.\n2. Read `research\u002F.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading; treat legacy `abandoned` as `archived` and exclude archived\u002Fdeferred\u002Frevisit\u002Fpromoted paths plus `research\u002F_archive\u002F` scopes from active target selection. Scope the onboarding map to the active product path by default.\n3. Require `research\u002Fjourney-map.md` or `research\u002F{slug}\u002Fjourney-map.md`; if missing, recommend `\u002Fjourney-map`.\n4. Load ICP, journey map, specs, customer feedback, metrics, and current product routes\u002Fcomponents when present.\n5. Interview and recommend around: signup entry points, account creation, required setup, imports\u002Fintegrations, team invites, empty states, first-session guidance, first 5 minutes\u002Fhour\u002Fday, aha threshold, drop-offs, recovery, and support touchpoints.\n6. Present the proposed onboarding model before writing.\n7. Write `research\u002Fonboarding-map.md` and `research\u002Fonboarding-map-interview.md` in flat mode, or `research\u002F{slug}\u002Fonboarding-map.md` and `research\u002F{slug}\u002Fonboarding-map-interview.md` when product-path scope is active, after validation.\n\n## Output Shape\n\n```markdown\n# Onboarding Map\n\n> Based on: research\u002Fjourney-map.md\n> Date: YYYY-MM-DD\n\n## Summary\n## Personas And Entry Points\n## Signup And Setup Flow\n## Activation Path\n## First Success\n## Drop-Offs And Recovery\n## Instrumentation Needs\n## Product Gaps\n## Next Steps\n```\n\n## Interview Protocol\n\n**Step 1 — Gather context.** Read `.agents\u002Fproject.json`, README, CLAUDE.md, existing research and specs, git history, and any argument-provided context. Build an internal evidence base before asking questions.\n\n**Step 2 — Assumptions manifest.** Present 3–7 assumptions about the user's situation, goals, and constraints. Tag each with source (`[from prompt]`, `[from repo]`, `[from research]`, `[inferred]`). Ask the user to confirm, correct, or flag before proceeding.\n\n**Step 3 — Focused interview.** Ask 1–3 questions per turn via `AskUserQuestion`. Research and recommend by default — present options with a recommended default. Continue until all areas are covered or the user signals enough.\n\n**Step 4 — Coverage checkpoint.** Present a summary of everything established. Ask the user to confirm completeness before building the alignment page.\n\n## Alignment Page\n\nFollow the shared alignment-page convention via the packaged convention resolver; output path is `alignment\u002Fonboarding-map-{topic}.html`.\n\n## Constraints\n\n- Stay stage-specific; do not rewrite the whole journey map.\n- Make onboarding steps concrete enough to drive specs, UX variations, and instrumentation.\n- End with `## Next Steps`, preferring `\u002Fconversion-map`, `\u002Flifecycle-metrics`, `\u002Fux-variations` as context dictates.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n\n",{"name":5,"type":28,"version":48,"description":7,"visual_tier":38,"argument-hint":49,"context_intake":39,"required_conventions":50},"v0.5","[optional: app, persona, or onboarding segment]",[51],"alignment-page","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fcustomer-lifecycle\u002Fclaude\u002Fonboarding-map",0,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills","https:\u002F\u002Fagentic-skills-blush.vercel.app","https:\u002F\u002Fgithub.com\u002FGeorgeQLe","georgeqle.com","George Le is a futurist and serial tech entrepreneur who wants to work toward a world where humanity is free from robotic tasks.","2026-11-10 04:07:24",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill onboarding-map",{"tool":68,"command":69},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill onboarding-map",{"tool":71,"command":72},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill onboarding-map","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fcustomer-lifecycle\u002Fclaude\u002Fonboarding-map\u002FSKILL.md",true,[76,82],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"ALIGNMENT-PAGE.md","REFERENCE","参考文档",54070,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fcustomer-lifecycle\u002Fclaude\u002Fonboarding-map\u002FALIGNMENT-PAGE.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"CHANGELOG.md",1185,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fcustomer-lifecycle\u002Fclaude\u002Fonboarding-map\u002FCHANGELOG.md",[87,99,109,121,136,147],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":43},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[94,95,96,97,32,98],"source checkout allowed","checkout","fixture","only","valid",{"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":43},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[106,107,108,98,96,32],"deck install valid","deck","install",{"skillNo":110,"name":111,"nameZh":6,"description":112,"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":43},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[116,117,118,98,119,120,96,32],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":132,"publishedAt":43},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[133,134,98,119,32,135,96],"codex missing skill valid","missing","fallback",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":43},"01M6G0N7PC0EKFD40ZWQAXSAQ9","codex-base-skill-fallback-valid","Valid Codex base skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-base-skill-fallback\u002FSKILL.md",[142],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},[98,119,135,144,145,146,32,96],"base skill","codex base skill fallback valid","base",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":43},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[98,118,117,154,120,32,96],"claude pack guard valid"]