[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7574QJKSYN58GDD9B2HEN8F":3,"skill-same:01M7574QJKSYN58GDD9B2HEN8F":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7574QJKSYN58GDD9B2HEN8F","archi-full",null,"Run or read full-project architecture analysis and summarize structural weaknesses, hotspots, and maintainability risks.","SeemSeam\u002Fagent-roles-spec","SeemSeam","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29205273?v=4","01M7572MDYPSM30Y29C9HRMGK7","01M7572MEGCX02T16BHYV9PBVK",19,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Farchi\u002Fskills\u002Farchi-full\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: archi-full\ndescription: Run or read full-project architecture analysis and summarize structural weaknesses, hotspots, and maintainability risks.\n---\n\n# Archi Full\n\nUse this skill for full-project baseline architecture review.\n\n## Workflow\n\n1. Inspect the available architecture-analysis command shape before assuming\n   flags.\n2. Use `archi-evidence-map` when deciding whether to use Architec\u002FHippo,\n   dependency graphs, architecture tests, Semgrep, CodeQL, or direct review.\n3. Run or read full-project architecture review evidence only when available or\n   requested.\n4. Refresh structural inputs only when the user asks for fresh evidence, the\n   snapshot is stale, or stale evidence is central to the question.\n5. Read project docs, module maps, dependency rules, and representative source\n   paths directly.\n6. Route focused findings to `archi-dependency-topology`,\n   `archi-module-boundaries`, `archi-fitness-functions`,\n   `archi-decision-drift`, `archi-change-impact`, or\n   `archi-distributed-systems` when the baseline needs that method.\n7. Use vendored `improve-codebase-architecture` when the review is looking for\n   deep-module, seam, adapter, leverage, locality, or interface-depth\n   opportunities.\n8. Use vendored `code-review-and-quality` when the baseline needs adjacent\n   correctness, security, performance, or review-quality coverage.\n9. Read `.architec\u002Farchitec-summary.md` first when present.\n10. Use `.architec\u002Farchitec-analysis.json` for exact scores, concerns, signals,\n   hotspots, and artifact paths.\n\n## Output\n\n```text\nScore\n- overall:\n- key reading:\n\nProblems\n- ...\n\nImprovements\n- ...\n\nVerification\n- ...\n```\n\nDo not turn full review into task-goal planning. Use `archi-advice` when the\nuser wants a refactor roadmap.\n\nIf the tool baseline is missing, produce a source-backed baseline with an\nexplicit \"tool evidence unavailable\" note.\n","# Archi Full\n\nUse this skill for full-project baseline architecture review.\n\n## Workflow\n\n1. Inspect the available architecture-analysis command shape before assuming\n   flags.\n2. Use `archi-evidence-map` when deciding whether to use Architec\u002FHippo,\n   dependency graphs, architecture tests, Semgrep, CodeQL, or direct review.\n3. Run or read full-project architecture review evidence only when available or\n   requested.\n4. Refresh structural inputs only when the user asks for fresh evidence, the\n   snapshot is stale, or stale evidence is central to the question.\n5. Read project docs, module maps, dependency rules, and representative source\n   paths directly.\n6. Route focused findings to `archi-dependency-topology`,\n   `archi-module-boundaries`, `archi-fitness-functions`,\n   `archi-decision-drift`, `archi-change-impact`, or\n   `archi-distributed-systems` when the baseline needs that method.\n7. Use vendored `improve-codebase-architecture` when the review is looking for\n   deep-module, seam, adapter, leverage, locality, or interface-depth\n   opportunities.\n8. Use vendored `code-review-and-quality` when the baseline needs adjacent\n   correctness, security, performance, or review-quality coverage.\n9. Read `.architec\u002Farchitec-summary.md` first when present.\n10. Use `.architec\u002Farchitec-analysis.json` for exact scores, concerns, signals,\n   hotspots, and artifact paths.\n\n## Output\n\n```text\nScore\n- overall:\n- key reading:\n\nProblems\n- ...\n\nImprovements\n- ...\n\nVerification\n- ...\n```\n\nDo not turn full review into task-goal planning. Use `archi-advice` when the\nuser wants a refactor roadmap.\n\nIf the tool baseline is missing, produce a source-backed baseline with an\nexplicit \"tool evidence unavailable\" note.\n",{"name":5,"description":7},"main","d07398b0a36ffa994efd970a554dd9596932ed5c","roles\u002Farchi\u002Fskills\u002Farchi-full",2,"https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec","https:\u002F\u002Fgithub.com\u002FSeemSeam","2026-08-14 10:00:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add SeemSeam\u002Fagent-roles-spec --skill archi-full",{"tool":36,"command":37},"bunx","bunx skills add SeemSeam\u002Fagent-roles-spec --skill archi-full",{"tool":39,"command":40},"pnpm","pnpm dlx skills add SeemSeam\u002Fagent-roles-spec --skill archi-full","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Farchi\u002Fskills\u002Farchi-full\u002FSKILL.md",true,[],[45,51,58,65,72,79],{"skillNo":46,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M757C4HNYHR92Z3MDGPW9JSA","example-skill","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Frole-with-skills\u002Fskills\u002Fexample-skill\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M757C2B2YT62JBH98CG1BKWG","su-status","从 docs 人读真相源与 .ccb 协调件读取当前项目、Requirement 或子任务状态。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-status\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M757C0DVFT88AFBXN1PFXH9D","su-revise-breakdown","根据用户反馈重写 Requirement breakdown draft。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-revise-breakdown\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M757BY5XVMPKEK118D782PRM","su-review","审查执行回执、diff 和验证证据，决定通过、返工、replan 或升级用户。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-review\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M757BW1R61F61X7JJF2SSJET","su-resume","从 docs 人读真相源与 .ccb 协调件恢复 paused\u002Fdeferred\u002Fin-progress 主体的上下文。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-resume\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M757BTEAFRRXA9DY3KBRTRNY","su-reconcile","AI-native 自检 docs 人读真相源、.ccb 协调件与 Console 投影漂移，并按审批结果执行修复。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-reconcile\u002FSKILL.md",[],[]]