[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVBMC2ZHVSPPR7G0S1HP9S":3,"skill-same:01M7AVBMC2ZHVSPPR7G0S1HP9S":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},"01M7AVBMC2ZHVSPPR7G0S1HP9S","ui-design-contract",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-contract\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nownerAgent: bcfcb4921dce\nname: ui-design-contract\ndescription_zh: \"为多屏、品牌、长期复用或参考冲突的 UIDesigner 任务建立持久设计契约，覆盖 DESIGN.md、source screen contract、tokens、keep\u002Fchange\u002Fdo-not-copy 边界和实现交接；普通单屏截图任务使用紧凑执行器即可。\"\ndescription_en: \"Create durable UIDesigner design contracts for multi-screen, brand, long-lived, or conflicting-reference work across DESIGN.md, source-screen rules, tokens, keep\u002Fchange\u002Fdo-not-copy boundaries, and implementation handoff; ordinary single-screen screenshot work stays on the compact executor.\"\ncategory: rnd\n---\n\n# ui-design-contract\n\nUse this skill before rendering when the direction must persist across multiple screens\u002Fcomponents, brand or system work, conflicting references, formal handoff, or a genuinely vague visual system. Ordinary single-screen screenshots and clear briefs use `ui-design-executor`'s compact source\u002Fvisual thesis instead of loading a full durable contract.\n\nThe contract is not extra ceremony. It prevents generic templates, protects the user's reference intent, and gives the HTML artifact a stable design source of truth.\n\nFor standalone work, keep any long-lived `DESIGN.md` inside the canonical directory chosen by `ui-artifact-workspace`. On later revisions, read and update that contract in place only when the accepted design direction actually changes.\n\nWhen the source is a Figma link\u002Fexport, design JSON, PDF, or design-tool screenshot, use `ui-design-source` first so the contract is grounded in inspectable frames, components, variables, and fidelity boundaries.\n\nWhen a visual benchmark or page pattern is needed, pair this skill with `ui-reference-packs` after the contract is drafted. Skip reference packs when the screenshot, repo tokens, or existing design system already provide enough direction. The contract decides what must be preserved; reference packs only help choose style DNA and pattern boundaries.\n\n## When To Create A Contract\n\nCreate a compact durable contract before HTML when any of these are true:\n\n- The screenshot\u002Freference spans multiple screens, must establish a reusable direction, or contains conflicting evidence that a compact executor snapshot cannot resolve.\n- The user says \"make it feel like this\", \"参考这个\", \"做同款但不照抄\", or gives brand\u002Fstyle references.\n- The request spans more than one screen, component family, or visual system.\n- The user asks for a design system, brand board, logo\u002Fidentity board, or implementation handoff.\n- Existing app tokens\u002Fcomponents are unclear and the agent must infer a direction.\n\nIf the user only asks for a tiny local UI tweak with a clear existing system, a full contract can be a short inline \"contract snapshot\".\n\n## Evidence Ledger\n\nEvery contract separates facts from guesses:\n\n- `observed`: visible in the screenshot, HTML, repo, Figma notes, or rendered UI.\n- `provided`: explicitly stated by the user.\n- `inferred`: a reasonable choice made from context.\n- `unknown`: missing information that could change the design.\n\nDo not let inferred items override observed screenshot structure or provided user constraints.\nDo not let an inaccessible Figma URL count as observed evidence. Treat it as provided context until a connector, export, screenshot, or notes are actually inspected.\n\n## Source Screen Contract\n\nFor screenshot or image-based work, extract this before choosing a new layout:\n\n```markdown\n## Source Screen Contract\n- Page type:\n- Primary user job:\n- Visible text:\n- Major regions:\n- Controls and component inventory:\n- Repeated items:\n- Visual hierarchy:\n- Color roles:\n- Typography roles:\n- Density and spacing:\n- Must preserve:\n- May change:\n- Unknown or low-confidence areas:\n```\n\nThe screenshot is the contract for information architecture. Do not replace an input page, landing view, editor, chat surface, form, or simple settings screen with a dashboard, table, chart, sidebar, or operational cockpit unless those elements are visible or explicitly requested.\n\n## DESIGN.md Compatibility\n\nWhen a reusable visual system is needed, create or summarize a `DESIGN.md`-compatible contract. The goal is not to copy a public brand document; it is to give coding agents a durable, versionable design source of truth for this product.\n\nInclude compact metadata when useful: name, version, source, fidelity mode, and token format. Then use these nine headings:\n\n1. `## 1. Visual Theme & Atmosphere`\n2. `## 2. Color`\n3. `## 3. Typography`\n4. `## 4. Spacing & Grid`\n5. `## 5. Layout & Composition`\n6. `## 6. Components`\n7. `## 7. Motion & Interaction`\n8. `## 8. Voice & Brand`\n9. `## 9. Anti-patterns`\n\nKeep each section operational. Prefer constraints the next HTML pass can obey:\n\n- Good: \"single warm amber accent for primary actions; no purple-blue glow\".\n- Weak: \"premium, modern, elegant\".\n\nIf token detail matters, express it in role-based or DTCG-like terms that `ui-design-system` can turn into CSS variables: color roles (`bg`, `surface`, `text`, `accent`), typography roles (`title`, `body`, `label`), spacing scale (`xs` to `lg`), and radius roles (`control`, `panel`).\n\nDo not import public `DESIGN.md` files or brand analyses wholesale. Use them only to understand structure, vocabulary, and quality bar; the actual contract must be grounded in the user's source, repo, and ownership boundaries.\n\n## Reference Boundaries\n\nFor each reference, state:\n\n- `Keep`: transferable qualities such as density, composition rhythm, material feel, type contrast, color temperature, interaction attitude, or component behavior.\n- `Change`: product content, navigation, copy, data model, brand fit, density, or layout changes needed for the user's actual job.\n- `Do not copy`: logos, protected assets, exact layouts, claims, pricing, proprietary UI, unique illustrations, or any source content the user does not own.\n\nWhen references conflict, choose one recommended direction and name the tradeoff. Do not generate five unrelated moodboards unless the user asks for options.\n\n## HTML Implementation Handoff\n\nBefore `ui-design-executor` writes the artifact, hand off:\n\n- Contract name or direction.\n- Source of truth: screenshot, repo tokens, user brief, brand reference, or inferred system.\n- Layout model.\n- Token decisions: color, type, spacing, radius, border, elevation, motion.\n- Component families and required states.\n- Source-to-redesign mapping for every major screenshot region.\n- Responsive requirements.\n- Asset rules and do-not-copy constraints.\n- Acceptance gates the HTML must prove.\n- State\u002Fstory coverage for components that need reusable variants.\n- Fixed decisions that ordinary follow-up edits must preserve, plus any deliberately open axes.\n\nFor standalone drafts, the contract can be embedded as a visible \"Design System\" or \"Handoff\" section only when useful. For app screens, keep the artifact focused on the product experience and mention the contract in the final handoff.\n\n## Quality Gates\n\nBefore rendering or final delivery, check:\n\n- The main artifact type is explicit: app screen, component system, brand board, review page, deck, or other.\n- Observed screenshot structure is preserved or explicitly changed.\n- Inferred content is labeled and does not masquerade as source content.\n- No generic template category overrides the provided reference.\n- Any selected reference pack is named, justified, and rejected patterns are recorded when they could mislead the output.\n- The contract names anti-patterns to avoid.\n- The next HTML pass has enough concrete token and component guidance to execute without guessing.\n- Tokens and component rules are specific enough to produce HTML\u002FCSS, not only mood adjectives.\n- Public reference systems are treated as structure and quality inspiration, not as copied brand identity.\n\n## Output Shape\n\nUse this compact shape in the final handoff when a separate file is not created:\n\n```markdown\n## Design Contract Snapshot\n- Evidence:\n- Design source:\n- Direction:\n- Keep:\n- Change:\n- Do not copy:\n- Tokens:\n- Components:\n- State\u002Fstory coverage:\n- Reference pack, if used:\n- Rejected patterns:\n- Responsive:\n- Anti-patterns:\n- HTML acceptance gates:\n```\n\nIf the user asks for actual files or a long-running design system, write `DESIGN.md` beside the entry file in the canonical artifact directory or inside the target project according to local conventions.\n","# ui-design-contract\n\nUse this skill before rendering when the direction must persist across multiple screens\u002Fcomponents, brand or system work, conflicting references, formal handoff, or a genuinely vague visual system. Ordinary single-screen screenshots and clear briefs use `ui-design-executor`'s compact source\u002Fvisual thesis instead of loading a full durable contract.\n\nThe contract is not extra ceremony. It prevents generic templates, protects the user's reference intent, and gives the HTML artifact a stable design source of truth.\n\nFor standalone work, keep any long-lived `DESIGN.md` inside the canonical directory chosen by `ui-artifact-workspace`. On later revisions, read and update that contract in place only when the accepted design direction actually changes.\n\nWhen the source is a Figma link\u002Fexport, design JSON, PDF, or design-tool screenshot, use `ui-design-source` first so the contract is grounded in inspectable frames, components, variables, and fidelity boundaries.\n\nWhen a visual benchmark or page pattern is needed, pair this skill with `ui-reference-packs` after the contract is drafted. Skip reference packs when the screenshot, repo tokens, or existing design system already provide enough direction. The contract decides what must be preserved; reference packs only help choose style DNA and pattern boundaries.\n\n## When To Create A Contract\n\nCreate a compact durable contract before HTML when any of these are true:\n\n- The screenshot\u002Freference spans multiple screens, must establish a reusable direction, or contains conflicting evidence that a compact executor snapshot cannot resolve.\n- The user says \"make it feel like this\", \"参考这个\", \"做同款但不照抄\", or gives brand\u002Fstyle references.\n- The request spans more than one screen, component family, or visual system.\n- The user asks for a design system, brand board, logo\u002Fidentity board, or implementation handoff.\n- Existing app tokens\u002Fcomponents are unclear and the agent must infer a direction.\n\nIf the user only asks for a tiny local UI tweak with a clear existing system, a full contract can be a short inline \"contract snapshot\".\n\n## Evidence Ledger\n\nEvery contract separates facts from guesses:\n\n- `observed`: visible in the screenshot, HTML, repo, Figma notes, or rendered UI.\n- `provided`: explicitly stated by the user.\n- `inferred`: a reasonable choice made from context.\n- `unknown`: missing information that could change the design.\n\nDo not let inferred items override observed screenshot structure or provided user constraints.\nDo not let an inaccessible Figma URL count as observed evidence. Treat it as provided context until a connector, export, screenshot, or notes are actually inspected.\n\n## Source Screen Contract\n\nFor screenshot or image-based work, extract this before choosing a new layout:\n\n```markdown\n## Source Screen Contract\n- Page type:\n- Primary user job:\n- Visible text:\n- Major regions:\n- Controls and component inventory:\n- Repeated items:\n- Visual hierarchy:\n- Color roles:\n- Typography roles:\n- Density and spacing:\n- Must preserve:\n- May change:\n- Unknown or low-confidence areas:\n```\n\nThe screenshot is the contract for information architecture. Do not replace an input page, landing view, editor, chat surface, form, or simple settings screen with a dashboard, table, chart, sidebar, or operational cockpit unless those elements are visible or explicitly requested.\n\n## DESIGN.md Compatibility\n\nWhen a reusable visual system is needed, create or summarize a `DESIGN.md`-compatible contract. The goal is not to copy a public brand document; it is to give coding agents a durable, versionable design source of truth for this product.\n\nInclude compact metadata when useful: name, version, source, fidelity mode, and token format. Then use these nine headings:\n\n1. `## 1. Visual Theme & Atmosphere`\n2. `## 2. Color`\n3. `## 3. Typography`\n4. `## 4. Spacing & Grid`\n5. `## 5. Layout & Composition`\n6. `## 6. Components`\n7. `## 7. Motion & Interaction`\n8. `## 8. Voice & Brand`\n9. `## 9. Anti-patterns`\n\nKeep each section operational. Prefer constraints the next HTML pass can obey:\n\n- Good: \"single warm amber accent for primary actions; no purple-blue glow\".\n- Weak: \"premium, modern, elegant\".\n\nIf token detail matters, express it in role-based or DTCG-like terms that `ui-design-system` can turn into CSS variables: color roles (`bg`, `surface`, `text`, `accent`), typography roles (`title`, `body`, `label`), spacing scale (`xs` to `lg`), and radius roles (`control`, `panel`).\n\nDo not import public `DESIGN.md` files or brand analyses wholesale. Use them only to understand structure, vocabulary, and quality bar; the actual contract must be grounded in the user's source, repo, and ownership boundaries.\n\n## Reference Boundaries\n\nFor each reference, state:\n\n- `Keep`: transferable qualities such as density, composition rhythm, material feel, type contrast, color temperature, interaction attitude, or component behavior.\n- `Change`: product content, navigation, copy, data model, brand fit, density, or layout changes needed for the user's actual job.\n- `Do not copy`: logos, protected assets, exact layouts, claims, pricing, proprietary UI, unique illustrations, or any source content the user does not own.\n\nWhen references conflict, choose one recommended direction and name the tradeoff. Do not generate five unrelated moodboards unless the user asks for options.\n\n## HTML Implementation Handoff\n\nBefore `ui-design-executor` writes the artifact, hand off:\n\n- Contract name or direction.\n- Source of truth: screenshot, repo tokens, user brief, brand reference, or inferred system.\n- Layout model.\n- Token decisions: color, type, spacing, radius, border, elevation, motion.\n- Component families and required states.\n- Source-to-redesign mapping for every major screenshot region.\n- Responsive requirements.\n- Asset rules and do-not-copy constraints.\n- Acceptance gates the HTML must prove.\n- State\u002Fstory coverage for components that need reusable variants.\n- Fixed decisions that ordinary follow-up edits must preserve, plus any deliberately open axes.\n\nFor standalone drafts, the contract can be embedded as a visible \"Design System\" or \"Handoff\" section only when useful. For app screens, keep the artifact focused on the product experience and mention the contract in the final handoff.\n\n## Quality Gates\n\nBefore rendering or final delivery, check:\n\n- The main artifact type is explicit: app screen, component system, brand board, review page, deck, or other.\n- Observed screenshot structure is preserved or explicitly changed.\n- Inferred content is labeled and does not masquerade as source content.\n- No generic template category overrides the provided reference.\n- Any selected reference pack is named, justified, and rejected patterns are recorded when they could mislead the output.\n- The contract names anti-patterns to avoid.\n- The next HTML pass has enough concrete token and component guidance to execute without guessing.\n- Tokens and component rules are specific enough to produce HTML\u002FCSS, not only mood adjectives.\n- Public reference systems are treated as structure and quality inspiration, not as copied brand identity.\n\n## Output Shape\n\nUse this compact shape in the final handoff when a separate file is not created:\n\n```markdown\n## Design Contract Snapshot\n- Evidence:\n- Design source:\n- Direction:\n- Keep:\n- Change:\n- Do not copy:\n- Tokens:\n- Components:\n- State\u002Fstory coverage:\n- Reference pack, if used:\n- Rejected patterns:\n- Responsive:\n- Anti-patterns:\n- HTML acceptance gates:\n```\n\nIf the user asks for actual files or a long-running design system, write `DESIGN.md` beside the entry file in the canonical artifact directory or inside the target project according to local conventions.\n",{"name":5,"category":23,"ownerAgent":24,"description_en":25,"description_zh":26},"rnd","bcfcb4921dce","Create durable UIDesigner design contracts for multi-screen, brand, long-lived, or conflicting-reference work across DESIGN.md, source-screen rules, tokens, keep\u002Fchange\u002Fdo-not-copy boundaries, and implementation handoff; ordinary single-screen screenshot work stays on the compact executor.","为多屏、品牌、长期复用或参考冲突的 UIDesigner 任务建立持久设计契约，覆盖 DESIGN.md、source screen contract、tokens、keep\u002Fchange\u002Fdo-not-copy 边界和实现交接；普通单屏截图任务使用紧凑执行器即可。","main","6afb98b7a438d4b993ba23f3af1494c862d80378","resources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-contract",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-contract",{"tool":43,"command":44},"bunx","bunx skills add bonc-ai\u002Fcogseed --skill ui-design-contract",{"tool":46,"command":47},"pnpm","pnpm dlx skills add bonc-ai\u002Fcogseed --skill ui-design-contract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-contract\u002FSKILL.md",true,[51,57,61,65,69,73,77],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"artifact.yaml","REFERENCE","参考文档",903,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-contract\u002Fartifact.yaml",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Fevals.json",265,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-contract\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-contract\u002Freferences\u002Fbusiness-ontology.yaml",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fsecurity-manifest.yaml",2485,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-contract\u002Freferences\u002Fsecurity-manifest.yaml",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fskill-spec.yaml",469,"https:\u002F\u002Fgithub.com\u002Fbonc-ai\u002Fcogseed\u002Fblob\u002Fmain\u002Fresources\u002Fbuiltin\u002Fmarketplace\u002Fagents\u002Fbcfcb4921dce\u002Fskills\u002Fui-design-contract\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-contract\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-contract\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",[],[]]