[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FV8PCF1EMCBH4PAT3NR23Z":3,"skill-same:01M6FV8PCF1EMCBH4PAT3NR23Z":79},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6FV8PCF1EMCBH4PAT3NR23Z","warden-studio",null,"Use Warden Studio (studio.wardenprotocol.org) via browser automation to register\u002Fpublish a Community Agent to the Warden Agent Hub. Use when you need to (1) log in to Studio, (2) create\u002Fsubmit an agent listing, (3) configure API URL\u002Fauth, skills, avatar, and billing model, (4) pay registration + gas, and (5) verify the agent appears in Studio and in Warden's Agent Hub. Designed for safe, repeatable publishing with explicit confirmation gates.","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\u002Fkryptopaid\u002Fwarden-studio-deploy\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"warden studio","studio","warden","log","pay","you","URL","billing","submit","community","browser automation","gas","confirmation","model","configure","api","publish","browser","create","auth","2026-11-10 10:12:30",false,"---\nname: warden-studio\ndescription: Use Warden Studio (studio.wardenprotocol.org) via browser automation to register\u002Fpublish a Community Agent to the Warden Agent Hub. Use when you need to (1) log in to Studio, (2) create\u002Fsubmit an agent listing, (3) configure API URL\u002Fauth, skills, avatar, and billing model, (4) pay registration + gas, and (5) verify the agent appears in Studio and in Warden's Agent Hub. Designed for safe, repeatable publishing with explicit confirmation gates.\n---\n\n# Warden Studio\n\nAutomate publishing a Community Agent in **Warden Studio** through a safe, repeatable workflow that other agents can follow.\n\n## Safety & constraints (non-negotiable)\n\n- Never request or store seed phrases \u002F private keys.\n- Never ask the user to paste secrets into chat. If an API key must be entered, instruct the user to paste it directly into the Studio UI field.\n- Treat publishing\u002Fonchain registration as **high-risk**: confirm network, fees, and what is being signed before any wallet confirmation.\n- Prefer read-only validation (checking forms, status, preview) unless the user explicitly authorizes execution (e.g., \"yes, publish\" \u002F \"yes, execute\").\n- Do not reveal any private info (local files, credentials, IPs, internal logs).\n- Public comms: do not claim any affiliation or relationship unless it is publicly disclosed and the user explicitly asks you to state it.\n\n## What this skill does\n\nTypical outcomes:\n\n- Log into `https:\u002F\u002Fstudio.wardenprotocol.org`\n- Create a new Agent submission\u002Flisting\n- Provide:\n  - API URL (service endpoint)\n  - API key \u002F auth method (if required)\n  - Name, description, skills, avatar\n  - Billing model (free vs paid per inference, in USDC)\n- Pay registration fee + gas (if prompted by the UI)\n- Verify the agent shows up in Studio and becomes discoverable in Warden's Agent Hub (Community tab), when applicable.\n\n## Workflow (UI automation)\n\n### 0) Preconditions\n\n1. A Chromium browser is available (Chrome\u002FBrave\u002FEdge\u002FChromium). (Firefox not supported.)\n2. User can log in to Warden Studio (email\u002FSSO\u002F2FA completed).\n3. The agent is already deployed somewhere and reachable via HTTPS (no UI required):\n   - stable API base URL\n   - (optional) API key or token if the endpoint is protected\n4. Funding is ready for registration (if required by the flow):\n   - USDC on Base for the registration fee (confirm the fee in the UI)\n   - ETH on Base for gas\n\nIf any of the above is missing, stop and ask the user to do that step.\n\n### 1) Open + stabilize Studio\n\n- Open: `https:\u002F\u002Fstudio.wardenprotocol.org`\n- Wait for the landing\u002Fdashboard to load.\n- Take a snapshot and identify:\n  - logged-in user \u002F account handle\n  - any \"Agents\" list\u002Ftable or \"Submit \u002F Create agent\" entry point\n  - network\u002Fpayment cues (e.g., Base, USDC, wallet connection state)\n\nIf Studio is gated by login, stop and ask the user to complete login in the UI.\n\n### 2) Read-only checks (default)\n\nUse these first to prevent failed submissions:\n\n- Confirm the agent endpoint is reachable:\n  - the URL is HTTPS\n  - no obvious typos\n  - (if a \"Test connection\" exists) run it\n- Validate required metadata is prepared:\n  - agent name (short)\n  - description (clear, non-misleading)\n  - skills list (concise + accurate)\n  - avatar image ready (square recommended)\n- Check billing\u002Fmonetization options:\n  - free vs per-inference (USDC)\n  - expected fees shown by the UI\n\n### 3) Draft the submission (no publishing yet)\n\n**Direct create page (recommended):** `https:\u002F\u002Fstudio.wardenprotocol.org\u002Fagents\u002Fcreate`\n\n#### Current “Register Agent” form fields\n\nFill the form top-to-bottom to match the UI sections:\n\n1. **API details**\n   - **API URL*** — your agent’s HTTPS endpoint\n   - **API Key** — if your endpoint requires a key  \n     *Never paste secrets into chat; enter them directly into the Studio field.*\n\n   The UI may also show helper links like **“Build an agent using LangGraph”** \u002F **“How it works”**.\n\n2. **Info**\n   - **Agent Name***  \n   - **Select agent skills*** — choose the relevant skill tags\n   - **Describe the key features of the agent*** — short, accurate capability summary\n\n3. **Agent avatar**\n   - Paste link to add an agent avatar → **Image link** (URL)\n\n4. **Billing model**\n   - Choose how the agent charges users: **Per inference** or **Free**\n   - If **Per inference**: **Cost in USDC*** (numeric)\n\n5. **Agent Preview**\n   - **Agent name**\n   - **Short description about your agent** (max **100** characters)\n\n6. Final action: **Register agent**\n\nNavigate to the agent submission flow (or go directly to `https:\u002F\u002Fstudio.wardenprotocol.org\u002Fagents\u002Fcreate`), then fill fields in a deterministic order:\n\n1. **Identity**\n   - Agent name\n   - Short tagline (if any)\n   - Category (if any)\n\n2. **Capabilities**\n   - Description\n   - Skills (keywords and\u002For bullet list)\n   - Links (docs, GitHub, website) if requested\n\n3. **Integration**\n   - API URL (service endpoint)\n   - Auth:\n     - API key field (if present), or\n     - header\u002Ftoken configuration (if present)\n\n4. **Branding**\n   - Upload avatar\n   - Optional banner\u002Fimages (if supported)\n\n5. **Monetization**\n   - Choose billing model (free vs paid\u002Fper inference) if supported\n   - Review any platform\u002Fregistration fee disclosures\n\nAt the end of drafting, stop and show the user a **Submission Summary**:\n\n- Agent name + description (1–2 lines)\n- Skills list\n- API URL (domain + path)\n- Auth method (mask any key\u002Ftoken)\n- Billing model + any displayed fees\n\n### 4) Publish \u002F register (requires explicit approval)\n\n**Execution gate:** Do not click the final \"Publish \u002F Register \u002F Submit\" button unless the user explicitly replies with **\"yes, publish\"** or **\"yes, execute\"** (or an unambiguous equivalent).\n\nBefore finalizing, summarize:\n\n- What action will happen (publish\u002Fregister agent listing)\n- What network\u002Fpayment is involved (e.g., Base; registration fee + gas, as shown in the UI)\n- Any costs shown in the UI (USDC amount + estimated gas)\n- What could go wrong:\n  - wrong endpoint \u002F downtime → failed validation\n  - wrong billing settings\n  - wallet prompt on wrong network\n  - unintended fee payment\n\nThen proceed with the final click and wallet confirmation step (user signs in their wallet).\n\n### 5) Post-publish verification\n\nAfter publishing\u002Fregistration:\n\n- Confirm status in Studio:\n  - \"Submitted\", \"Pending\", \"Published\", etc.\n- Capture any agent identifier or link shown (listing URL).\n- Check the agent appears in Studio's Agents list.\n- If the UI mentions distribution:\n  - verify it appears in Warden Agent Hub → Community tab (when available)\n- Record any errors verbatim and capture screenshots of:\n  - validation errors\n  - payment failures\n  - endpoint\u002Fauth failures\n\n## Troubleshooting playbook\n\nCommon failures and fixes:\n\n- **Endpoint validation fails**\n  - Check HTTPS, trailing slashes, versioned paths\n  - Confirm the agent server is live and not geo-blocked\n  - If auth required, verify the correct key\u002Ftoken was entered in UI (never paste it into chat)\n\n- **Wallet\u002Fnetwork mismatch**\n  - Ensure wallet is on the correct network (e.g., Base) if Studio requires it\n\n- **Insufficient funds**\n  - Add USDC on Base for fee and ETH on Base for gas, then retry\n\n## Building a wrapper skill other agents can use\n\nWhen asked to \"create a skill that lets other agents publish via Warden Studio\":\n\n1. Record the minimal repeatable workflow (URLs + UI landmarks) in `references\u002Fwarden-studio-ui-notes.md`.\n2. Keep `SKILL.md` stable and general; put volatile UI selectors, screenshots, and clickpaths in references.\n3. Only add deterministic scripts if they reduce errors (e.g., a submission summary checklist formatter).\n\n## References\n\n- Read `references\u002Fwarden-studio-ui-notes.md` for the latest Studio navigation map, observed fields, and publishing quirks.\n","# Warden Studio\n\nAutomate publishing a Community Agent in **Warden Studio** through a safe, repeatable workflow that other agents can follow.\n\n## Safety & constraints (non-negotiable)\n\n- Never request or store seed phrases \u002F private keys.\n- Never ask the user to paste secrets into chat. If an API key must be entered, instruct the user to paste it directly into the Studio UI field.\n- Treat publishing\u002Fonchain registration as **high-risk**: confirm network, fees, and what is being signed before any wallet confirmation.\n- Prefer read-only validation (checking forms, status, preview) unless the user explicitly authorizes execution (e.g., \"yes, publish\" \u002F \"yes, execute\").\n- Do not reveal any private info (local files, credentials, IPs, internal logs).\n- Public comms: do not claim any affiliation or relationship unless it is publicly disclosed and the user explicitly asks you to state it.\n\n## What this skill does\n\nTypical outcomes:\n\n- Log into `https:\u002F\u002Fstudio.wardenprotocol.org`\n- Create a new Agent submission\u002Flisting\n- Provide:\n  - API URL (service endpoint)\n  - API key \u002F auth method (if required)\n  - Name, description, skills, avatar\n  - Billing model (free vs paid per inference, in USDC)\n- Pay registration fee + gas (if prompted by the UI)\n- Verify the agent shows up in Studio and becomes discoverable in Warden's Agent Hub (Community tab), when applicable.\n\n## Workflow (UI automation)\n\n### 0) Preconditions\n\n1. A Chromium browser is available (Chrome\u002FBrave\u002FEdge\u002FChromium). (Firefox not supported.)\n2. User can log in to Warden Studio (email\u002FSSO\u002F2FA completed).\n3. The agent is already deployed somewhere and reachable via HTTPS (no UI required):\n   - stable API base URL\n   - (optional) API key or token if the endpoint is protected\n4. Funding is ready for registration (if required by the flow):\n   - USDC on Base for the registration fee (confirm the fee in the UI)\n   - ETH on Base for gas\n\nIf any of the above is missing, stop and ask the user to do that step.\n\n### 1) Open + stabilize Studio\n\n- Open: `https:\u002F\u002Fstudio.wardenprotocol.org`\n- Wait for the landing\u002Fdashboard to load.\n- Take a snapshot and identify:\n  - logged-in user \u002F account handle\n  - any \"Agents\" list\u002Ftable or \"Submit \u002F Create agent\" entry point\n  - network\u002Fpayment cues (e.g., Base, USDC, wallet connection state)\n\nIf Studio is gated by login, stop and ask the user to complete login in the UI.\n\n### 2) Read-only checks (default)\n\nUse these first to prevent failed submissions:\n\n- Confirm the agent endpoint is reachable:\n  - the URL is HTTPS\n  - no obvious typos\n  - (if a \"Test connection\" exists) run it\n- Validate required metadata is prepared:\n  - agent name (short)\n  - description (clear, non-misleading)\n  - skills list (concise + accurate)\n  - avatar image ready (square recommended)\n- Check billing\u002Fmonetization options:\n  - free vs per-inference (USDC)\n  - expected fees shown by the UI\n\n### 3) Draft the submission (no publishing yet)\n\n**Direct create page (recommended):** `https:\u002F\u002Fstudio.wardenprotocol.org\u002Fagents\u002Fcreate`\n\n#### Current “Register Agent” form fields\n\nFill the form top-to-bottom to match the UI sections:\n\n1. **API details**\n   - **API URL*** — your agent’s HTTPS endpoint\n   - **API Key** — if your endpoint requires a key  \n     *Never paste secrets into chat; enter them directly into the Studio field.*\n\n   The UI may also show helper links like **“Build an agent using LangGraph”** \u002F **“How it works”**.\n\n2. **Info**\n   - **Agent Name***  \n   - **Select agent skills*** — choose the relevant skill tags\n   - **Describe the key features of the agent*** — short, accurate capability summary\n\n3. **Agent avatar**\n   - Paste link to add an agent avatar → **Image link** (URL)\n\n4. **Billing model**\n   - Choose how the agent charges users: **Per inference** or **Free**\n   - If **Per inference**: **Cost in USDC*** (numeric)\n\n5. **Agent Preview**\n   - **Agent name**\n   - **Short description about your agent** (max **100** characters)\n\n6. Final action: **Register agent**\n\nNavigate to the agent submission flow (or go directly to `https:\u002F\u002Fstudio.wardenprotocol.org\u002Fagents\u002Fcreate`), then fill fields in a deterministic order:\n\n1. **Identity**\n   - Agent name\n   - Short tagline (if any)\n   - Category (if any)\n\n2. **Capabilities**\n   - Description\n   - Skills (keywords and\u002For bullet list)\n   - Links (docs, GitHub, website) if requested\n\n3. **Integration**\n   - API URL (service endpoint)\n   - Auth:\n     - API key field (if present), or\n     - header\u002Ftoken configuration (if present)\n\n4. **Branding**\n   - Upload avatar\n   - Optional banner\u002Fimages (if supported)\n\n5. **Monetization**\n   - Choose billing model (free vs paid\u002Fper inference) if supported\n   - Review any platform\u002Fregistration fee disclosures\n\nAt the end of drafting, stop and show the user a **Submission Summary**:\n\n- Agent name + description (1–2 lines)\n- Skills list\n- API URL (domain + path)\n- Auth method (mask any key\u002Ftoken)\n- Billing model + any displayed fees\n\n### 4) Publish \u002F register (requires explicit approval)\n\n**Execution gate:** Do not click the final \"Publish \u002F Register \u002F Submit\" button unless the user explicitly replies with **\"yes, publish\"** or **\"yes, execute\"** (or an unambiguous equivalent).\n\nBefore finalizing, summarize:\n\n- What action will happen (publish\u002Fregister agent listing)\n- What network\u002Fpayment is involved (e.g., Base; registration fee + gas, as shown in the UI)\n- Any costs shown in the UI (USDC amount + estimated gas)\n- What could go wrong:\n  - wrong endpoint \u002F downtime → failed validation\n  - wrong billing settings\n  - wallet prompt on wrong network\n  - unintended fee payment\n\nThen proceed with the final click and wallet confirmation step (user signs in their wallet).\n\n### 5) Post-publish verification\n\nAfter publishing\u002Fregistration:\n\n- Confirm status in Studio:\n  - \"Submitted\", \"Pending\", \"Published\", etc.\n- Capture any agent identifier or link shown (listing URL).\n- Check the agent appears in Studio's Agents list.\n- If the UI mentions distribution:\n  - verify it appears in Warden Agent Hub → Community tab (when available)\n- Record any errors verbatim and capture screenshots of:\n  - validation errors\n  - payment failures\n  - endpoint\u002Fauth failures\n\n## Troubleshooting playbook\n\nCommon failures and fixes:\n\n- **Endpoint validation fails**\n  - Check HTTPS, trailing slashes, versioned paths\n  - Confirm the agent server is live and not geo-blocked\n  - If auth required, verify the correct key\u002Ftoken was entered in UI (never paste it into chat)\n\n- **Wallet\u002Fnetwork mismatch**\n  - Ensure wallet is on the correct network (e.g., Base) if Studio requires it\n\n- **Insufficient funds**\n  - Add USDC on Base for fee and ETH on Base for gas, then retry\n\n## Building a wrapper skill other agents can use\n\nWhen asked to \"create a skill that lets other agents publish via Warden Studio\":\n\n1. Record the minimal repeatable workflow (URLs + UI landmarks) in `references\u002Fwarden-studio-ui-notes.md`.\n2. Keep `SKILL.md` stable and general; put volatile UI selectors, screenshots, and clickpaths in references.\n3. Only add deterministic scripts if they reduce errors (e.g., a submission summary checklist formatter).\n\n## References\n\n- Read `references\u002Fwarden-studio-ui-notes.md` for the latest Studio navigation map, observed fields, and publishing quirks.\n",{"name":5,"description":7},"main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fkryptopaid\u002Fwarden-studio-deploy",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add kbarbel640-del\u002Fskills --skill warden-studio",{"tool":61,"command":62},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill warden-studio",{"tool":64,"command":65},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill warden-studio","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fkryptopaid\u002Fwarden-studio-deploy\u002FSKILL.md",true,[69,75],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"_meta.json","REFERENCE","参考文档",305,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fkryptopaid\u002Fwarden-studio-deploy\u002F_meta.json",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fwarden-studio-ui-notes.md",2263,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fkryptopaid\u002Fwarden-studio-deploy\u002Freferences\u002Fwarden-studio-ui-notes.md",[80,110,131,152,158,178],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":91,"publishedAt":43},"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",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[92,93,38,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"crowd prompting","prompting","with","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":43},"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",[116],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[118,38,119,120,40,121,41,122,33,123,124,125,126,127,128,31,129,98,130],"dilemm ai","arena","analyze","openclaw agent","automation","bot","openclaw","design","strategy","headless","compete","matchmaking","use",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":43},"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",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[141,142,143,144,145,146,147,94,148,31,130,149,38,150,151],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http","via",{"skillNo":153,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":43},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[156],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},[144,143,142,141,151,146,147,94,145,31,130,148,149,38,150],{"skillNo":159,"name":160,"nameZh":6,"description":161,"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":164,"publishedAt":43},"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",[],[165,166,167,168,169,170,171,172,173,174,175,176,177],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":188,"publishedAt":43},"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",[184,185],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":186,"categoryName":187,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000037","律师与法务",[189,190,191,192,94,193,194,48,26,149,195,196,197,198,199,107,200,201,202],"agent constitution","constitution","contracts","tree","query","base","check","Rules","projects","compliance","actions","state","governance","github"]