[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVT42EHPWFT5ET8S2QGEA7":3,"skill-same:01M6JVT42EHPWFT5ET8S2QGEA7":72},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6JVT42EHPWFT5ET8S2QGEA7","visual-source-artifact",null,"Shape product, business, data, research, UX, and mockup artifacts as agent-readable sources with generated visual human review surfaces.","45ck\u002Fskill-harness","45ck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F98618920?v=4","01M6JVMEERB77XKFGN2RT770BP","Calvin","01M6JVMEK42E6WBBD4R3QE9Y4P",15,"MIT","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fpacks\u002Fdeveloper-artifact-skills\u002Fskills\u002Fvisual-source-artifact\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"visual source artifact","source","visual","artifact","surfaces","mockup","with","sources","as","human","review","shape","human review","business","generated","data","ux","product","artifacts","research","2026-11-10 10:12:30",false,"---\nname: visual-source-artifact\ndescription: Shape product, business, data, research, UX, and mockup artifacts as agent-readable sources with generated visual human review surfaces.\n---\n\n# Visual Source Artifact\n\nUse this skill when a human needs to inspect product, business, data, research, UX, or mockup work visually while agents need durable source they can diff, update, and verify.\n\n## Core Rule\n\nUse a source-first pair:\n\n- Canonical source: Markdown, TOON, JSON, YAML, specgraph-compatible docs, model text, or structured data.\n- Generated review surface: static HTML, dashboard, state board, prototype, journey map, schema map, evidence board, or comparison page under `generated\u002Freview\u002F`.\n- For human-facing discovery and planning, the generated review surface should be infographic-style HTML under `generated\u002Freview\u002F\u003Cfamily>\u002F`.\n\nGenerated visual files are never the only durable source. Edit source first, then regenerate or discard the review surface.\n\n## Default Fidelity\n\n- High-fidelity is the default for UI, product, customer-facing workflow, and mockup review.\n- Low-fidelity sketches are scratch artifacts only unless the project explicitly records them as research evidence.\n- Use realistic states, dense data, error paths, accessibility cues, assumptions, and evidence strength in the review surface.\n- Use scan-friendly metrics, charts, timelines, evidence\u002Ffreshness panels, and source links for non-UI human review artifacts.\n- Use Mermaid for authored diagrams, Vega-Lite as the default chart grammar, Observable Plot for compact exploratory charts, D3 for bespoke static layouts, Graphviz for node-edge maps, ECharts only as generation-time\u002Fstatic output, RAWGraphs for exported design-led SVGs, and Chart.js only through server-rendered\u002Fstatic output or an equivalent static chart.\n- Put chart and graph intent in `artifact-infographic` JSON fences or manifest `infographics` arrays when the project has the generic renderer.\n\n## Artifact Families\n\n- Product: PRD, opportunity brief, feature map, roadmap, acceptance matrix.\n- Business: business model, pricing assumptions, stakeholder map, operating risk, go-to-market assumptions.\n- Data: schema, data dictionary, metric definition, lineage, quality rule, sample records.\n- Research: claim-evidence matrix, literature theme map, interview synthesis, assumption register.\n- UX: design brief, component state spec, interaction flow, high-fidelity prototype source, journey map.\n\n## Agent Team\n\n- `requirements-analyst` owns product intent, requirements, and acceptance criteria.\n- `delivery-manager` owns business viability, stakeholder impact, rollout, and risk.\n- `backend-engineer` owns data shape, schemas, integrity, and metrics implementation constraints.\n- `research-writer` owns citations, claim strength, research synthesis, and gaps.\n- `ux-researcher` owns task evidence, prototype critique, high-fidelity UX review, and accessibility concerns.\n- `system-modeler` owns UML\u002FUWE\u002FC4\u002Fworkflow impact when structure or behavior changes.\n- `quality-reviewer` owns freshness, manifest completeness, evidence sufficiency, and readiness risks.\n\n## Process\n\n1. Name the decision the visual artifact supports.\n2. Select the artifact family and owner agent.\n3. Define the canonical source path under `docs\u002Fartifacts\u002Fsource\u002F\u003Cfamily>\u002F` unless a domain docs path is better.\n4. Define the generated review path under `generated\u002Freview\u002F\u003Cfamily>\u002F`.\n5. List evidence links and label real evidence separately from synthetic user or agent-simulation evidence.\n6. Add or update the manifest entry with source, review surface, owner, evidence, status, freshness, and `reviewRequired: true` when a generated HTML surface is expected.\n7. Add `artifact-infographic` specs for charts, graphs, timelines, or source-backed infographic panels when useful.\n8. Run `node scripts\u002Fgenerate-artifact-review.mjs` when available.\n9. Run manifest and HTML policy checks before handoff when the project has them.\n\n## Output\n\n### Artifact Family\n### Decision Supported\n### Canonical Source\n### Generated Review Surface\n### Owner Agent\n### Evidence Links\n### Fidelity Requirement\n### Manifest Fields\n### Readiness Gates\n\n","# Visual Source Artifact\n\nUse this skill when a human needs to inspect product, business, data, research, UX, or mockup work visually while agents need durable source they can diff, update, and verify.\n\n## Core Rule\n\nUse a source-first pair:\n\n- Canonical source: Markdown, TOON, JSON, YAML, specgraph-compatible docs, model text, or structured data.\n- Generated review surface: static HTML, dashboard, state board, prototype, journey map, schema map, evidence board, or comparison page under `generated\u002Freview\u002F`.\n- For human-facing discovery and planning, the generated review surface should be infographic-style HTML under `generated\u002Freview\u002F\u003Cfamily>\u002F`.\n\nGenerated visual files are never the only durable source. Edit source first, then regenerate or discard the review surface.\n\n## Default Fidelity\n\n- High-fidelity is the default for UI, product, customer-facing workflow, and mockup review.\n- Low-fidelity sketches are scratch artifacts only unless the project explicitly records them as research evidence.\n- Use realistic states, dense data, error paths, accessibility cues, assumptions, and evidence strength in the review surface.\n- Use scan-friendly metrics, charts, timelines, evidence\u002Ffreshness panels, and source links for non-UI human review artifacts.\n- Use Mermaid for authored diagrams, Vega-Lite as the default chart grammar, Observable Plot for compact exploratory charts, D3 for bespoke static layouts, Graphviz for node-edge maps, ECharts only as generation-time\u002Fstatic output, RAWGraphs for exported design-led SVGs, and Chart.js only through server-rendered\u002Fstatic output or an equivalent static chart.\n- Put chart and graph intent in `artifact-infographic` JSON fences or manifest `infographics` arrays when the project has the generic renderer.\n\n## Artifact Families\n\n- Product: PRD, opportunity brief, feature map, roadmap, acceptance matrix.\n- Business: business model, pricing assumptions, stakeholder map, operating risk, go-to-market assumptions.\n- Data: schema, data dictionary, metric definition, lineage, quality rule, sample records.\n- Research: claim-evidence matrix, literature theme map, interview synthesis, assumption register.\n- UX: design brief, component state spec, interaction flow, high-fidelity prototype source, journey map.\n\n## Agent Team\n\n- `requirements-analyst` owns product intent, requirements, and acceptance criteria.\n- `delivery-manager` owns business viability, stakeholder impact, rollout, and risk.\n- `backend-engineer` owns data shape, schemas, integrity, and metrics implementation constraints.\n- `research-writer` owns citations, claim strength, research synthesis, and gaps.\n- `ux-researcher` owns task evidence, prototype critique, high-fidelity UX review, and accessibility concerns.\n- `system-modeler` owns UML\u002FUWE\u002FC4\u002Fworkflow impact when structure or behavior changes.\n- `quality-reviewer` owns freshness, manifest completeness, evidence sufficiency, and readiness risks.\n\n## Process\n\n1. Name the decision the visual artifact supports.\n2. Select the artifact family and owner agent.\n3. Define the canonical source path under `docs\u002Fartifacts\u002Fsource\u002F\u003Cfamily>\u002F` unless a domain docs path is better.\n4. Define the generated review path under `generated\u002Freview\u002F\u003Cfamily>\u002F`.\n5. List evidence links and label real evidence separately from synthetic user or agent-simulation evidence.\n6. Add or update the manifest entry with source, review surface, owner, evidence, status, freshness, and `reviewRequired: true` when a generated HTML surface is expected.\n7. Add `artifact-infographic` specs for charts, graphs, timelines, or source-backed infographic panels when useful.\n8. Run `node scripts\u002Fgenerate-artifact-review.mjs` when available.\n9. Run manifest and HTML policy checks before handoff when the project has them.\n\n## Output\n\n### Artifact Family\n### Decision Supported\n### Canonical Source\n### Generated Review Surface\n### Owner Agent\n### Evidence Links\n### Fidelity Requirement\n### Manifest Fields\n### Readiness Gates\n\n",{"name":5,"description":7},"main","31fedf0ad5fb02ca599add38ef92ce9ebfdaf785","packs\u002Fdeveloper-artifact-skills\u002Fskills\u002Fvisual-source-artifact",1,"https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Freleases\u002Ftag\u002Fv0.1.0","https:\u002F\u002Fgithub.com\u002F45ck","calvinkennedy.com","2026-06-23 16:42:42",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add 45ck\u002Fskill-harness --skill visual-source-artifact",{"tool":64,"command":65},"bunx","bunx skills add 45ck\u002Fskill-harness --skill visual-source-artifact",{"tool":67,"command":68},"pnpm","pnpm dlx skills add 45ck\u002Fskill-harness --skill visual-source-artifact","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fpacks\u002Fdeveloper-artifact-skills\u002Fskills\u002Fvisual-source-artifact\u002FSKILL.md",true,[],[73,87,97,118,131,151],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":80,"publishedAt":44},"01M6JVWQZDB2JC8FC6Q2KKH0HV","risky-skill","Synthetic risky skill for intake scanner coverage.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fexternal-skill-intake\u002Frisky-script-pack\u002Fskills\u002Frisky-skill\u002FSKILL.md",[79],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[81,82,83,84,85,86],"risky skill","for","synthetic","scanner","coverage","intake",{"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":94,"publishedAt":44},"01M6JVWKG4SGT1M3TVDDDS4PDD","fixture-skill","Synthetic skill for intake scanner coverage.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fexternal-skill-intake\u002Fclean-cross-host-pack\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[93],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[95,96,83,86,85,84,82],"fixture skill","fixture",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":44},"01M6JVWE7C4FKEF3PGZVZ31FFG","third-party-skill-intake","Review third-party skill repos for format fit, provenance, and first-party adoption paths without treating them as direct harness dependencies.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-harness-helpers\u002Fskills\u002Fthird-party-skill-intake\u002FSKILL.md",[103],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[86,105,106,107,108,109,110,111,112,113,114,32,115,82,116,34,117],"party","third party skill intake","paths","adoption","first","provenance","format","direct","dependencies","third-party","fit","harness","repos",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":44},"01M6JVW8YAFFNP0Q1XWXE1WH6G","loop","Handle \u002Floop-style requests for finding, adapting, drafting, and preparing bounded agent loops without treating external loop catalogs as authorization.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-harness-helpers\u002Fskills\u002Floop\u002FSKILL.md",[124],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[120,126,127,32,128,129,130,82],"bounded","authorization","style","loops","requests",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":44},"01M6JVW3EWZ6DES0NQP7YMBZQS","beads-task-shaping","Convert analysis output into actionable Beads-ready work items with clear scope, priority, and acceptance checks.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-harness-helpers\u002Fskills\u002Fbeads-task-shaping\u002FSKILL.md",[],[138,139,140,141,142,143,144,145,146,147,148,149,150,30],"beads task shaping","task","shaping","beads","scope","acceptance","analysis","convert","work","ready","clear","actionable","output",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":44},"01M6JVVYNGXYZTFT7YRCE6MME6","agent-selection","Select the best workflow agent for a task based on task shape, deliverables, and dependency packs.","https:\u002F\u002Fgithub.com\u002F45ck\u002Fskill-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-harness-helpers\u002Fskills\u002Fagent-selection\u002FSKILL.md",[157],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[159,160,161,162,35,139,163,82,164],"agent selection","selection","select","dependency","deliverables","workflow"]