[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVBSNA58B3AX5A6N2RPV75":3,"skill-same:01M7AVBSNA58B3AX5A6N2RPV75":87},{"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},"01M7AVBSNA58B3AX5A6N2RPV75","ui-design-executor",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-design-executor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nownerAgent: bcfcb4921dce\nname: ui-design-executor\ndescription_zh: \"UIDesigner 的紧凑默认执行器；用于普通单页、组件、截图改版和仓库内 UI 实现，以最少技能和工具循环完成设计、HTML\u002F显式格式产物、相关状态、快速验证与交付。\"\ndescription_en: \"UIDesigner's compact default executor for ordinary single-page, component, screenshot-redesign, and in-repo UI work; complete the design, HTML or explicit-format artifact, relevant states, fast validation, and delivery with minimal skill loading and tool loops.\"\ncategory: rnd\n---\n\n# ui-design-executor\n\nUse this as UIDesigner's default execution skill. It contains the baseline design, accessibility, HTML, runtime-safety, responsive, taste, and verification rules needed by ordinary UI work. Do not load the separate system, control, taste, color, renderer, or craft skills merely to repeat these baseline rules.\n\nPair it with:\n\n- `ui-artifact-workspace` for a new standalone artifact or an in-place artifact revision.\n- `ui-design-source` when an inspectable screenshot, Figma export, PDF, design JSON, existing HTML, or other fidelity source exists.\n- One specialist skill only when its trigger below materially changes the work.\n\n## Minimal Routing\n\nUse the fast path for a clear single screen, component, local redesign, or small repo UI change:\n\n1. Load this skill.\n2. Add `ui-artifact-workspace` only for standalone output or artifact revision.\n3. Add `ui-design-source` only for inspectable source evidence.\n4. Build, run the fast gate, publish, and stop.\n\nDo not load `ui-design-contract`, `ui-design-system`, `ui-controls-accessibility`, `ui-taste`, `ui-color`, `ui-html-renderer`, and `ui-craft-checks` together. Load a specialist only for its narrow trigger:\n\n- `ui-design-contract`: durable multi-screen\u002Fbrand direction, conflicting references, or a genuinely vague visual system.\n- `ui-reference-packs`: explicit named style\u002Freference need and insufficient source\u002Frepo direction.\n- `ui-design-system`: reusable token\u002Fcomponent system work.\n- `ui-controls-accessibility`: accessibility audit, complex form, or non-trivial composite widget.\n- `ui-taste`: explicit anti-generic critique, expressive restyle, or brand\u002Fvisual-thesis challenge.\n- `ui-color`: palette, dark mode, chart color, or contrast-focused work.\n- `ui-html-renderer`: unusually complex stateful HTML, runtime-risk repair, or detailed source-to-HTML handoff.\n- `ui-craft-checks`: formal review, QA, launch handoff, exact-fidelity inspection, or high-risk complex UI.\n- `ui-live-artifact`: refreshable, connector-backed, recurring, or auditable data UI.\n- `ui-design-review`: review\u002Fcritique\u002Fpolish where findings are the primary result.\n\nIf a specialist is loaded, keep this executor as the coordinator instead of recursively loading every skill named by that specialist.\n\n## Execution Budget\n\nFor a fast-path task, normally stay within six model\u002Ftool loops and eight tool calls after the needed skills are loaded. This is a coordination target, not permission to skip required evidence.\n\n- Skip a formal execution plan for one clear screen\u002Fcomponent or a bounded local edit. Use an internal compact brief instead.\n- Inspect the source\u002Ftarget once. Batch independent reads when several small files are required.\n- Write the main entry once. Do not repeatedly re-read a newly written full HTML file unless a write was truncated, a validator points to a location, or a later edit requires a narrow range.\n- Run one grouped deterministic validation command instead of many exploratory shell checks.\n- Create `DESIGN.md` only for multi-screen work, reusable systems, brand\u002Fidentity work, formal handoff, or an explicit user request. A simple standalone screen normally needs only its entry and `artifact.json`.\n- Do not create optional state galleries, documentation, assets, or dependencies that the brief does not need.\n- If the budget must be exceeded, continue only for a concrete blocker, failed validation, source ambiguity, or requested complexity; consolidate the remaining work rather than repeating broad inspection.\n\n## Compact Design Brief\n\nBefore editing, resolve these facts internally:\n\n- Subject\u002Fproduct and target user.\n- Page's single job and primary workflow.\n- Source of truth and confidence: user brief, screenshot\u002Fexport, current artifact, or repo UI.\n- Output format and canonical target.\n- Keep\u002Fchange boundaries and responsive constraint.\n- Visual thesis: hierarchy\u002Flayout, density, two precise tone words, role-based palette\u002Ftype, one subject-specific signature, and one generic choice rejected.\n\nFor a screenshot or existing screen, preserve its information architecture and visible content unless the user requests a structural redesign. Do not invent dashboards, tables, charts, metrics, sidebars, or operational data that the source and brief do not support.\n\n## Build Rules\n\n- Design deliverables default to HTML; honor an explicit SVG, PDF, React, Vue, PNG, Markdown, or other final format.\n- For a standalone HTML artifact, prefer self-contained semantic HTML\u002FCSS with minimal JavaScript and no remote runtime dependency.\n- For repo implementation, reuse the existing framework, components, tokens, icons, routes, and conventions. The repo screen is canonical; do not create a parallel preview unless requested.\n- Use role tokens for background, surface, text, muted text, border, accent, focus, and semantic states. Ground density, radius, shadow, type, imagery, and motion in the subject rather than a fixed house style.\n- Open on the actual product workflow, not a marketing hero. Remove unjustified glow gradients, bento\u002Fcard stacks, decorative blobs, oversized rounded panels, and empty promotional copy.\n- Keep controls semantic and keyboard reachable; provide visible focus and accessible names. Implement the expected keyboard model for composite controls such as tabs.\n- Define responsive behavior for navigation, primary action, dense data, long localized text, and narrow targets. If 320px or no horizontal scroll is explicit, recompose rather than relying on horizontal scrolling.\n\nImplement only states the workflow can reach, but implement those states in real DOM\u002Fcomponent branches:\n\n- Data fetching\u002Ftransformation: populated, loading, empty, error, and partial\u002Fstale when the surface actually fetches or transforms data.\n- Forms: pristine, dirty\u002Ftouched invalid, submitted-pending, recoverable error, and success when the task includes a real form workflow.\n- Explicit success\u002Ffailure requests: distinct named triggers, rendered feedback, and recovery; an unreachable conditional or prose list does not count.\n- Static navigation or presentation screens do not need artificial data-fetch states merely to satisfy a checklist.\n\nFor interactive standalone HTML:\n\n- Keep meaningful primary content in static HTML before scripts run.\n- Use `addEventListener`, delegation, or data-action hooks; do not nest inline handlers inside generated HTML strings.\n- Keep cached element references immutable. Build complex state in a fragment\u002Fdetached container and commit once.\n- Guard the real initialization callback so a failure leaves the static shell visible and shows an actionable fallback.\n\n## Fast Gate\n\nFor a standalone HTML artifact, run the bundled validator when Node and shell execution are available:\n\n```text\n\"$COGSEED_NODE\" \"$COGSEED_PC_DIR\u002Fbin\u002Frun-skill.cjs\" \\\n  ui-design-executor validate-html-artifact -- \\\n  \u003Cartifact-directory>\n```\n\nIt checks strict `artifact.json`, entry\u002Ffile inventory, safe relative paths, critical HTML structure, meaningful static content, inline JavaScript syntax, fragile generated inline handlers, and local references in one call. Fix every reported error. Treat warnings as review prompts, not automatic failures.\n\nFor an in-place revision, validate the changed entry before incrementing the manifest when practical, then run the final package check after the single revision increment. Also smoke-check the requested change, non-blank first render, primary workflow, responsive behavior, and local asset\u002Freference resolution.\n\nUse embedded preview, DOM inspection, screenshots, interaction playback, or accessibility tooling only when already available and proportionate to the task. Do not open an external browser or install dependencies by default.\n\nIf a parser\u002Fbrowser\u002Fruntime check did not run, mark it `not run`; do not convert source inspection into a runtime claim.\n\n## Delivery\n\nLead with the canonical directory or repo screen, entry\u002Ffinal format, revision for standalone artifacts, files changed, checks actually run, and remaining risks. Keep ordinary summaries compact. Surface a full design contract or craft matrix only when the user requested a review, system, handoff, or QA report.\n","# ui-design-executor\n\nUse this as UIDesigner's default execution skill. It contains the baseline design, accessibility, HTML, runtime-safety, responsive, taste, and verification rules needed by ordinary UI work. Do not load the separate system, control, taste, color, renderer, or craft skills merely to repeat these baseline rules.\n\nPair it with:\n\n- `ui-artifact-workspace` for a new standalone artifact or an in-place artifact revision.\n- `ui-design-source` when an inspectable screenshot, Figma export, PDF, design JSON, existing HTML, or other fidelity source exists.\n- One specialist skill only when its trigger below materially changes the work.\n\n## Minimal Routing\n\nUse the fast path for a clear single screen, component, local redesign, or small repo UI change:\n\n1. Load this skill.\n2. Add `ui-artifact-workspace` only for standalone output or artifact revision.\n3. Add `ui-design-source` only for inspectable source evidence.\n4. Build, run the fast gate, publish, and stop.\n\nDo not load `ui-design-contract`, `ui-design-system`, `ui-controls-accessibility`, `ui-taste`, `ui-color`, `ui-html-renderer`, and `ui-craft-checks` together. Load a specialist only for its narrow trigger:\n\n- `ui-design-contract`: durable multi-screen\u002Fbrand direction, conflicting references, or a genuinely vague visual system.\n- `ui-reference-packs`: explicit named style\u002Freference need and insufficient source\u002Frepo direction.\n- `ui-design-system`: reusable token\u002Fcomponent system work.\n- `ui-controls-accessibility`: accessibility audit, complex form, or non-trivial composite widget.\n- `ui-taste`: explicit anti-generic critique, expressive restyle, or brand\u002Fvisual-thesis challenge.\n- `ui-color`: palette, dark mode, chart color, or contrast-focused work.\n- `ui-html-renderer`: unusually complex stateful HTML, runtime-risk repair, or detailed source-to-HTML handoff.\n- `ui-craft-checks`: formal review, QA, launch handoff, exact-fidelity inspection, or high-risk complex UI.\n- `ui-live-artifact`: refreshable, connector-backed, recurring, or auditable data UI.\n- `ui-design-review`: review\u002Fcritique\u002Fpolish where findings are the primary result.\n\nIf a specialist is loaded, keep this executor as the coordinator instead of recursively loading every skill named by that specialist.\n\n## Execution Budget\n\nFor a fast-path task, normally stay within six model\u002Ftool loops and eight tool calls after the needed skills are loaded. This is a coordination target, not permission to skip required evidence.\n\n- Skip a formal execution plan for one clear screen\u002Fcomponent or a bounded local edit. Use an internal compact brief instead.\n- Inspect the source\u002Ftarget once. Batch independent reads when several small files are required.\n- Write the main entry once. Do not repeatedly re-read a newly written full HTML file unless a write was truncated, a validator points to a location, or a later edit requires a narrow range.\n- Run one grouped deterministic validation command instead of many exploratory shell checks.\n- Create `DESIGN.md` only for multi-screen work, reusable systems, brand\u002Fidentity work, formal handoff, or an explicit user request. A simple standalone screen normally needs only its entry and `artifact.json`.\n- Do not create optional state galleries, documentation, assets, or dependencies that the brief does not need.\n- If the budget must be exceeded, continue only for a concrete blocker, failed validation, source ambiguity, or requested complexity; consolidate the remaining work rather than repeating broad inspection.\n\n## Compact Design Brief\n\nBefore editing, resolve these facts internally:\n\n- Subject\u002Fproduct and target user.\n- Page's single job and primary workflow.\n- Source of truth and confidence: user brief, screenshot\u002Fexport, current artifact, or repo UI.\n- Output format and canonical target.\n- Keep\u002Fchange boundaries and responsive constraint.\n- Visual thesis: hierarchy\u002Flayout, density, two precise tone words, role-based palette\u002Ftype, one subject-specific signature, and one generic choice rejected.\n\nFor a screenshot or existing screen, preserve its information architecture and visible content unless the user requests a structural redesign. Do not invent dashboards, tables, charts, metrics, sidebars, or operational data that the source and brief do not support.\n\n## Build Rules\n\n- Design deliverables default to HTML; honor an explicit SVG, PDF, React, Vue, PNG, Markdown, or other final format.\n- For a standalone HTML artifact, prefer self-contained semantic HTML\u002FCSS with minimal JavaScript and no remote runtime dependency.\n- For repo implementation, reuse the existing framework, components, tokens, icons, routes, and conventions. The repo screen is canonical; do not create a parallel preview unless requested.\n- Use role tokens for background, surface, text, muted text, border, accent, focus, and semantic states. Ground density, radius, shadow, type, imagery, and motion in the subject rather than a fixed house style.\n- Open on the actual product workflow, not a marketing hero. Remove unjustified glow gradients, bento\u002Fcard stacks, decorative blobs, oversized rounded panels, and empty promotional copy.\n- Keep controls semantic and keyboard reachable; provide visible focus and accessible names. Implement the expected keyboard model for composite controls such as tabs.\n- Define responsive behavior for navigation, primary action, dense data, long localized text, and narrow targets. If 320px or no horizontal scroll is explicit, recompose rather than relying on horizontal scrolling.\n\nImplement only states the workflow can reach, but implement those states in real DOM\u002Fcomponent branches:\n\n- Data fetching\u002Ftransformation: populated, loading, empty, error, and partial\u002Fstale when the surface actually fetches or transforms data.\n- Forms: pristine, dirty\u002Ftouched invalid, submitted-pending, recoverable error, and success when the task includes a real form workflow.\n- Explicit success\u002Ffailure requests: distinct named triggers, rendered feedback, and recovery; an unreachable conditional or prose list does not count.\n- Static navigation or presentation screens do not need artificial data-fetch states merely to satisfy a checklist.\n\nFor interactive standalone HTML:\n\n- Keep meaningful primary content in static HTML before scripts run.\n- Use `addEventListener`, delegation, or data-action hooks; do not nest inline handlers inside generated HTML strings.\n- Keep cached element references immutable. Build complex state in a fragment\u002Fdetached container and commit once.\n- Guard the real initialization callback so a failure leaves the static shell visible and shows an actionable fallback.\n\n## Fast Gate\n\nFor a standalone HTML artifact, run the bundled validator when Node and shell execution are available:\n\n```text\n\"$COGSEED_NODE\" \"$COGSEED_PC_DIR\u002Fbin\u002Frun-skill.cjs\" \\\n  ui-design-executor validate-html-artifact -- \\\n  \u003Cartifact-directory>\n```\n\nIt checks strict `artifact.json`, entry\u002Ffile inventory, safe relative paths, critical HTML structure, meaningful static content, inline JavaScript syntax, fragile generated inline handlers, and local references in one call. Fix every reported error. Treat warnings as review prompts, not automatic failures.\n\nFor an in-place revision, validate the changed entry before incrementing the manifest when practical, then run the final package check after the single revision increment. Also smoke-check the requested change, non-blank first render, primary workflow, responsive behavior, and local asset\u002Freference resolution.\n\nUse embedded preview, DOM inspection, screenshots, interaction playback, or accessibility tooling only when already available and proportionate to the task. Do not open an external browser or install dependencies by default.\n\nIf a parser\u002Fbrowser\u002Fruntime check did not run, mark it `not run`; do not convert source inspection into a runtime claim.\n\n## Delivery\n\nLead with the canonical directory or repo screen, entry\u002Ffinal format, revision for standalone artifacts, files changed, checks actually run, and remaining risks. Keep ordinary summaries compact. Surface a full design contract or craft matrix only when the user requested a review, system, handoff, or QA report.\n",{"name":5,"category":23,"ownerAgent":24,"description_en":25,"description_zh":26},"rnd","bcfcb4921dce","UIDesigner's compact default executor for ordinary single-page, component, screenshot-redesign, and in-repo UI work; complete the design, HTML or explicit-format artifact, relevant states, fast validation, and delivery with minimal skill loading and tool loops.","UIDesigner 的紧凑默认执行器；用于普通单页、组件、截图改版和仓库内 UI 实现，以最少技能和工具循环完成设计、HTML\u002F显式格式产物、相关状态、快速验证与交付。","main","6afb98b7a438d4b993ba23f3af1494c862d80378","resources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor",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-design-executor",{"tool":43,"command":44},"bunx","bunx skills add bonc-ai\u002Fcogseed --skill ui-design-executor",{"tool":46,"command":47},"pnpm","pnpm dlx skills add bonc-ai\u002Fcogseed --skill ui-design-executor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor\u002FSKILL.md",true,[51,57,61,65,69,73,77,81],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"artifact.yaml","REFERENCE","参考文档",924,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor\u002Fartifact.yaml",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Fevals.json",246,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor\u002Fevals\u002Fevals.json",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fbusiness-ontology.yaml",73,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor\u002Freferences\u002Fbusiness-ontology.yaml",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fsecurity-manifest.yaml",2940,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor\u002Freferences\u002Fsecurity-manifest.yaml",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fskill-spec.yaml",450,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor\u002Freferences\u002Fskill-spec.yaml",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fvalidation-contract.yaml",59,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor\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-design-executor\u002Fschemas.json",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fvalidate-html-artifact.mjs","SCRIPT","脚本",7403,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-executor\u002Fscripts\u002Fvalidate-html-artifact.mjs",[88,95,102,109,116,123],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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",[],[]]