[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D38EVRP5N20ZD29JFJHF83":3,"skill-same:01M6D38EVRP5N20ZD29JFJHF83":231},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6D38EVRP5N20ZD29JFJHF83","afps-status",null,"Summarize AFPS product-workflow progress from existing artifacts and recommend the next concrete skill command","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\u002Fbase\u002Fclaude\u002Fafps-status\u002Farchive\u002Fv0.5\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35],"status","afps status","summarize","workflow","artifacts","product","analysis","command","v0","next","focus","project","2026-11-10 10:12:30",false,"---\nname: afps-status\ndescription: Summarize AFPS product-workflow progress from existing artifacts and recommend the next concrete skill command\ntype: analysis\nversion: v0.5\nargument-hint: \"[optional project path, product path, or focus]\"\n---\n\n# AFPS Status\n\nInvoke as `\u002Fafps-status`.\n\nUse this skill when the user asks where a product project is in the AFPS workflow, what research\u002Fplanning\u002Fimplementation artifact is missing next, whether task docs match product evidence, or which AFPS command should run next.\n\nAFPS here means the product workflow from raw idea through concept scoping, customer discovery\u002Fresearch, lifecycle\u002Fgrowth planning, specs, roadmap\u002Fphase work, implementation, validation, and shipping. This is read-mostly reconciliation. It summarizes existing artifacts and recommends a route; it does not create a competing workflow state system.\n\n## Process\n\n1. Resolve target project:\n   - Default to the current working directory.\n   - If `$ARGUMENTS` names a path, inspect that project.\n   - If `$ARGUMENTS` names a product path, app, customer, audience, or focus, prioritize matching artifacts under `research\u002F`, `specs\u002F`, `tasks\u002F`, and `alignment\u002F`.\n   - Confirm whether the target is a git worktree when possible. Continue with filesystem evidence if git is unavailable.\n2. Read project orientation:\n   - `.agents\u002Fproject.json`\n   - `README.md`, `AGENTS.md`, `CLAUDE.md`\n   - package\u002Fworkspace manifests and obvious app entrypoints when needed to understand whether implementation exists.\n   - Use `scripts\u002Fpack.sh list-packs` when available to determine enabled packs; do not grep `.agents\u002Fproject.json` directly when choosing installed-pack routes.\n3. Inspect AFPS evidence from existing artifacts:\n   - Product-path state: `research\u002F.progress.yaml`, including legacy `active_path` normalized mentally to `active_paths`.\n   - Research-loop state: selected-set run manifests `research\u002F_working\u002F{orchestrator}-run.yaml` (or `research\u002F{slug}\u002F_working\u002F{orchestrator}-run.yaml`) for the self-advancing research orchestrators (`customer-discovery`, `competitive-analysis`, `positioning`, `journey-map`). When a manifest exists, read its `selected_frameworks` and compare against existing canonical intermediates `research\u002F{orchestrator}-{framework}.md` (or `research\u002F{slug}\u002F{orchestrator}-{framework}.md`) to derive how many frameworks are complete. A manifest with frameworks still pending — or all intermediates present but no synthesized canonical (`research\u002F{orchestrator}.md`) yet — means that loop is **mid-run**.\n   - Concept artifacts: `research\u002Fidea-brief*.md`, app-scoped `research\u002F*\u002Fidea-brief*.md`, and concept\u002Finterview notes.\n   - Discovery artifacts: customer-discovery docs such as `research\u002Ficp.md`, competitive analysis, customer feedback, journey\u002Flifecycle maps, value-prop canvas, positioning, lean canvas, market evidence, and assumption\u002Frisk trackers.\n   - Lifecycle\u002Fgrowth artifacts: onboarding, activation, retention, conversion, monetization, GTM, growth model, metrics, PMF, and experiment docs.\n   - Product\u002Fspec artifacts: `specs\u002F`, `spec.md`, app\u002Ffeature specs, UX\u002FUI\u002Fprototype\u002FUAT\u002Fconsolidation notes, and alignment pages under `alignment\u002F`.\n   - Execution artifacts: `tasks\u002Froadmap.md`, `tasks\u002Ftodo.md`, `tasks\u002Fmanual-todo.md`, `tasks\u002Frecord-todo.md`, `tasks\u002Frecurring-todo.md`, `tasks\u002Fhistory.md`, `tasks\u002Fphases\u002F`, and recent validation notes.\n   - Rapid pipeline artifacts: `research\u002Fvard-ship-log.md` (VARD experiments), `research\u002Ford-ship-log.md` (ORD packages), and `alignment\u002Fvard-*.md` or `alignment\u002Ford-*.md` alignment docs.\n   - Git evidence: `git status --short`, current branch\u002Fupstream, last relevant commits, unpushed commits, and changed files.\n4. Reconcile evidence instead of trusting one file:\n   - Distinguish missing artifacts, stale artifacts, contradictory artifacts, completed work, active implementation tasks, manual blockers, unvalidated implementation, and unshipped local changes.\n   - Treat `research\u002F.progress.yaml` as a manifest of product\u002Fapp\u002Fcustomer focus, not as the source of truth over concrete artifacts. Its `pipeline_stage` is a pointer to which orchestrator stage last ran, not per-framework status.\n   - For a self-advancing research orchestrator, derive framework progress from the run manifest + canonical-intermediate existence and report it as \"k of N frameworks complete,\" not from `tasks\u002Ftodo.md` checkboxes (the migrated orchestrators no longer queue framework work there).\n   - If product-path manifest entries are missing or stale, report the exact proposed update in prose. Do not write `research\u002F.progress.yaml` unless the user explicitly asks for mutation.\n   - If task docs contradict research\u002Fspec\u002Fcode\u002Fgit evidence, call out the contradiction and route to reconciliation rather than choosing whichever artifact is newest.\n5. Detect rapid pipeline activity:\n   - If `research\u002Fvard-ship-log.md` exists, report VARD pipeline status: number of experiments shipped, most recent entry, and whether any show traction signals warranting graduation to Business AFPS.\n   - If `research\u002Ford-ship-log.md` exists, report ORD pipeline status: number of packages published, most recent entry, and whether any show traction signals warranting graduation to Devtool AFPS.\n   - If `vard` or `ord` packs are enabled, note the active rapid pipeline alongside deliberate pipeline status.\n6. Classify AFPS stage:\n   - `unscoped`: no concept brief or the concept is too unclear for customer discovery.\n   - `concept-ready`: concept exists but discovery pack\u002Fskills are not enabled.\n   - `discovery-needed`: concept exists and discovery skills are enabled, but customer discovery is absent or not specific enough.\n   - `research-incomplete`: customer discovery exists but market, competitive, value, positioning, journey, or lifecycle evidence is missing.\n   - `lifecycle-gap`: discovery exists but onboarding, conversion, activation, retention, monetization, GTM, or metrics questions block spec quality.\n   - `spec-needed`: research is sufficient but durable product\u002Fspec artifacts are absent or stale.\n   - `roadmap-needed`: research\u002Fspec artifacts exist but `tasks\u002Froadmap.md` or `tasks\u002Ftodo.md` is missing, stale, contradictory, or not actionable.\n   - `execution-ready`: a clear unchecked implementation task exists with no blocking manual task.\n   - `ship-needed`: implementation changes are present, completed, or unpushed but validation, task review, commit, push, or deploy packaging is pending.\n   - `reconcile-needed`: artifacts conflict enough that the next step should be reconciliation before new research or implementation.\n6. Choose the next route with these rules:\n   - No concept brief or unclear concept: `\u002Fidea-scope-brief`\n   - Concept exists but business discovery is missing: `npx skillpacks install business-discovery` from the project shell.\n   - Concept exists and discovery is enabled, but no customer-discovery evidence: `\u002Fcustomer-discovery`\n   - A self-advancing research loop is mid-run (a run manifest exists with frameworks still pending, or all intermediates exist but no synthesized canonical yet): re-invoke that same orchestrator to advance one phase — `\u002Fcustomer-discovery`, `\u002Fcompetitive-analysis`, `\u002Fpositioning`, or `\u002Fjourney-map` — and tell the user to clear context and re-run it. This continuation takes precedence over starting a new orchestrator; do not imply a single pass and do not route framework work to `\u002Fexec`.\n   - Customer discovery exists but market\u002Fvalue evidence is missing: the most specific discovery command, usually `\u002Fcompetitive-analysis`, `\u002Fvalue-prop-canvas`, or `\u002Fpositioning`\n   - Journey\u002Flifecycle\u002Fgrowth questions are missing after discovery: recommend the relevant installed command, or install the required pack first, such as `npx skillpacks install customer-lifecycle` from the project shell, or `npx skillpacks install business-growth` from the project shell.\n   - Research\u002Fspecs exist but task queue is stale or absent: `\u002Froadmap`\n   - Clear executable task exists: `\u002Fexec`\n   - Implementation is done but unvalidated, dirty, uncommitted, unpushed, or otherwise unshipped: `\u002Fship`\n   - Contradictory research\u002Fspec\u002Ftask evidence: `\u002Freconcile-research` when business-ops is enabled, `\u002Fspec-drift` when agent-work-admin is enabled, otherwise `\u002Fcodebase-status` with a focused prompt naming the contradiction.\n7. Validate command availability before recommending pack-local routes:\n   - Use `scripts\u002Fpack.sh list-packs` when present to detect enabled packs.\n   - If the best command lives in an uninstalled pack, recommend the package install command instead of the unavailable command: `npx skillpacks install \u003Cpack>` from the project shell.\n   - If `scripts\u002Fpack.sh` is missing or pack lookup fails, silently fall back to the global\u002Fdefault route and mention the degraded lookup only if it changes confidence.\n\n## Output\n\nProduce a concise structured report with:\n\n- **Overview:** repo path, product\u002Fapp focus, git status, enabled packs, active rapid pipelines (VARD\u002FORD), and whether AFPS evidence is single-path or multi-path.\n- **Rapid Pipeline Status** (if applicable): VARD and\u002For ORD experiment counts, latest shipment, traction signals, and graduation readiness.\n- **Artifact Map:** concept, customer discovery\u002Fresearch, lifecycle\u002Fgrowth, specs\u002Fprototypes\u002FUAT, tasks, alignment pages, and shipping evidence with present\u002Fmissing\u002Fstale status. For a research stage whose run manifest exists, report loop progress as \"k of N frameworks complete\" and whether it is mid-run.\n- **AFPS Stage:** one stage label from the workflow above, with confidence and evidence.\n- **Contradictions And Gaps:** conflicting artifacts, missing product-path manifest updates, stale task queues, manual blockers, validation\u002Fshipping gaps, and uncertainty.\n- **Recommended Route:** the next concrete work item and why it is the narrowest route.\n\nEnd with exactly:\n\n```md\n**Next work:** \u003Cspecific AFPS step or blocker>\n**Recommended next command:** \u003Cone command or route>\n```\n\n## Constraints\n\n- Read-only by default. Do not modify workflow state, task docs, research docs, specs, or git state unless the user explicitly asks for mutation.\n- Do not create a new AFPS state file or schema. Use existing artifacts, especially `research\u002F.progress.yaml`, `research\u002F`, `specs\u002F`, `tasks\u002F`, `alignment\u002F`, and git.\n- Propose missing `research\u002F.progress.yaml` updates in the report instead of writing them by default.\n- Do not run expensive tests, installs, web research, deploys, or external-account actions during status synthesis.\n- Do not treat `tasks\u002Frecord-todo.md` or `tasks\u002Frecurring-todo.md` as execution queues unless an item has clearly been promoted into `tasks\u002Ftodo.md`.\n- Do not route agent-executable repo work to `\u002Fguide`; reserve guided\u002Fmanual routes for human-only blockers.\n- Do not create or modify GitHub Actions workflows.\n\n## Alignment Page\n\nBy default, this skill reports results inline and writes only its normal durable artifacts (for example `tasks\u002F*.md`, reports, queues, benchmark notes, status docs, or other skill-specific files). Do not build an alignment page automatically. Create `alignment\u002Fafps-status-{topic}.html` only when the user explicitly requests an alignment page or when you explicitly identify a concrete clarification\u002Freview need that cannot be handled cleanly inline; when you create one, follow `ALIGNMENT-PAGE.md` in this skill's directory.\n\n## Default Shipping Contract\n\n- **Default next-step routing:** when reporting completion, include the two-line pair `**Next work:** \u003Cspecific task or \"none\">` and `**Recommended next command:** \u003Cone command or route>` so the next caller has a concrete handoff.\n- Normally read-only and should not create or modify tracked repository files.\n- If the user explicitly asks this skill to create or modify tracked files, finish by committing and pushing all intended changes to the repository primary branch (`main` when present, otherwise `master`) before stopping.\n- This contract does not override stricter safety rules about secrets, destructive history changes, release publication\u002Ftag confirmation, production deploy confirmation, paid actions, or public visibility changes.\n","# AFPS Status\n\nInvoke as `\u002Fafps-status`.\n\nUse this skill when the user asks where a product project is in the AFPS workflow, what research\u002Fplanning\u002Fimplementation artifact is missing next, whether task docs match product evidence, or which AFPS command should run next.\n\nAFPS here means the product workflow from raw idea through concept scoping, customer discovery\u002Fresearch, lifecycle\u002Fgrowth planning, specs, roadmap\u002Fphase work, implementation, validation, and shipping. This is read-mostly reconciliation. It summarizes existing artifacts and recommends a route; it does not create a competing workflow state system.\n\n## Process\n\n1. Resolve target project:\n   - Default to the current working directory.\n   - If `$ARGUMENTS` names a path, inspect that project.\n   - If `$ARGUMENTS` names a product path, app, customer, audience, or focus, prioritize matching artifacts under `research\u002F`, `specs\u002F`, `tasks\u002F`, and `alignment\u002F`.\n   - Confirm whether the target is a git worktree when possible. Continue with filesystem evidence if git is unavailable.\n2. Read project orientation:\n   - `.agents\u002Fproject.json`\n   - `README.md`, `AGENTS.md`, `CLAUDE.md`\n   - package\u002Fworkspace manifests and obvious app entrypoints when needed to understand whether implementation exists.\n   - Use `scripts\u002Fpack.sh list-packs` when available to determine enabled packs; do not grep `.agents\u002Fproject.json` directly when choosing installed-pack routes.\n3. Inspect AFPS evidence from existing artifacts:\n   - Product-path state: `research\u002F.progress.yaml`, including legacy `active_path` normalized mentally to `active_paths`.\n   - Research-loop state: selected-set run manifests `research\u002F_working\u002F{orchestrator}-run.yaml` (or `research\u002F{slug}\u002F_working\u002F{orchestrator}-run.yaml`) for the self-advancing research orchestrators (`customer-discovery`, `competitive-analysis`, `positioning`, `journey-map`). When a manifest exists, read its `selected_frameworks` and compare against existing canonical intermediates `research\u002F{orchestrator}-{framework}.md` (or `research\u002F{slug}\u002F{orchestrator}-{framework}.md`) to derive how many frameworks are complete. A manifest with frameworks still pending — or all intermediates present but no synthesized canonical (`research\u002F{orchestrator}.md`) yet — means that loop is **mid-run**.\n   - Concept artifacts: `research\u002Fidea-brief*.md`, app-scoped `research\u002F*\u002Fidea-brief*.md`, and concept\u002Finterview notes.\n   - Discovery artifacts: customer-discovery docs such as `research\u002Ficp.md`, competitive analysis, customer feedback, journey\u002Flifecycle maps, value-prop canvas, positioning, lean canvas, market evidence, and assumption\u002Frisk trackers.\n   - Lifecycle\u002Fgrowth artifacts: onboarding, activation, retention, conversion, monetization, GTM, growth model, metrics, PMF, and experiment docs.\n   - Product\u002Fspec artifacts: `specs\u002F`, `spec.md`, app\u002Ffeature specs, UX\u002FUI\u002Fprototype\u002FUAT\u002Fconsolidation notes, and alignment pages under `alignment\u002F`.\n   - Execution artifacts: `tasks\u002Froadmap.md`, `tasks\u002Ftodo.md`, `tasks\u002Fmanual-todo.md`, `tasks\u002Frecord-todo.md`, `tasks\u002Frecurring-todo.md`, `tasks\u002Fhistory.md`, `tasks\u002Fphases\u002F`, and recent validation notes.\n   - Rapid pipeline artifacts: `research\u002Fvard-ship-log.md` (VARD experiments), `research\u002Ford-ship-log.md` (ORD packages), and `alignment\u002Fvard-*.md` or `alignment\u002Ford-*.md` alignment docs.\n   - Git evidence: `git status --short`, current branch\u002Fupstream, last relevant commits, unpushed commits, and changed files.\n4. Reconcile evidence instead of trusting one file:\n   - Distinguish missing artifacts, stale artifacts, contradictory artifacts, completed work, active implementation tasks, manual blockers, unvalidated implementation, and unshipped local changes.\n   - Treat `research\u002F.progress.yaml` as a manifest of product\u002Fapp\u002Fcustomer focus, not as the source of truth over concrete artifacts. Its `pipeline_stage` is a pointer to which orchestrator stage last ran, not per-framework status.\n   - For a self-advancing research orchestrator, derive framework progress from the run manifest + canonical-intermediate existence and report it as \"k of N frameworks complete,\" not from `tasks\u002Ftodo.md` checkboxes (the migrated orchestrators no longer queue framework work there).\n   - If product-path manifest entries are missing or stale, report the exact proposed update in prose. Do not write `research\u002F.progress.yaml` unless the user explicitly asks for mutation.\n   - If task docs contradict research\u002Fspec\u002Fcode\u002Fgit evidence, call out the contradiction and route to reconciliation rather than choosing whichever artifact is newest.\n5. Detect rapid pipeline activity:\n   - If `research\u002Fvard-ship-log.md` exists, report VARD pipeline status: number of experiments shipped, most recent entry, and whether any show traction signals warranting graduation to Business AFPS.\n   - If `research\u002Ford-ship-log.md` exists, report ORD pipeline status: number of packages published, most recent entry, and whether any show traction signals warranting graduation to Devtool AFPS.\n   - If `vard` or `ord` packs are enabled, note the active rapid pipeline alongside deliberate pipeline status.\n6. Classify AFPS stage:\n   - `unscoped`: no concept brief or the concept is too unclear for customer discovery.\n   - `concept-ready`: concept exists but discovery pack\u002Fskills are not enabled.\n   - `discovery-needed`: concept exists and discovery skills are enabled, but customer discovery is absent or not specific enough.\n   - `research-incomplete`: customer discovery exists but market, competitive, value, positioning, journey, or lifecycle evidence is missing.\n   - `lifecycle-gap`: discovery exists but onboarding, conversion, activation, retention, monetization, GTM, or metrics questions block spec quality.\n   - `spec-needed`: research is sufficient but durable product\u002Fspec artifacts are absent or stale.\n   - `roadmap-needed`: research\u002Fspec artifacts exist but `tasks\u002Froadmap.md` or `tasks\u002Ftodo.md` is missing, stale, contradictory, or not actionable.\n   - `execution-ready`: a clear unchecked implementation task exists with no blocking manual task.\n   - `ship-needed`: implementation changes are present, completed, or unpushed but validation, task review, commit, push, or deploy packaging is pending.\n   - `reconcile-needed`: artifacts conflict enough that the next step should be reconciliation before new research or implementation.\n6. Choose the next route with these rules:\n   - No concept brief or unclear concept: `\u002Fidea-scope-brief`\n   - Concept exists but business discovery is missing: `npx skillpacks install business-discovery` from the project shell.\n   - Concept exists and discovery is enabled, but no customer-discovery evidence: `\u002Fcustomer-discovery`\n   - A self-advancing research loop is mid-run (a run manifest exists with frameworks still pending, or all intermediates exist but no synthesized canonical yet): re-invoke that same orchestrator to advance one phase — `\u002Fcustomer-discovery`, `\u002Fcompetitive-analysis`, `\u002Fpositioning`, or `\u002Fjourney-map` — and tell the user to clear context and re-run it. This continuation takes precedence over starting a new orchestrator; do not imply a single pass and do not route framework work to `\u002Fexec`.\n   - Customer discovery exists but market\u002Fvalue evidence is missing: the most specific discovery command, usually `\u002Fcompetitive-analysis`, `\u002Fvalue-prop-canvas`, or `\u002Fpositioning`\n   - Journey\u002Flifecycle\u002Fgrowth questions are missing after discovery: recommend the relevant installed command, or install the required pack first, such as `npx skillpacks install customer-lifecycle` from the project shell, or `npx skillpacks install business-growth` from the project shell.\n   - Research\u002Fspecs exist but task queue is stale or absent: `\u002Froadmap`\n   - Clear executable task exists: `\u002Fexec`\n   - Implementation is done but unvalidated, dirty, uncommitted, unpushed, or otherwise unshipped: `\u002Fship`\n   - Contradictory research\u002Fspec\u002Ftask evidence: `\u002Freconcile-research` when business-ops is enabled, `\u002Fspec-drift` when agent-work-admin is enabled, otherwise `\u002Fcodebase-status` with a focused prompt naming the contradiction.\n7. Validate command availability before recommending pack-local routes:\n   - Use `scripts\u002Fpack.sh list-packs` when present to detect enabled packs.\n   - If the best command lives in an uninstalled pack, recommend the package install command instead of the unavailable command: `npx skillpacks install \u003Cpack>` from the project shell.\n   - If `scripts\u002Fpack.sh` is missing or pack lookup fails, silently fall back to the global\u002Fdefault route and mention the degraded lookup only if it changes confidence.\n\n## Output\n\nProduce a concise structured report with:\n\n- **Overview:** repo path, product\u002Fapp focus, git status, enabled packs, active rapid pipelines (VARD\u002FORD), and whether AFPS evidence is single-path or multi-path.\n- **Rapid Pipeline Status** (if applicable): VARD and\u002For ORD experiment counts, latest shipment, traction signals, and graduation readiness.\n- **Artifact Map:** concept, customer discovery\u002Fresearch, lifecycle\u002Fgrowth, specs\u002Fprototypes\u002FUAT, tasks, alignment pages, and shipping evidence with present\u002Fmissing\u002Fstale status. For a research stage whose run manifest exists, report loop progress as \"k of N frameworks complete\" and whether it is mid-run.\n- **AFPS Stage:** one stage label from the workflow above, with confidence and evidence.\n- **Contradictions And Gaps:** conflicting artifacts, missing product-path manifest updates, stale task queues, manual blockers, validation\u002Fshipping gaps, and uncertainty.\n- **Recommended Route:** the next concrete work item and why it is the narrowest route.\n\nEnd with exactly:\n\n```md\n**Next work:** \u003Cspecific AFPS step or blocker>\n**Recommended next command:** \u003Cone command or route>\n```\n\n## Constraints\n\n- Read-only by default. Do not modify workflow state, task docs, research docs, specs, or git state unless the user explicitly asks for mutation.\n- Do not create a new AFPS state file or schema. Use existing artifacts, especially `research\u002F.progress.yaml`, `research\u002F`, `specs\u002F`, `tasks\u002F`, `alignment\u002F`, and git.\n- Propose missing `research\u002F.progress.yaml` updates in the report instead of writing them by default.\n- Do not run expensive tests, installs, web research, deploys, or external-account actions during status synthesis.\n- Do not treat `tasks\u002Frecord-todo.md` or `tasks\u002Frecurring-todo.md` as execution queues unless an item has clearly been promoted into `tasks\u002Ftodo.md`.\n- Do not route agent-executable repo work to `\u002Fguide`; reserve guided\u002Fmanual routes for human-only blockers.\n- Do not create or modify GitHub Actions workflows.\n\n## Alignment Page\n\nBy default, this skill reports results inline and writes only its normal durable artifacts (for example `tasks\u002F*.md`, reports, queues, benchmark notes, status docs, or other skill-specific files). Do not build an alignment page automatically. Create `alignment\u002Fafps-status-{topic}.html` only when the user explicitly requests an alignment page or when you explicitly identify a concrete clarification\u002Freview need that cannot be handled cleanly inline; when you create one, follow `ALIGNMENT-PAGE.md` in this skill's directory.\n\n## Default Shipping Contract\n\n- **Default next-step routing:** when reporting completion, include the two-line pair `**Next work:** \u003Cspecific task or \"none\">` and `**Recommended next command:** \u003Cone command or route>` so the next caller has a concrete handoff.\n- Normally read-only and should not create or modify tracked repository files.\n- If the user explicitly asks this skill to create or modify tracked files, finish by committing and pushing all intended changes to the repository primary branch (`main` when present, otherwise `master`) before stopping.\n- This contract does not override stricter safety rules about secrets, destructive history changes, release publication\u002Ftag confirmation, production deploy confirmation, paid actions, or public visibility changes.\n",{"name":5,"type":30,"version":41,"description":7,"argument-hint":42},"v0.5","[optional project path, product path, or focus]","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fbase\u002Fclaude\u002Fafps-status\u002Farchive\u002Fv0.5",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill afps-status",{"tool":59,"command":60},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill afps-status",{"tool":62,"command":63},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill afps-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbase\u002Fclaude\u002Fafps-status\u002Farchive\u002Fv0.5\u002FSKILL.md",true,[67,73,77,81,85,89,93,97,101,105,109,113,117,123,127,131,135,139,143,147,151,155,159,163,167,171,175,179,183,187,191,195,199,203,207,211,215,219,223,227],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fretail-prices-api.md","REFERENCE","参考文档",6439,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Freferences\u002Fretail-prices-api.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fvm-families.md",5942,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Freferences\u002Fvm-families.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fvm-quotas.md",4191,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Freferences\u002Fvm-quotas.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fvmss-guide.md",6348,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Freferences\u002Fvmss-guide.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"workflows\u002Fcapacity-reservation\u002Fcapacity-reservation.md",7971,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fcapacity-reservation\u002Fcapacity-reservation.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"workflows\u002Fcapacity-reservation\u002Freferences\u002Fassociation-disassociation.md",3908,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fcapacity-reservation\u002Freferences\u002Fassociation-disassociation.md",{"path":94,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":95,"sourceHtmlUrl":96},"workflows\u002Fcapacity-reservation\u002Freferences\u002Fcapacity-reservation-overview.md",6108,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fcapacity-reservation\u002Freferences\u002Fcapacity-reservation-overview.md",{"path":98,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":99,"sourceHtmlUrl":100},"workflows\u002Fessential-machine-management\u002Fessential-machine-management.md",5101,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fessential-machine-management\u002Fessential-machine-management.md",{"path":102,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":103,"sourceHtmlUrl":104},"workflows\u002Fessential-machine-management\u002Freferences\u002Femm-enable-flow-portal-guidance.md",3140,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fessential-machine-management\u002Freferences\u002Femm-enable-flow-portal-guidance.md",{"path":106,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":107,"sourceHtmlUrl":108},"workflows\u002Fessential-machine-management\u002Freferences\u002Femm-enable-flow.md",9429,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fessential-machine-management\u002Freferences\u002Femm-enable-flow.md",{"path":110,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":111,"sourceHtmlUrl":112},"workflows\u002Fessential-machine-management\u002Freferences\u002Femm-overview.md",2442,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fessential-machine-management\u002Freferences\u002Femm-overview.md",{"path":114,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":115,"sourceHtmlUrl":116},"workflows\u002Fessential-machine-management\u002Freferences\u002Femm-prerequisites.md",3544,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fessential-machine-management\u002Freferences\u002Femm-prerequisites.md",{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"workflows\u002Fvm-creator\u002Fexamples\u002Fbicep\u002Fmain.bicep","OTHER","其他",3858,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Fexamples\u002Fbicep\u002Fmain.bicep",{"path":124,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":125,"sourceHtmlUrl":126},"workflows\u002Fvm-creator\u002Fexamples\u002Fbicep\u002FREADME.md",1681,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Fexamples\u002Fbicep\u002FREADME.md",{"path":128,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":129,"sourceHtmlUrl":130},"workflows\u002Fvm-creator\u002Fexamples\u002Fterraform\u002Fmain.tf",3324,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Fexamples\u002Fterraform\u002Fmain.tf",{"path":132,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":133,"sourceHtmlUrl":134},"workflows\u002Fvm-creator\u002Fexamples\u002Fterraform\u002Foutputs.tf",135,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Fexamples\u002Fterraform\u002Foutputs.tf",{"path":136,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":137,"sourceHtmlUrl":138},"workflows\u002Fvm-creator\u002Fexamples\u002Fterraform\u002FREADME.md",2562,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Fexamples\u002Fterraform\u002FREADME.md",{"path":140,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":141,"sourceHtmlUrl":142},"workflows\u002Fvm-creator\u002Fexamples\u002Fterraform\u002Fvariables.tf",1010,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Fexamples\u002Fterraform\u002Fvariables.tf",{"path":144,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":145,"sourceHtmlUrl":146},"workflows\u002Fvm-creator\u002Freferences\u002Fdelivery-options\u002Fgithub-pr.md",3289,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdelivery-options\u002Fgithub-pr.md",{"path":148,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":149,"sourceHtmlUrl":150},"workflows\u002Fvm-creator\u002Freferences\u002Fdelivery-options\u002Findex.md",2326,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdelivery-options\u002Findex.md",{"path":152,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":153,"sourceHtmlUrl":154},"workflows\u002Fvm-creator\u002Freferences\u002Fdelivery-options\u002Fprint.md",474,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdelivery-options\u002Fprint.md",{"path":156,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":157,"sourceHtmlUrl":158},"workflows\u002Fvm-creator\u002Freferences\u002Fdelivery-options\u002Fsave-local.md",2045,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdelivery-options\u002Fsave-local.md",{"path":160,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":161,"sourceHtmlUrl":162},"workflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fbeginner.md",1214,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fbeginner.md",{"path":164,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":165,"sourceHtmlUrl":166},"workflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fcost-deep.md",1150,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fcost-deep.md",{"path":168,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":169,"sourceHtmlUrl":170},"workflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Findex.md",3043,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Findex.md",{"path":172,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":173,"sourceHtmlUrl":174},"workflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fnetworking-deep.md",1623,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fnetworking-deep.md",{"path":176,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":177,"sourceHtmlUrl":178},"workflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fsecurity-deep.md",1270,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fsecurity-deep.md",{"path":180,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":181,"sourceHtmlUrl":182},"workflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fspec-deep.md",1377,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fdepth-probe\u002Fspec-deep.md",{"path":184,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":185,"sourceHtmlUrl":186},"workflows\u002Fvm-creator\u002Freferences\u002Fmcp-tools.md",2329,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fmcp-tools.md",{"path":188,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":189,"sourceHtmlUrl":190},"workflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Faz-cli.md",1948,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Faz-cli.md",{"path":192,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":193,"sourceHtmlUrl":194},"workflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Fbicep.md",1760,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Fbicep.md",{"path":196,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":197,"sourceHtmlUrl":198},"workflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Findex.md",3053,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Findex.md",{"path":200,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":201,"sourceHtmlUrl":202},"workflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Fmcp-apply.md",2649,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Fmcp-apply.md",{"path":204,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":205,"sourceHtmlUrl":206},"workflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Fterraform.md",1555,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Foutput-adapters\u002Fterraform.md",{"path":208,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":209,"sourceHtmlUrl":210},"workflows\u002Fvm-creator\u002Freferences\u002Fplan-card.md",4015,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fplan-card.md",{"path":212,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":213,"sourceHtmlUrl":214},"workflows\u002Fvm-creator\u002Freferences\u002Fvalidation-gates.md",2225,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Freferences\u002Fvalidation-gates.md",{"path":216,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":217,"sourceHtmlUrl":218},"workflows\u002Fvm-creator\u002Fvm-creator.md",7681,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-creator\u002Fvm-creator.md",{"path":220,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":221,"sourceHtmlUrl":222},"workflows\u002Fvm-recommender\u002Freferences\u002Fhandoff-to-creator.md",1684,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-recommender\u002Freferences\u002Fhandoff-to-creator.md",{"path":224,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":225,"sourceHtmlUrl":226},"workflows\u002Fvm-recommender\u002Freferences\u002Fweb-fetch-policy.md",1661,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-recommender\u002Freferences\u002Fweb-fetch-policy.md",{"path":228,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":229,"sourceHtmlUrl":230},"workflows\u002Fvm-recommender\u002Fvm-recommender.md",6586,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fskills\u002Fblob\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fazure-compute\u002Fworkflows\u002Fvm-recommender\u002Fvm-recommender.md",[232,244,254,266,281,292],{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":238,"publishedAt":36},"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",[],[239,240,241,242,32,243],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":245,"name":246,"nameZh":6,"description":247,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":248,"categories":249,"keywords":250,"publishedAt":36},"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",[],[251,252,253,243,241,32],"deck install valid","deck","install",{"skillNo":255,"name":256,"nameZh":6,"description":257,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":258,"categories":259,"keywords":260,"publishedAt":36},"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",[],[261,262,263,243,264,265,241,32],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":267,"name":268,"nameZh":6,"description":269,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":270,"categories":271,"keywords":277,"publishedAt":36},"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",[272],{"categoryNo":273,"categoryName":274,"taxonomyType":275,"taxonomyTypeDesc":276},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[278,279,243,264,32,280,241],"codex missing skill valid","missing","fallback",{"skillNo":282,"name":283,"nameZh":6,"description":284,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":285,"categories":286,"keywords":288,"publishedAt":36},"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",[287],{"categoryNo":273,"categoryName":274,"taxonomyType":275,"taxonomyTypeDesc":276},[243,264,280,289,290,291,32,241],"base skill","codex base skill fallback valid","base",{"skillNo":293,"name":294,"nameZh":6,"description":295,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":296,"categories":297,"keywords":298,"publishedAt":36},"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",[],[243,263,262,299,265,32,241],"claude pack guard valid"]