[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G7QRGZAQ59724PSNXHPCAX":3,"skill-same:01M6G7QRGZAQ59724PSNXHPCAX":83},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M6G7QRGZAQ59724PSNXHPCAX","frontend-design-extractor",null,"Extract reusable UI\u002FUX design systems from frontend codebases: design tokens, global styles, components, interaction patterns, and page templates. Use when analyzing any frontend repo (React\u002FVue\u002FAngular\u002FNext\u002FVite\u002Fetc.) to document or migrate UI\u002FUX for reuse across projects. Focus on UI\u002FUX only; explicitly ignore business logic and domain workflows.","kbarbel640-del\u002Fskills","kbarbel640-del","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255315490?v=4","01M6CJPPQGCCESXMG3K7BBGQ5J","01M6CJPPX2PB2BCZERFVM2C2B3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fxsir0\u002Ffrontend-design-extractor\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"design","frontend design","frontend","frontend design extractor","interaction","across","focus","next","patterns","only","projects","migrate","angular","analyzing","ui","ux","design systems","react","components","workflows","2026-11-10 10:12:30",false,"---\nname: frontend-design-extractor\ndescription: \"Extract reusable UI\u002FUX design systems from frontend codebases: design tokens, global styles, components, interaction patterns, and page templates. Use when analyzing any frontend repo (React\u002FVue\u002FAngular\u002FNext\u002FVite\u002Fetc.) to document or migrate UI\u002FUX for reuse across projects. Focus on UI\u002FUX only; explicitly ignore business logic and domain workflows.\"\n---\n\n# Frontend Design Extractor\n\n## Overview\nExtract a reusable UI\u002FUX design spec from a frontend codebase by inventorying UI sources, documenting foundations, cataloging components, and capturing page-level patterns and behaviors. Exclude business logic and domain-specific workflows. Framework-agnostic: adapt to the actual stack in the target repo.\n\n## Quick start\n1) Confirm mode: new project (greenfield) or refactor existing. Clarify that business logic is out of scope.\n2) If existing repo: run `scripts\u002Fscan_ui_sources.sh` to scan the repo root (no directory layout assumptions). It uses common globs + keyword hits, and ignores common build\u002Fcache dirs and extraction output folders by default.\n3) Optionally: `scripts\u002Fscan_ui_sources.sh \u003Crepo_root> [out_file] [extra_glob ...]` or `--root\u002F--out\u002F--ignore` for nonstandard layouts.\n4) Create the output folder (default `.\u002Fui-ux-spec`) via `scripts\u002Fgenerate_output_skeleton.sh` and write all extraction results inside it.\n5) Produce outputs in the default structure (see \"Output structure\").\n\n## Modes (choose one)\n\n### A) Greenfield (from blank)\nGoal: create a reusable UI\u002FUX foundation and starter UI without business logic.\n\n1) Define foundations: tokens (color\u002Ftypography\u002Fspacing\u002Fradius\u002Fshadow\u002Fmotion), global styles, breakpoints, layout shell.\n2) Create a baseline component set: Button, Input, Select, Card, Modal, Table\u002FList, Tabs, Toast, EmptyState.\n3) Create page templates: list\u002Fdetail\u002Fform\u002Fdashboard skeletons with placeholder data.\n4) Provide implementation notes for the target framework (CSS architecture, theming mechanism, file structure).\n5) Optionally run `scripts\u002Fgenerate_output_skeleton.sh [out_root]` to scaffold folders and empty templates. Default output root is `.\u002Fui-ux-spec`.\n\nDeliverables:\n- Design tokens doc + global styles spec\n- Component catalog with variants\u002Fstates\u002Fa11y\n- Page templates with layout rules\n- Engineering constraints (naming, CSS approach, theming)\n\n### B) Refactor existing project\nGoal: extract current UI\u002FUX, normalize tokens, and plan safe, incremental improvements.\n\n1) Inventory UI sources (scan script + manual inspection).\n2) Normalize tokens and map existing styles to them.\n3) Identify high-impact components\u002Fpatterns for first pass.\n4) Plan migration with minimal diffs (wrappers, theme adapters, gradual replacement).\n5) Document behavioral and a11y gaps to fix progressively.\n\nDeliverables:\n- Extracted design spec (same as greenfield)\n- Migration plan (phased, low-risk steps)\n- Component-by-component mapping notes\n\n## Refactor from spec (fixed flow)\nUse this when applying an existing `ui-ux-spec\u002F` to a target project. Always work from a plan and execute step-by-step to avoid missing gaps.\n\n### 0) Understand the target project\n- Identify framework, styling system, component library usage, and entry points.\n- Confirm constraints: UI\u002FUX only, business logic untouched.\n- Keep existing project structure unchanged unless explicitly requested.\n\n### 1) Build the refactor plan (required)\n- Compare spec → current project and list differences by category:\n  - Tokens & global styles\n  - Components (priority order)\n  - Patterns & pages\n  - A11y gaps\n- Do not assume the spec folder structure matches the target project. Map by content, not by paths.\n- Produce a phased plan (Phase 1 tokens, Phase 2 base components, Phase 3 pages, etc.).\n- Do not proceed to edits until the plan is accepted.\n\n### 2) Execute phase by phase\n- Apply changes for the current phase only.\n- Re-check against the spec after each phase.\n- Keep diffs minimal and reversible.\n- Do not restructure folders or move files; update in place.\n\n### 3) Summarize and verify\n- Provide a change list and remaining gaps.\n- Suggest next phase only after current phase is done.\n\n## Refactor prompt templates\nUse one of the templates below to keep requests precise and plan-driven.\n\n### Template A: Standard refactor\n```\nPlease refactor the existing project based on this UI\u002FUX spec:\n- Project path: \u002Fpath\u002Fto\u002Ftarget-project\n- Spec path: \u002Fpath\u002Fto\u002Fui-ux-spec\n- Goal: UI\u002FUX only (tokens, styles, components, layout), do not change business logic\u002FAPIs\n- Scope: start with global styles + base components\n- Constraints: minimal changes, small-step commits, reversible\n- Deliverables: refactor plan + actual code changes + list of impacted files\n```\n\n### Template B: Phased refactor\n```\nPlease refactor UI\u002FUX in phases; only do Phase 1:\n- Project path: \u002Fpath\u002Fto\u002Ftarget-project\n- Spec path: \u002Fpath\u002Fto\u002Fui-ux-spec\n- Phase 1: align tokens + global styles (colors\u002Ftypography\u002Fspacing\u002Fradius\u002Fshadows)\n- Do not change: business logic\u002Frouting\u002FAPIs\n- Deliverables: list of changed files + alignment diff notes\n```\n\n### Template C: Component-level refactor\n```\nPlease align the following components to the spec while keeping business logic unchanged:\n- Project path: \u002Fpath\u002Fto\u002Ftarget-project\n- Spec path: \u002Fpath\u002Fto\u002Fui-ux-spec\n- Component list: Button, Input, Modal, Table\n- Goal: only change styling\u002Fstructure\u002Finteraction details\n- Deliverables: alignment notes per component + code changes\n```\n\n## Workflow\n\n### 0) Scope and constraints\n- Confirm repo root, frameworks, and any design system packages.\n- Confirm desired output format (Markdown by default).\n- Ask for constraints: must-keep brand rules, target platforms, and accessibility level.\n- Reconfirm: exclude business logic, business rules, and domain workflows.\n- Do not assume a specific frontend framework or language; adapt to the project’s stack.\n\n### 1) Source inventory (existing repos only)\n- Do not assume a fixed directory structure; scan results should guide where to read.\n- Run the scan script and inspect results for:\n  - tokens\u002Fthemes, global styles, theme providers\n  - component libraries and local wrappers\n  - Storybook, docs, or visual regression tests\n  - assets and i18n sources\n\n### 2) Foundations (tokens + global styles)\n- Document colors, typography, spacing, radius, shadows, z-index, and motion tokens.\n- Capture reset\u002Fnormalize, body defaults, link\u002Fform defaults, focus-visible, scrollbar.\n\n### 3) Layout & information architecture\n- Document breakpoints, containers, grid rules, navigation structure, and layout shells.\n\n### 4) Component catalog\n- For each component, capture: purpose, structure\u002Fslots, variants, states, interactions, a11y, responsive behavior, motion, and theming hooks.\n- If a third-party library is used, focus on local wrapper components and overrides.\n\n### 5) Page templates & composition rules\n- Extract page skeletons (list\u002Fdetail\u002Fform\u002Fdashboard\u002Fetc.) and module ordering.\n- Capture combined states: loading\u002Fempty\u002Ferror\u002Fpermission\u002Freadonly.\n\n### 6) Behavior & content rules\n- Capture loading and error strategies, validation patterns, undo\u002Foptimistic updates.\n- Capture microcopy conventions and i18n formatting constraints.\n\n### 7) Package outputs\n- Produce at least:\n  - Design tokens doc\n  - Component catalog\n  - Page templates\n- Ensure outputs are written under a dedicated folder (default `ui-ux-spec\u002F`).\n- Use the output structure below unless the user asks for another layout.\n\n## Output structure (default)\nThis structure is a recommended documentation layout. It does not need to match the target project's directory structure, and it can be renamed or relocated (e.g., `docs\u002Fui-ux-spec\u002F`).\n```\nui-ux-spec\u002F\n  01_Foundation\u002F\n  02_Components\u002F\n  03_Patterns\u002F\n  04_Pages\u002F\n  05_A11y\u002F\n  06_Assets\u002F\n  07_Engineering_Constraints\u002F\n```\n\n## Resources\n- `scripts\u002Fscan_ui_sources.sh`: find candidate UI sources in a repo.\n- `scripts\u002Fgenerate_output_skeleton.sh`: create the standard output folders and placeholder templates.\n- `references\u002Fdesign-extraction-checklist.md`: detailed checklist derived from README.\n","# Frontend Design Extractor\n\n## Overview\nExtract a reusable UI\u002FUX design spec from a frontend codebase by inventorying UI sources, documenting foundations, cataloging components, and capturing page-level patterns and behaviors. Exclude business logic and domain-specific workflows. Framework-agnostic: adapt to the actual stack in the target repo.\n\n## Quick start\n1) Confirm mode: new project (greenfield) or refactor existing. Clarify that business logic is out of scope.\n2) If existing repo: run `scripts\u002Fscan_ui_sources.sh` to scan the repo root (no directory layout assumptions). It uses common globs + keyword hits, and ignores common build\u002Fcache dirs and extraction output folders by default.\n3) Optionally: `scripts\u002Fscan_ui_sources.sh \u003Crepo_root> [out_file] [extra_glob ...]` or `--root\u002F--out\u002F--ignore` for nonstandard layouts.\n4) Create the output folder (default `.\u002Fui-ux-spec`) via `scripts\u002Fgenerate_output_skeleton.sh` and write all extraction results inside it.\n5) Produce outputs in the default structure (see \"Output structure\").\n\n## Modes (choose one)\n\n### A) Greenfield (from blank)\nGoal: create a reusable UI\u002FUX foundation and starter UI without business logic.\n\n1) Define foundations: tokens (color\u002Ftypography\u002Fspacing\u002Fradius\u002Fshadow\u002Fmotion), global styles, breakpoints, layout shell.\n2) Create a baseline component set: Button, Input, Select, Card, Modal, Table\u002FList, Tabs, Toast, EmptyState.\n3) Create page templates: list\u002Fdetail\u002Fform\u002Fdashboard skeletons with placeholder data.\n4) Provide implementation notes for the target framework (CSS architecture, theming mechanism, file structure).\n5) Optionally run `scripts\u002Fgenerate_output_skeleton.sh [out_root]` to scaffold folders and empty templates. Default output root is `.\u002Fui-ux-spec`.\n\nDeliverables:\n- Design tokens doc + global styles spec\n- Component catalog with variants\u002Fstates\u002Fa11y\n- Page templates with layout rules\n- Engineering constraints (naming, CSS approach, theming)\n\n### B) Refactor existing project\nGoal: extract current UI\u002FUX, normalize tokens, and plan safe, incremental improvements.\n\n1) Inventory UI sources (scan script + manual inspection).\n2) Normalize tokens and map existing styles to them.\n3) Identify high-impact components\u002Fpatterns for first pass.\n4) Plan migration with minimal diffs (wrappers, theme adapters, gradual replacement).\n5) Document behavioral and a11y gaps to fix progressively.\n\nDeliverables:\n- Extracted design spec (same as greenfield)\n- Migration plan (phased, low-risk steps)\n- Component-by-component mapping notes\n\n## Refactor from spec (fixed flow)\nUse this when applying an existing `ui-ux-spec\u002F` to a target project. Always work from a plan and execute step-by-step to avoid missing gaps.\n\n### 0) Understand the target project\n- Identify framework, styling system, component library usage, and entry points.\n- Confirm constraints: UI\u002FUX only, business logic untouched.\n- Keep existing project structure unchanged unless explicitly requested.\n\n### 1) Build the refactor plan (required)\n- Compare spec → current project and list differences by category:\n  - Tokens & global styles\n  - Components (priority order)\n  - Patterns & pages\n  - A11y gaps\n- Do not assume the spec folder structure matches the target project. Map by content, not by paths.\n- Produce a phased plan (Phase 1 tokens, Phase 2 base components, Phase 3 pages, etc.).\n- Do not proceed to edits until the plan is accepted.\n\n### 2) Execute phase by phase\n- Apply changes for the current phase only.\n- Re-check against the spec after each phase.\n- Keep diffs minimal and reversible.\n- Do not restructure folders or move files; update in place.\n\n### 3) Summarize and verify\n- Provide a change list and remaining gaps.\n- Suggest next phase only after current phase is done.\n\n## Refactor prompt templates\nUse one of the templates below to keep requests precise and plan-driven.\n\n### Template A: Standard refactor\n```\nPlease refactor the existing project based on this UI\u002FUX spec:\n- Project path: \u002Fpath\u002Fto\u002Ftarget-project\n- Spec path: \u002Fpath\u002Fto\u002Fui-ux-spec\n- Goal: UI\u002FUX only (tokens, styles, components, layout), do not change business logic\u002FAPIs\n- Scope: start with global styles + base components\n- Constraints: minimal changes, small-step commits, reversible\n- Deliverables: refactor plan + actual code changes + list of impacted files\n```\n\n### Template B: Phased refactor\n```\nPlease refactor UI\u002FUX in phases; only do Phase 1:\n- Project path: \u002Fpath\u002Fto\u002Ftarget-project\n- Spec path: \u002Fpath\u002Fto\u002Fui-ux-spec\n- Phase 1: align tokens + global styles (colors\u002Ftypography\u002Fspacing\u002Fradius\u002Fshadows)\n- Do not change: business logic\u002Frouting\u002FAPIs\n- Deliverables: list of changed files + alignment diff notes\n```\n\n### Template C: Component-level refactor\n```\nPlease align the following components to the spec while keeping business logic unchanged:\n- Project path: \u002Fpath\u002Fto\u002Ftarget-project\n- Spec path: \u002Fpath\u002Fto\u002Fui-ux-spec\n- Component list: Button, Input, Modal, Table\n- Goal: only change styling\u002Fstructure\u002Finteraction details\n- Deliverables: alignment notes per component + code changes\n```\n\n## Workflow\n\n### 0) Scope and constraints\n- Confirm repo root, frameworks, and any design system packages.\n- Confirm desired output format (Markdown by default).\n- Ask for constraints: must-keep brand rules, target platforms, and accessibility level.\n- Reconfirm: exclude business logic, business rules, and domain workflows.\n- Do not assume a specific frontend framework or language; adapt to the project’s stack.\n\n### 1) Source inventory (existing repos only)\n- Do not assume a fixed directory structure; scan results should guide where to read.\n- Run the scan script and inspect results for:\n  - tokens\u002Fthemes, global styles, theme providers\n  - component libraries and local wrappers\n  - Storybook, docs, or visual regression tests\n  - assets and i18n sources\n\n### 2) Foundations (tokens + global styles)\n- Document colors, typography, spacing, radius, shadows, z-index, and motion tokens.\n- Capture reset\u002Fnormalize, body defaults, link\u002Fform defaults, focus-visible, scrollbar.\n\n### 3) Layout & information architecture\n- Document breakpoints, containers, grid rules, navigation structure, and layout shells.\n\n### 4) Component catalog\n- For each component, capture: purpose, structure\u002Fslots, variants, states, interactions, a11y, responsive behavior, motion, and theming hooks.\n- If a third-party library is used, focus on local wrapper components and overrides.\n\n### 5) Page templates & composition rules\n- Extract page skeletons (list\u002Fdetail\u002Fform\u002Fdashboard\u002Fetc.) and module ordering.\n- Capture combined states: loading\u002Fempty\u002Ferror\u002Fpermission\u002Freadonly.\n\n### 6) Behavior & content rules\n- Capture loading and error strategies, validation patterns, undo\u002Foptimistic updates.\n- Capture microcopy conventions and i18n formatting constraints.\n\n### 7) Package outputs\n- Produce at least:\n  - Design tokens doc\n  - Component catalog\n  - Page templates\n- Ensure outputs are written under a dedicated folder (default `ui-ux-spec\u002F`).\n- Use the output structure below unless the user asks for another layout.\n\n## Output structure (default)\nThis structure is a recommended documentation layout. It does not need to match the target project's directory structure, and it can be renamed or relocated (e.g., `docs\u002Fui-ux-spec\u002F`).\n```\nui-ux-spec\u002F\n  01_Foundation\u002F\n  02_Components\u002F\n  03_Patterns\u002F\n  04_Pages\u002F\n  05_A11y\u002F\n  06_Assets\u002F\n  07_Engineering_Constraints\u002F\n```\n\n## Resources\n- `scripts\u002Fscan_ui_sources.sh`: find candidate UI sources in a repo.\n- `scripts\u002Fgenerate_output_skeleton.sh`: create the standard output folders and placeholder templates.\n- `references\u002Fdesign-extraction-checklist.md`: detailed checklist derived from README.\n",{"name":5,"description":7},"main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fxsir0\u002Ffrontend-design-extractor",0,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del","2026-08-23 22:39:37",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add kbarbel640-del\u002Fskills --skill frontend-design-extractor",{"tool":69,"command":70},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill frontend-design-extractor",{"tool":72,"command":73},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill frontend-design-extractor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fxsir0\u002Ffrontend-design-extractor\u002FSKILL.md",true,[77],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"_meta.json","REFERENCE","参考文档",301,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fxsir0\u002Ffrontend-design-extractor\u002F_meta.json",[84,113,139,160,166,186],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":93,"publishedAt":51},"01M6G8J55967D6281ACMKAKTEQ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",[94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"crowd prompting","prompting","api","with","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":122,"publishedAt":51},"01M6G8J0PKPAYVET6BWE8W4C26","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[123,96,124,125,126,127,128,129,130,131,132,31,133,134,135,136,137,101,138],"dilemm ai","arena","analyze","browser","openclaw agent","create","automation","browser automation","bot","openclaw","strategy","headless","compete","submit","matchmaking","use",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":148,"publishedAt":51},"01M6G8HWAF3K9SW7NP3Z83CPJ6","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, and submit comments. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, or submitting paper reviews via API at http:\u002F\u002F150.158.152.82:8000.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Fweak-accept\u002FSKILL.md",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[149,150,151,152,153,154,155,97,156,136,138,157,96,158,159],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http","via",{"skillNo":161,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":51},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[164],{"categoryNo":146,"categoryName":147,"taxonomyType":20,"taxonomyTypeDesc":21},[152,151,150,149,159,154,155,97,153,136,138,156,157,96,158],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":51},"01M6G8HM95Y64JNVFC2HN4E2BG","git-summary","Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzweack\u002Fgit-summary\u002FSKILL.md",[],[173,174,175,176,177,178,179,180,181,182,183,184,185],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":196,"publishedAt":51},"01M6G8HGEGF05CNEJCGVYFSC4R","agent-constitution","Interact with AgentConstitution governance contracts on Base Sepolia. Check compliance, read rules, log actions, query governance state.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fztsalexey\u002Fagent-constitution\u002FSKILL.md",[192,193],{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":194,"categoryName":195,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000037","律师与法务",[197,198,199,200,97,201,202,56,203,157,204,205,41,206,207,110,208,209,210],"agent constitution","constitution","contracts","tree","query","base","log","check","Rules","compliance","actions","state","governance","github"]