[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JFSJX0STFN34SRQ8XDPN4":3,"skill-same:01M71JFSJX0STFN34SRQ8XDPN4":73},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M71JFSJX0STFN34SRQ8XDPN4","find-way",null,"Plan a large effort as a shared map of decision tickets on an issue tracker, resolving them one at a time until the way is clear. Use when an idea is too big for one session, needs structured exploration before implementation, or requires mapping decisions before building.","danielvm-git\u002Fbigpowers","danielvm-git","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1020864?v=4","01M71H1N1CTQ529S0KN7KETVG6","Daniel V M","01M71H1N218Y3S8WHCJ58NPRSW",289,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ffind-way\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"find","find way","session","for","effort","as","idea","sonnet","mapping","issue","at","tracker","plan","one at a time","when","map","decision","time","exploration","shared","2026-11-10 10:12:30",false,"---\nname: find-way\nmodel: sonnet\ndescription: \"Plan a large effort as a shared map of decision tickets on an issue tracker, resolving them one at a time until the way is clear. Use when an idea is too big for one session, needs structured exploration before implementation, or requires mapping decisions before building.\"\n---\n\n# Find Way\n\n## Concept\n\nA large effort arrives — too big for one session, wrapped in fog. **Find-way** charts the way as a **shared map** on the repo's issue tracker, then works **decision tickets** — questions whose resolution is a decision, not build slices — one at a time until the route is clear.\n\n**Plan, don't do.** Each ticket resolves a decision. The map is done when the way is clear — nothing left to decide before someone executes.\n\n**Refer by name.** Every map and ticket is an issue with a title. Always use the name, never bare ids or numbers.\n\n## The Map\n\nA single issue labelled `wayfinder:map` — the canonical artifact. Child issues are its tickets.\n\n```markdown\n## Destination\n\u003Cwhat reaching the end looks like — one or two lines>\n\n## Notes\n\u003Cdomain, skills to consult, standing preferences>\n\n## Decisions so far\n- [closed ticket title](link) — one-line gist\n\n## Not yet specified\n\u003Cin-scope fog you can't ticket yet>\n\n## Out of scope\n\u003Cwork ruled beyond the destination>\n```\n\n## Ticket Types\n\n| Type | Label | Mode | Purpose |\n|------|-------|------|---------|\n| Research | `wayfinder:research` | AFK | Surface facts from docs\u002FAPIs |\n| Prototype | `wayfinder:prototype` | HITL | Cheap artifact to react to |\n| Grilling | `wayfinder:grilling` | HITL | One-question-at-a-time dialogue |\n| Task | `wayfinder:task` | Either | Manual work unblocking a decision |\n\n**HITL** = human in the loop. **AFK** = agent alone.\n\n## Two Modes\n\n### Chart the Map\n\nUser invokes with a loose idea.\n\n1. **Name the destination** — grill to pin down what this map finds its way to\n2. **Map the frontier** — breadth-first: surface open decisions and first steps. If no fog emerges, the effort fits one session — skip the map\n3. **Create the map** issue (label `wayfinder:map`)\n4. **Create tickets** as child issues, then wire blocking edges in a second pass\n5. **Fire research subagents** for each `research` ticket in parallel\n6. Stop — charting resolves nothing\n\n### Work Through the Map\n\nUser invokes with a map (URL\u002Fnumber). Ticket optional — without one, pick the next frontier ticket.\n\n1. Load the map (low-res view)\n2. **Choose & claim** — assign ticket before any work\n3. **Resolve** — zoom into related\u002Fclosed tickets as needed\n4. **Record** — post resolution comment, close issue, append to Decisions-so-far\n5. **Graduate fog** — create new tickets from newly-specifiable fog, clear from Not-yet-specified\n6. **Rule out of scope** if resolution reveals something past the destination\n\n**Never resolve more than one ticket per session** (except research).\n\n## Fog of War\n\nBeyond live tickets lies the **fog** — decisions you can tell are coming but can't pin down yet. The **Not yet specified** section holds this dim view.\n\n**Fog or ticket?** Test: can you state the question precisely now?\n\n- **Ticket** when the question is sharp (even if blocked)\n- **Not yet specified** when you can't phrase it sharply yet\n\n## Out of Scope\n\nWork beyond the destination. Ruling something out is a scoping act, not a route step. Never graduates — returns only if destination is redrawn.\n\nIf an existing ticket sits past the destination, close it and note in Out of scope.\n\n## Blocking & Frontier\n\n- **Blocking**: tracker's native dependency relationship\n- **Unblocked**: every blocker is closed\n- **Frontier**: open, unblocked, unclaimed children — the edge of the known\n\n## Detailed Reference\n\nSee [REFERENCE.md](..\u002F..\u002F..\u002Fskills\u002Ffind-way\u002FREFERENCE.md) for ticket anatomy, resolution protocol, and examples.\n\n---\n\n# Find-Way Reference\n\n## Ticket Anatomy\n\nEach ticket holds one question, sized to one 100K token agent session:\n\n```markdown\n## Question\n\n\u003Cthe decision or investigation this ticket resolves>\n```\n\n**Labels:** `wayfinder:research`, `wayfinder:prototype`, `wayfinder:grilling`, or `wayfinder:task`\n\n**Claim:** Assign to yourself before any work — claim blocks concurrent sessions.\n\n**Blocking:** Use tracker's native dependency relationship so the frontier renders visually.\n\n**Resolution:** Post answer as a comment, close the issue, append to map's Decisions-so-far.\n\n## Resolution Protocol\n\n1. **Load the map** — read low-res view, not every ticket body\n2. **Choose & claim** — assign ticket to yourself (or take first frontier ticket if not named)\n3. **Resolve** — zoom into related\u002Fclosed tickets as needed; invoke skills the Notes block names\n4. **Record** — post resolution comment with the answer, close the issue\n5. **Update map** — append to Decisions-so-far with one-line gist + link\n6. **Graduate fog** — create new tickets from newly-specifiable fog; clear from Not-yet-specified\n7. **Rule out of scope** if resolution reveals something past the destination\n\n## Ticket Types in Detail\n\n### Research (AFK)\nSurfacing facts from docs, APIs, or knowledge bases that a decision waits on.\n- Resolved by a `\u002Fresearch` subagent\n- Use when knowledge outside the working directory is required\n- **Label:** `wayfinder:research`\n\n### Prototype (HITL)\nRaise fidelity by building cheap, rough, concrete artifact to react to — outline, stub, UI\u002Flogic code.\n- Use the `\u002Fprototype` skill\n- Links the prototype as an asset\n- Use when \"how should it look\" or \"how should it behave\" is key\n- **Label:** `wayfinder:prototype`\n\n### Grilling (HITL)\nConversation via `\u002Fgrilling` and `\u002Fdomain-modeling` skills, one question at a time.\n- The default case for clarifying decisions\n- **Label:** `wayfinder:grilling`\n\n### Task (HITL or AFK)\nManual work unblocking a decision — signing up for service, provisioning access, moving data.\n- This is the **only** type that does rather than decides\n- Earns its place by unblocking a decision, not by delivering the destination\n- Agent drives AFK tasks alone; HITL tasks get precise checklist\n- **Label:** `wayfinder:task`\n\n## Fog-to-Ticket Graduation\n\nWhen resolving a ticket clears fog, graduate the newly-specifiable bits into fresh tickets:\n\n1. **Identify the fog** in Not-yet-specified that the resolution illuminates\n2. **Create new tickets** with crisp question statements\n3. **Wire blocking edges** if the new tickets depend on each other or existing ones\n4. **Clear from fog** — remove the graduated patch from Not-yet-specified so it lives only as its ticket\n\n## Out-of-Scope Close Protocol\n\nIf a ticket turns out to sit past the destination:\n\n1. **Close the ticket** — mark it resolved or won't-fix\n2. **Add one line to Out of scope** — gist + why it's out of scope, linking the closed ticket\n3. **Never append to Decisions so far** — scope boundaries aren't steps on the route\n\n## Map State Transitions\n\n| State | Meaning | Action |\n|-------|---------|--------|\n| **Open, unblocked, unclaimed** | Frontier — ready to take | Claim and resolve |\n| **Open, blocked** | Waiting on something | Wait for blockers to close |\n| **Open, claimed** | Concurrent session working | Skip for now |\n| **Closed** | Decided — lives in Decisions so far | Reference, don't re-open |\n\n## Concurrency\n\nUsers may run unblocked tickets in parallel, so expect the tracker to be edited concurrently. Always:\n\n- Refresh the map before picking a ticket\n- Claim immediately before starting work\n- Never assume state hasn't changed since last read\n","# Find Way\n\n## Concept\n\nA large effort arrives — too big for one session, wrapped in fog. **Find-way** charts the way as a **shared map** on the repo's issue tracker, then works **decision tickets** — questions whose resolution is a decision, not build slices — one at a time until the route is clear.\n\n**Plan, don't do.** Each ticket resolves a decision. The map is done when the way is clear — nothing left to decide before someone executes.\n\n**Refer by name.** Every map and ticket is an issue with a title. Always use the name, never bare ids or numbers.\n\n## The Map\n\nA single issue labelled `wayfinder:map` — the canonical artifact. Child issues are its tickets.\n\n```markdown\n## Destination\n\u003Cwhat reaching the end looks like — one or two lines>\n\n## Notes\n\u003Cdomain, skills to consult, standing preferences>\n\n## Decisions so far\n- [closed ticket title](link) — one-line gist\n\n## Not yet specified\n\u003Cin-scope fog you can't ticket yet>\n\n## Out of scope\n\u003Cwork ruled beyond the destination>\n```\n\n## Ticket Types\n\n| Type | Label | Mode | Purpose |\n|------|-------|------|---------|\n| Research | `wayfinder:research` | AFK | Surface facts from docs\u002FAPIs |\n| Prototype | `wayfinder:prototype` | HITL | Cheap artifact to react to |\n| Grilling | `wayfinder:grilling` | HITL | One-question-at-a-time dialogue |\n| Task | `wayfinder:task` | Either | Manual work unblocking a decision |\n\n**HITL** = human in the loop. **AFK** = agent alone.\n\n## Two Modes\n\n### Chart the Map\n\nUser invokes with a loose idea.\n\n1. **Name the destination** — grill to pin down what this map finds its way to\n2. **Map the frontier** — breadth-first: surface open decisions and first steps. If no fog emerges, the effort fits one session — skip the map\n3. **Create the map** issue (label `wayfinder:map`)\n4. **Create tickets** as child issues, then wire blocking edges in a second pass\n5. **Fire research subagents** for each `research` ticket in parallel\n6. Stop — charting resolves nothing\n\n### Work Through the Map\n\nUser invokes with a map (URL\u002Fnumber). Ticket optional — without one, pick the next frontier ticket.\n\n1. Load the map (low-res view)\n2. **Choose & claim** — assign ticket before any work\n3. **Resolve** — zoom into related\u002Fclosed tickets as needed\n4. **Record** — post resolution comment, close issue, append to Decisions-so-far\n5. **Graduate fog** — create new tickets from newly-specifiable fog, clear from Not-yet-specified\n6. **Rule out of scope** if resolution reveals something past the destination\n\n**Never resolve more than one ticket per session** (except research).\n\n## Fog of War\n\nBeyond live tickets lies the **fog** — decisions you can tell are coming but can't pin down yet. The **Not yet specified** section holds this dim view.\n\n**Fog or ticket?** Test: can you state the question precisely now?\n\n- **Ticket** when the question is sharp (even if blocked)\n- **Not yet specified** when you can't phrase it sharply yet\n\n## Out of Scope\n\nWork beyond the destination. Ruling something out is a scoping act, not a route step. Never graduates — returns only if destination is redrawn.\n\nIf an existing ticket sits past the destination, close it and note in Out of scope.\n\n## Blocking & Frontier\n\n- **Blocking**: tracker's native dependency relationship\n- **Unblocked**: every blocker is closed\n- **Frontier**: open, unblocked, unclaimed children — the edge of the known\n\n## Detailed Reference\n\nSee [REFERENCE.md](..\u002F..\u002F..\u002Fskills\u002Ffind-way\u002FREFERENCE.md) for ticket anatomy, resolution protocol, and examples.\n\n---\n\n# Find-Way Reference\n\n## Ticket Anatomy\n\nEach ticket holds one question, sized to one 100K token agent session:\n\n```markdown\n## Question\n\n\u003Cthe decision or investigation this ticket resolves>\n```\n\n**Labels:** `wayfinder:research`, `wayfinder:prototype`, `wayfinder:grilling`, or `wayfinder:task`\n\n**Claim:** Assign to yourself before any work — claim blocks concurrent sessions.\n\n**Blocking:** Use tracker's native dependency relationship so the frontier renders visually.\n\n**Resolution:** Post answer as a comment, close the issue, append to map's Decisions-so-far.\n\n## Resolution Protocol\n\n1. **Load the map** — read low-res view, not every ticket body\n2. **Choose & claim** — assign ticket to yourself (or take first frontier ticket if not named)\n3. **Resolve** — zoom into related\u002Fclosed tickets as needed; invoke skills the Notes block names\n4. **Record** — post resolution comment with the answer, close the issue\n5. **Update map** — append to Decisions-so-far with one-line gist + link\n6. **Graduate fog** — create new tickets from newly-specifiable fog; clear from Not-yet-specified\n7. **Rule out of scope** if resolution reveals something past the destination\n\n## Ticket Types in Detail\n\n### Research (AFK)\nSurfacing facts from docs, APIs, or knowledge bases that a decision waits on.\n- Resolved by a `\u002Fresearch` subagent\n- Use when knowledge outside the working directory is required\n- **Label:** `wayfinder:research`\n\n### Prototype (HITL)\nRaise fidelity by building cheap, rough, concrete artifact to react to — outline, stub, UI\u002Flogic code.\n- Use the `\u002Fprototype` skill\n- Links the prototype as an asset\n- Use when \"how should it look\" or \"how should it behave\" is key\n- **Label:** `wayfinder:prototype`\n\n### Grilling (HITL)\nConversation via `\u002Fgrilling` and `\u002Fdomain-modeling` skills, one question at a time.\n- The default case for clarifying decisions\n- **Label:** `wayfinder:grilling`\n\n### Task (HITL or AFK)\nManual work unblocking a decision — signing up for service, provisioning access, moving data.\n- This is the **only** type that does rather than decides\n- Earns its place by unblocking a decision, not by delivering the destination\n- Agent drives AFK tasks alone; HITL tasks get precise checklist\n- **Label:** `wayfinder:task`\n\n## Fog-to-Ticket Graduation\n\nWhen resolving a ticket clears fog, graduate the newly-specifiable bits into fresh tickets:\n\n1. **Identify the fog** in Not-yet-specified that the resolution illuminates\n2. **Create new tickets** with crisp question statements\n3. **Wire blocking edges** if the new tickets depend on each other or existing ones\n4. **Clear from fog** — remove the graduated patch from Not-yet-specified so it lives only as its ticket\n\n## Out-of-Scope Close Protocol\n\nIf a ticket turns out to sit past the destination:\n\n1. **Close the ticket** — mark it resolved or won't-fix\n2. **Add one line to Out of scope** — gist + why it's out of scope, linking the closed ticket\n3. **Never append to Decisions so far** — scope boundaries aren't steps on the route\n\n## Map State Transitions\n\n| State | Meaning | Action |\n|-------|---------|--------|\n| **Open, unblocked, unclaimed** | Frontier — ready to take | Claim and resolve |\n| **Open, blocked** | Waiting on something | Wait for blockers to close |\n| **Open, claimed** | Concurrent session working | Skip for now |\n| **Closed** | Decided — lives in Decisions so far | Reference, don't re-open |\n\n## Concurrency\n\nUsers may run unblocked tickets in parallel, so expect the tracker to be edited concurrently. Always:\n\n- Refresh the map before picking a ticket\n- Claim immediately before starting work\n- Never assume state hasn't changed since last read\n",{"name":5,"model":26,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".pi\u002Fskills\u002Ffind-way",24,"https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers","https:\u002F\u002Fdanielvm-git.github.io\u002Fbigpowers\u002F","https:\u002F\u002Fgithub.com\u002Fdanielvm-git","danielvm.net","2026-11-10 01:18:54",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add danielvm-git\u002Fbigpowers --skill find-way",{"tool":59,"command":60},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill find-way",{"tool":62,"command":63},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill find-way","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ffind-way\u002FSKILL.md",true,[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"REFERENCE.md","REFERENCE","参考文档",3685,"https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ffind-way\u002FREFERENCE.md",[74,94,101,129,150,171],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":39},"01M71KBG9F8X644MJB16H4V8M7","skill-verify-fail-open-fixture","Negative-path fixture for run-skill-verify.sh — must never PASS.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fskill-verify-fail-open\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[86,87,88,89,90,91,92,22,93],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","never",{"skillNo":95,"name":96,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":39},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[100,91],"negative path",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":110,"publishedAt":39},"01M71KBBGF7Y4EB4AMHBZ8CJFC","write-document","Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs\u002F directory.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-document\u002FSKILL.md",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000002","文档处理",[111,112,113,114,115,116,117,118,119,120,121,33,122,123,26,124,125,126,127,128],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","use","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":39},"01M71KB8TM089JJD5AY5KAFSDM","wire-observability","Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-observability\u002FSKILL.md",[],[136,137,138,120,139,121,140,24,141,142,26,143,29,144,145,146,147,33,148,149],"observability","wire observability","readiness","commands","development","logging","add","instrumentation","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":39},"01M71KB6CNRANP449DQA3NJZ96","wire-ci","CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-ci\u002FSKILL.md",[],[157,158,159,160,161,162,163,164,165,166,167,120,168,22,136,26,169,170],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":188,"publishedAt":39},"01M71KB2ZV98P03X88QR8MT9F1","visual-dashboard","Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers\u002Fdashboard\u002F. Reads specs\u002Fstate.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-dashboard\u002FSKILL.md",[177,180,185],{"categoryNo":178,"categoryName":179,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":181,"categoryName":182,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":186,"categoryName":187,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000033","数据分析师",[189,190,191,192,193,194,195,196,197,26,198,199,200,31,201,202,203,148,204,205],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","browser","api","architecture","project status","http api"]