[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVBFZ66RT56ZDPV8V2ZNCB":3,"skill-same:01M7AVBFZ66RT56ZDPV8V2ZNCB":81},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7AVBFZ66RT56ZDPV8V2ZNCB","ui-craft-checks",null,"bonc-ai\u002Fcogseed","bonc-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F313335383?v=4","01M7AV826PEZKTFGW9MCPBERA7","东方国信 BONC","01M7AV827DEZPMD30Y94T1ZFKQ",19,"MIT","https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nownerAgent: bcfcb4921dce\nname: ui-craft-checks\ndescription_zh: \"UIDesigner 的完整 HTML 质量门槛；用于正式 review、QA、上线交接、严格保真或高风险复杂 UI，检查可访问性、状态、表单、排版、响应式、反模板和运行时。普通单页使用快速验证。\"\ndescription_en: \"UIDesigner's comprehensive HTML quality gate for formal review, QA, launch handoff, exact fidelity, or high-risk complex UI across accessibility, states, forms, typography, responsive behavior, anti-template quality, and runtime; ordinary single-page work uses the fast validator.\"\ncategory: rnd\n---\n\n# ui-craft-checks\n\nUse this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses `ui-design-executor` and its bundled validator without loading this full matrix. Pair standalone artifacts with `ui-artifact-workspace` when this specialist is triggered.\n\nThis skill does not replace `ui-html-renderer` or `ui-design-review`. It tells them what must be checked before delivery.\n\nRun the gate internally by default. Surface the full checklist only for review, handoff, QA, or when the user asks for the detailed pass\u002Ffail matrix.\n\n## When To Use\n\nUse this skill when:\n\n- The user asks for a formal review, QA matrix, hardening, launch-readiness, accessibility audit, or detailed handoff.\n- Exact screenshot\u002Fdesign-source fidelity needs comprehensive validation.\n- A complex form, live\u002Fdata surface, or composite interaction is high risk or has failed the fast gate.\n- The user explicitly requests a full craft or anti-template critique.\n\nFor ordinary single-page delivery and tiny text-only answers, skip this skill.\n\n## Severity\n\n- `P0`: Must fix before final delivery.\n- `P1`: Should fix before production or stakeholder review.\n- `P2`: Polish; fix when scope allows.\n\n## P0 Gates\n\nThe artifact fails the craft pass if any P0 is present:\n\n- **Not HTML by default**: a UI\u002Fdesign deliverable is only prose, PNG, SVG, Markdown, or a raw asset gallery when the user did not request that final format.\n- **Explicit format ignored**: the user requested a non-HTML final format but the artifact silently substitutes HTML or another format for it.\n- **Detached revision**: a normal follow-up creates a new sibling or regenerates an unrelated artifact instead of inspecting and patching the canonical artifact in place, losing accepted content or user edits.\n- **Broken artifact boundary**: a standalone deliverable has no stable artifact directory or valid manifest\u002Fentry, or it depends on missing local files, machine-specific absolute paths, undeclared secrets, or an unmentioned build step that prevents sharing or packaging.\n- **Source drift**: screenshot, Figma\u002Fdesign-source, or explicit contract structure is replaced by an unrelated dashboard, table, chart, sidebar, pricing page, or kanban board.\n- **Missing critical states**: a data-fetching or data-transforming surface does not implement reachable loading, populated, empty, error, and edge\u002Fpartial states. Mentioning them in rationale while shipping only populated DOM still fails.\n- **Broken form validation**: required fields lack labels\u002Fhelper\u002Ferror wiring, or the prototype omits pristine, dirty\u002Ftouched invalid, submitted-pending, recoverable server-error, or success behavior that the workflow can reach. A user-requested success\u002Ffailure outcome that exists only in an untriggered branch still fails.\n- **Keyboard\u002Faccessibility failure**: interactive controls are not keyboard reachable, focus-visible is absent, icon-only controls lack names, or native elements are replaced with inert divs.\n- **Unsafe live data**: live-ready artifacts persist tokens, credentials, cookies, auth headers, raw provider responses, or secret-like fields.\n- **Text\u002Flayout collision**: text overlaps controls, is clipped without intent, or mobile layout hides the primary action.\n- **Broken HTML\u002Fruntime**: invalid or malformed HTML, unclosed critical tags, inline JavaScript syntax\u002Fruntime errors, or missing root content causes a blank or unusable first render. Inline event handlers nested inside `innerHTML` strings are a P0 because their quote\u002Fescape layers are fragile. Mutating cached element-reference maps to redirect a renderer, clearing a container before querying\u002Fmoving its former descendants, or wrapping only `addEventListener(\"DOMContentLoaded\", init)` in `try\u002Fcatch` while leaving the later callback unguarded is also P0; use immutable references, detached fragments, one safe commit, a genuinely guarded initializer, and data hooks plus listeners\u002Fdelegation.\n- **False capability claim**: the response claims Figma import, connector refresh, external-browser validation, or accessibility checks happened when they did not.\n- **Invented evidence**: sample metrics, placeholder records, inferred copy, or guessed assets are presented as observed source content or production data.\n- **Raster route bypassed**: a requested original raster asset is replaced by an inline SVG\u002Fgradient or the whole UI is delegated, even though the dedicated raster capability is available. The asset brief also fails if its stated aspect ratio conflicts with its pixel dimensions, or if it names a save path without wiring that relative raster path and an honest fallback into the HTML.\n\n## P1 Gates\n\nFix or explicitly note these before handoff:\n\n- **Contrast and focus**: body text, muted text, control borders, semantic status, and focus rings need sufficient contrast.\n- **State composition**: empty states need a headline, explanation, and recovery action; errors need what happened, why, and how to recover.\n- **Typography hierarchy**: hierarchy should use at least two vectors such as size, weight, spacing, color, position, or grouping; avoid both flat hierarchy and noisy hierarchy.\n- **Motion discipline**: motion should explain state, space, or feedback. Avoid ambient motion in work tools. Translate\u002Fscale\u002Frotate\u002Fparallax motion should respect reduced motion.\n- **Form timing**: do not show error chrome on pristine fields; validate after blur\u002Fsubmit, then clear errors as the user fixes input.\n- **Responsive behavior**: navigation, filters, tables, side panels, fixed boards, and action bars need a defined mobile behavior.\n- **RTL\u002Fbidi readiness**: for multilingual or unknown user-generated content, prefer logical properties and isolate unknown-direction text with `dir=\"auto\"` or `\u003Cbdi>`.\n- **AI-template tells**: remove unjustified purple-blue glow gradients, generic 3-card rows, stock-placeholder imagery, oversized rounded cards everywhere, decorative blobs, and empty marketing adjectives.\n- **Weak component stories**: reusable components lack meaningful variants\u002Fstates, making later implementation or review depend on guesswork.\n\n## P2 Polish\n\nImprove when time allows:\n\n- Tighten rhythm so related items align and unrelated items separate clearly.\n- Reduce redundant chips, badges, and microcopy that compete with the main task.\n- Prefer borders and layout clarity over heavy shadows.\n- Give the design one product-specific signature device that helps the workflow.\n- Replace arbitrary icons with familiar symbols and accessible labels.\n\n## Required Check Matrix\n\nBefore final delivery, internally verify this matrix:\n\n```markdown\n## Craft Check\n- HTML default:\n- Explicit format:\n- Artifact continuity:\n- Package boundary:\n- HTML syntax\u002Fruntime:\n- Source\u002Fdesign fidelity:\n- State coverage:\n- State implementation evidence:\n- Accessibility:\n- Form behavior:\n- Typography hierarchy:\n- Motion:\n- Responsive:\n- Live\u002Fsecurity:\n- Anti-template:\n- Optional automation:\n- Remaining risks:\n```\n\nJudge evidence, not vocabulary. A state passes only when it exists in the rendered artifact, DOM, component story, or executable rendering branch and there is a clear way to reach or inspect it. A validation passes only when the named check actually ran; otherwise mark it `not run`, keep the risk visible, and give the future execution action plus a concrete pass criterion instead of a bare checklist label.\n\nFor simple final answers, summarize only failures and verification performed. Do not clutter the user-facing artifact with a checklist unless it is a review page, handoff, QA report, or requested by the user.\n\n## Optional Automated Checks\n\nUse automated checks only when an HTML file\u002Fapp screen exists and the environment already supports the tool or the user asks for stronger validation. Do not install new dependencies just to satisfy this skill.\n\n- Accessibility: if axe-core, pa11y, Playwright accessibility helpers, or an equivalent existing checker is available, run it and fix actionable violations around labels, names, landmarks, contrast, focus order, and keyboard reachability.\n- Visual regression: when a source screenshot or prior HTML screenshot exists, use screenshot comparison or viewport screenshots to catch blank render, source drift, clipped text, overlap, broken assets, and unintended layout shifts.\n- Component stories: when Storybook or a local component preview exists, check the relevant states\u002Fstories rather than only the full page.\n- DOM\u002Fsource inspection: when browser automation is unavailable, inspect the generated HTML\u002FCSS\u002FJS for semantic elements, labels, state markup, media queries, and unsafe persisted data.\n- HTML syntax\u002Fruntime: when possible, parse the generated HTML, check inline script syntax, inspect console\u002Fruntime errors, and confirm the rendered body is non-blank with the primary region visible.\n\nAutomated tools are evidence, not a substitute for design judgment. If a tool cannot run, state that validation was reasoned from source\u002FHTML and list the remaining risks.\n\n## How To Apply\n\n1. Inspect the rendered HTML or app screen when possible.\n2. Compare it to `ui-design-source` and `ui-design-contract` outputs if present.\n3. Check HTML syntax\u002Fruntime and first render before visual polish; a blank artifact is a P0 even if the design direction is good.\n4. Check P0 first; fix P0 rather than merely listing it. Inspect the artifact for state DOM\u002Frendering branches instead of accepting a prose state inventory.\n5. Check P1\u002FP2 according to scope.\n6. Use optional automated checks only when available and relevant.\n7. If verification cannot run, say which checks were reasoned from source\u002FHTML and which still require rendered inspection.\n","# ui-craft-checks\n\nUse this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses `ui-design-executor` and its bundled validator without loading this full matrix. Pair standalone artifacts with `ui-artifact-workspace` when this specialist is triggered.\n\nThis skill does not replace `ui-html-renderer` or `ui-design-review`. It tells them what must be checked before delivery.\n\nRun the gate internally by default. Surface the full checklist only for review, handoff, QA, or when the user asks for the detailed pass\u002Ffail matrix.\n\n## When To Use\n\nUse this skill when:\n\n- The user asks for a formal review, QA matrix, hardening, launch-readiness, accessibility audit, or detailed handoff.\n- Exact screenshot\u002Fdesign-source fidelity needs comprehensive validation.\n- A complex form, live\u002Fdata surface, or composite interaction is high risk or has failed the fast gate.\n- The user explicitly requests a full craft or anti-template critique.\n\nFor ordinary single-page delivery and tiny text-only answers, skip this skill.\n\n## Severity\n\n- `P0`: Must fix before final delivery.\n- `P1`: Should fix before production or stakeholder review.\n- `P2`: Polish; fix when scope allows.\n\n## P0 Gates\n\nThe artifact fails the craft pass if any P0 is present:\n\n- **Not HTML by default**: a UI\u002Fdesign deliverable is only prose, PNG, SVG, Markdown, or a raw asset gallery when the user did not request that final format.\n- **Explicit format ignored**: the user requested a non-HTML final format but the artifact silently substitutes HTML or another format for it.\n- **Detached revision**: a normal follow-up creates a new sibling or regenerates an unrelated artifact instead of inspecting and patching the canonical artifact in place, losing accepted content or user edits.\n- **Broken artifact boundary**: a standalone deliverable has no stable artifact directory or valid manifest\u002Fentry, or it depends on missing local files, machine-specific absolute paths, undeclared secrets, or an unmentioned build step that prevents sharing or packaging.\n- **Source drift**: screenshot, Figma\u002Fdesign-source, or explicit contract structure is replaced by an unrelated dashboard, table, chart, sidebar, pricing page, or kanban board.\n- **Missing critical states**: a data-fetching or data-transforming surface does not implement reachable loading, populated, empty, error, and edge\u002Fpartial states. Mentioning them in rationale while shipping only populated DOM still fails.\n- **Broken form validation**: required fields lack labels\u002Fhelper\u002Ferror wiring, or the prototype omits pristine, dirty\u002Ftouched invalid, submitted-pending, recoverable server-error, or success behavior that the workflow can reach. A user-requested success\u002Ffailure outcome that exists only in an untriggered branch still fails.\n- **Keyboard\u002Faccessibility failure**: interactive controls are not keyboard reachable, focus-visible is absent, icon-only controls lack names, or native elements are replaced with inert divs.\n- **Unsafe live data**: live-ready artifacts persist tokens, credentials, cookies, auth headers, raw provider responses, or secret-like fields.\n- **Text\u002Flayout collision**: text overlaps controls, is clipped without intent, or mobile layout hides the primary action.\n- **Broken HTML\u002Fruntime**: invalid or malformed HTML, unclosed critical tags, inline JavaScript syntax\u002Fruntime errors, or missing root content causes a blank or unusable first render. Inline event handlers nested inside `innerHTML` strings are a P0 because their quote\u002Fescape layers are fragile. Mutating cached element-reference maps to redirect a renderer, clearing a container before querying\u002Fmoving its former descendants, or wrapping only `addEventListener(\"DOMContentLoaded\", init)` in `try\u002Fcatch` while leaving the later callback unguarded is also P0; use immutable references, detached fragments, one safe commit, a genuinely guarded initializer, and data hooks plus listeners\u002Fdelegation.\n- **False capability claim**: the response claims Figma import, connector refresh, external-browser validation, or accessibility checks happened when they did not.\n- **Invented evidence**: sample metrics, placeholder records, inferred copy, or guessed assets are presented as observed source content or production data.\n- **Raster route bypassed**: a requested original raster asset is replaced by an inline SVG\u002Fgradient or the whole UI is delegated, even though the dedicated raster capability is available. The asset brief also fails if its stated aspect ratio conflicts with its pixel dimensions, or if it names a save path without wiring that relative raster path and an honest fallback into the HTML.\n\n## P1 Gates\n\nFix or explicitly note these before handoff:\n\n- **Contrast and focus**: body text, muted text, control borders, semantic status, and focus rings need sufficient contrast.\n- **State composition**: empty states need a headline, explanation, and recovery action; errors need what happened, why, and how to recover.\n- **Typography hierarchy**: hierarchy should use at least two vectors such as size, weight, spacing, color, position, or grouping; avoid both flat hierarchy and noisy hierarchy.\n- **Motion discipline**: motion should explain state, space, or feedback. Avoid ambient motion in work tools. Translate\u002Fscale\u002Frotate\u002Fparallax motion should respect reduced motion.\n- **Form timing**: do not show error chrome on pristine fields; validate after blur\u002Fsubmit, then clear errors as the user fixes input.\n- **Responsive behavior**: navigation, filters, tables, side panels, fixed boards, and action bars need a defined mobile behavior.\n- **RTL\u002Fbidi readiness**: for multilingual or unknown user-generated content, prefer logical properties and isolate unknown-direction text with `dir=\"auto\"` or `\u003Cbdi>`.\n- **AI-template tells**: remove unjustified purple-blue glow gradients, generic 3-card rows, stock-placeholder imagery, oversized rounded cards everywhere, decorative blobs, and empty marketing adjectives.\n- **Weak component stories**: reusable components lack meaningful variants\u002Fstates, making later implementation or review depend on guesswork.\n\n## P2 Polish\n\nImprove when time allows:\n\n- Tighten rhythm so related items align and unrelated items separate clearly.\n- Reduce redundant chips, badges, and microcopy that compete with the main task.\n- Prefer borders and layout clarity over heavy shadows.\n- Give the design one product-specific signature device that helps the workflow.\n- Replace arbitrary icons with familiar symbols and accessible labels.\n\n## Required Check Matrix\n\nBefore final delivery, internally verify this matrix:\n\n```markdown\n## Craft Check\n- HTML default:\n- Explicit format:\n- Artifact continuity:\n- Package boundary:\n- HTML syntax\u002Fruntime:\n- Source\u002Fdesign fidelity:\n- State coverage:\n- State implementation evidence:\n- Accessibility:\n- Form behavior:\n- Typography hierarchy:\n- Motion:\n- Responsive:\n- Live\u002Fsecurity:\n- Anti-template:\n- Optional automation:\n- Remaining risks:\n```\n\nJudge evidence, not vocabulary. A state passes only when it exists in the rendered artifact, DOM, component story, or executable rendering branch and there is a clear way to reach or inspect it. A validation passes only when the named check actually ran; otherwise mark it `not run`, keep the risk visible, and give the future execution action plus a concrete pass criterion instead of a bare checklist label.\n\nFor simple final answers, summarize only failures and verification performed. Do not clutter the user-facing artifact with a checklist unless it is a review page, handoff, QA report, or requested by the user.\n\n## Optional Automated Checks\n\nUse automated checks only when an HTML file\u002Fapp screen exists and the environment already supports the tool or the user asks for stronger validation. Do not install new dependencies just to satisfy this skill.\n\n- Accessibility: if axe-core, pa11y, Playwright accessibility helpers, or an equivalent existing checker is available, run it and fix actionable violations around labels, names, landmarks, contrast, focus order, and keyboard reachability.\n- Visual regression: when a source screenshot or prior HTML screenshot exists, use screenshot comparison or viewport screenshots to catch blank render, source drift, clipped text, overlap, broken assets, and unintended layout shifts.\n- Component stories: when Storybook or a local component preview exists, check the relevant states\u002Fstories rather than only the full page.\n- DOM\u002Fsource inspection: when browser automation is unavailable, inspect the generated HTML\u002FCSS\u002FJS for semantic elements, labels, state markup, media queries, and unsafe persisted data.\n- HTML syntax\u002Fruntime: when possible, parse the generated HTML, check inline script syntax, inspect console\u002Fruntime errors, and confirm the rendered body is non-blank with the primary region visible.\n\nAutomated tools are evidence, not a substitute for design judgment. If a tool cannot run, state that validation was reasoned from source\u002FHTML and list the remaining risks.\n\n## How To Apply\n\n1. Inspect the rendered HTML or app screen when possible.\n2. Compare it to `ui-design-source` and `ui-design-contract` outputs if present.\n3. Check HTML syntax\u002Fruntime and first render before visual polish; a blank artifact is a P0 even if the design direction is good.\n4. Check P0 first; fix P0 rather than merely listing it. Inspect the artifact for state DOM\u002Frendering branches instead of accepting a prose state inventory.\n5. Check P1\u002FP2 according to scope.\n6. Use optional automated checks only when available and relevant.\n7. If verification cannot run, say which checks were reasoned from source\u002FHTML and which still require rendered inspection.\n",{"name":5,"category":23,"ownerAgent":24,"description_en":25,"description_zh":26},"rnd","bcfcb4921dce","UIDesigner's comprehensive HTML quality gate for formal review, QA, launch handoff, exact fidelity, or high-risk complex UI across accessibility, states, forms, typography, responsive behavior, anti-template quality, and runtime; ordinary single-page work uses the fast validator.","UIDesigner 的完整 HTML 质量门槛；用于正式 review、QA、上线交接、严格保真或高风险复杂 UI，检查可访问性、状态、表单、排版、响应式、反模板和运行时。普通单页使用快速验证。","main","6afb98b7a438d4b993ba23f3af1494c862d80378","resources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks",10,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed","https:\u002F\u002Fcogseed.ai","https:\u002F\u002Fgithub.com\u002Fbonc-ai","https:\u002F\u002Fwww.bonc.com.cn\u002F","北京东方国信科技股份有限公司开源组织 · Enterprise open source by BONC","2026-11-13 21:46:31",{"source":7,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add bonc-ai\u002Fcogseed --skill ui-craft-checks",{"tool":43,"command":44},"bunx","bunx skills add bonc-ai\u002Fcogseed --skill ui-craft-checks",{"tool":46,"command":47},"pnpm","pnpm dlx skills add bonc-ai\u002Fcogseed --skill ui-craft-checks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002FSKILL.md",true,[51,57,61,65,69,73,77],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"artifact.yaml","REFERENCE","参考文档",897,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002Fartifact.yaml",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Fevals.json",259,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002Fevals\u002Fevals.json",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fbusiness-ontology.yaml",70,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002Freferences\u002Fbusiness-ontology.yaml",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fsecurity-manifest.yaml",2479,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002Freferences\u002Fsecurity-manifest.yaml",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fskill-spec.yaml",466,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002Freferences\u002Fskill-spec.yaml",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fvalidation-contract.yaml",56,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002Freferences\u002Fvalidation-contract.yaml",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"schemas.json",40,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-craft-checks\u002Fschemas.json",[82,89,96,103,110,117],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7AVTAEJDDZ3YFV85AK28FWN","sample-supply-chain","供应链样本：安装钩子 + 拼写伪装 + 源覆盖。","https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fguardrail\u002Fskill-sentry\u002Ftests\u002Ffixtures\u002Fv2-samples\u002Fsample-supply-chain-skill\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7AVT84YQ5GZDMB9PRTEBV8V","sample-prose-only","纯散文安全守则样本：禁止某行为的说明不等于该行为。","https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fguardrail\u002Fskill-sentry\u002Ftests\u002Ffixtures\u002Fv2-samples\u002Fsample-prose-only-skill\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7AVT59NWX4M2EZJKRXMEPGB","sample-obfuscated","混淆载荷样本：解码与执行共现。","https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fguardrail\u002Fskill-sentry\u002Ftests\u002Ffixtures\u002Fv2-samples\u002Fsample-obfuscated-skill\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M7AVT246DRNSJ5D9JQRK4QKP","sample-hidden-content","隐藏内容载荷样本：用于回归「不可见字符不做上下文降权」这一不变量。","https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fguardrail\u002Fskill-sentry\u002Ftests\u002Ffixtures\u002Fv2-samples\u002Fsample-hidden-content-skill\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M7AVSYR91DFC262VQ23BAZA1","sample-evasion","反规避样本：危险内容只以「不可见字符切断」与「编码后」两种形式出现。","https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fguardrail\u002Fskill-sentry\u002Ftests\u002Ffixtures\u002Fv2-samples\u002Fsample-evasion-skill\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":18},"01M7AVSVMGH458JZC3Q454QWTK","sample-agentic","代理运行时风险样本：配置篡改 + 隐蔽指令。","https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fguardrail\u002Fskill-sentry\u002Ftests\u002Ffixtures\u002Fv2-samples\u002Fsample-agentic-skill\u002FSKILL.md",[],[]]