[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSMA5ZDRB1ND0TPE3FXFY7":3,"skill-same:01M6FSMA5ZDRB1ND0TPE3FXFY7":70},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6FSMA5ZDRB1ND0TPE3FXFY7","context-recovery",null,"Automatically recover working context after session compaction or when continuation is implied but context is missing. Works across Discord, Slack, Telegram, Signal, and other supported channels.","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\u002Fjdrhyne\u002Fcontext-recovery\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34],"recovery","context","context recovery","discord","slack","session","telegram","but","across","missing","compaction","channels","2026-11-10 10:12:30",false,"---\nname: context-recovery\ndescription: Automatically recover working context after session compaction or when continuation is implied but context is missing. Works across Discord, Slack, Telegram, Signal, and other supported channels.\nmetadata: {\"clawdbot\":{\"emoji\":\"?\"}}\n---\n\n# Context Recovery\n\nAutomatically recover working context after session compaction or when continuation is implied but context is missing. Works across Discord, Slack, Telegram, Signal, and other supported channels.\n\n**Use when**: Session starts with truncated context, user references prior work without specifying details, or compaction indicators appear.\n\n---\n\n## Triggers\n\n### Automatic Triggers\n- Session begins with a `\u003Csummary>` tag (compaction detected)\n- User message contains compaction indicators: \"Summary unavailable\", \"context limits\", \"truncated\"\n\n### Manual Triggers\n- User says \"continue\", \"did this happen?\", \"where were we?\", \"what was I working on?\"\n- User references \"the project\", \"the PR\", \"the branch\", \"the issue\" without specifying which\n- User implies prior work exists but context is unclear\n- User asks \"do you remember...?\" or \"we were working on...\"\n\n---\n\n## Execution Protocol\n\n### Step 1: Detect Active Channel\n\nExtract from runtime context:\n- `channel` — discord | slack | telegram | signal | etc.\n- `channelId` — the specific channel\u002Fconversation ID\n- `threadId` — for threaded conversations (Slack, Discord threads)\n\n### Step 2: Fetch Channel History (Adaptive Depth)\n\n**Initial fetch:**\n```\nmessage:read\n  channel: \u003Cdetected-channel>\n  channelId: \u003Cdetected-channel-id>\n  limit: 50\n```\n\n**Adaptive expansion logic:**\n1. Parse timestamps from returned messages\n2. Calculate time span: `newest_timestamp - oldest_timestamp`\n3. If time span \u003C 2 hours AND message count == limit:\n   - Fetch additional 50 messages (using `before` parameter if supported)\n   - Repeat until time span ≥ 2 hours OR total messages ≥ 100\n4. Hard cap: 100 messages maximum (token budget constraint)\n\n**Thread-aware recovery (Slack\u002FDiscord):**\n```\n# If threadId is present, fetch thread messages first\nmessage:read\n  channel: \u003Cdetected-channel>\n  threadId: \u003Cthread-id>\n  limit: 50\n\n# Then fetch parent channel for broader context\nmessage:read\n  channel: \u003Cdetected-channel>\n  channelId: \u003Cparent-channel-id>\n  limit: 30\n```\n\n**Parse for:**\n- Recent user requests (what was asked)\n- Recent assistant responses (what was done)\n- URLs, file paths, branch names, PR numbers\n- Incomplete actions (promises made but not fulfilled)\n- Project identifiers and working directories\n\n### Step 3: Fetch Session Logs (if available)\n\n```bash\n# Find most recent session files for this agent\nSESSION_DIR=$(ls -d ~\u002F.clawdbot-*\u002Fagents\u002F*\u002Fsessions 2>\u002Fdev\u002Fnull | head -1)\nSESSIONS=$(ls -t \"$SESSION_DIR\"\u002F*.jsonl 2>\u002Fdev\u002Fnull | head -3)\n\nfor SESSION in $SESSIONS; do\n  echo \"=== Session: $SESSION ===\"\n  \n  # Extract user requests\n  jq -r 'select(.message.role == \"user\") | .message.content[0].text \u002F\u002F empty' \"$SESSION\" | tail -20\n  \n  # Extract assistant actions (look for tool calls and responses)\n  jq -r 'select(.message.role == \"assistant\") | .message.content[]? | select(.type == \"text\") | .text \u002F\u002F empty' \"$SESSION\" | tail -50\ndone\n```\n\n### Step 4: Check Shared Memory\n\n```bash\n# Extract keywords from channel history (project names, PR numbers, branch names)\n# Search memory for relevant entries\ngrep -ri \"\u003Ckeyword>\" ~\u002Fclawd-*\u002Fmemory\u002F 2>\u002Fdev\u002Fnull | head -10\n\n# Check for recent daily logs\nls -t ~\u002Fclawd-*\u002Fmemory\u002F202*.md 2>\u002Fdev\u002Fnull | head -3 | xargs grep -l \"\u003Ckeyword>\" 2>\u002Fdev\u002Fnull\n```\n\n### Step 5: Synthesize Context\n\nCompile a structured summary:\n\n```markdown\n## Recovered Context\n\n**Channel:** #\u003Cchannel-name> (\u003Cplatform>)\n**Time Range:** \u003Coldest-message> to \u003Cnewest-message>\n**Messages Analyzed:** \u003Ccount>\n\n### Active Project\u002FTask\n- **Repository:** \u003Crepo-name>\n- **Branch:** \u003Cbranch-name>\n- **PR:** #\u003Cnumber> — \u003Ctitle>\n\n### Recent Work Timeline\n1. [\u003Ctimestamp>] \u003Caction\u002Frequest>\n2. [\u003Ctimestamp>] \u003Caction\u002Frequest>\n3. [\u003Ctimestamp>] \u003Caction\u002Frequest>\n\n### Pending\u002FIncomplete Actions\n- ⏳ \"\u003Cquoted incomplete action>\"\n- ⏳ \"\u003Canother incomplete item>\"\n\n### Key References\n| Type | Value |\n|------|-------|\n| PR | #\u003Cnumber> |\n| Branch | \u003Cname> |\n| Files | \u003Cpaths> |\n| URLs | \u003Clinks> |\n\n### Last User Request\n> \"\u003Cquoted request that may not have been completed>\"\n\n### Confidence Level\n- Channel context: \u003Chigh\u002Fmedium\u002Flow>\n- Session logs: \u003Cavailable\u002Fpartial\u002Funavailable>\n- Memory entries: \u003Cfound\u002Fnone>\n```\n\n### Step 6: Cache Recovered Context\n\n**Persist to memory for future reference:**\n\n```bash\n# Write to daily memory file\nMEMORY_FILE=~\u002Fclawd-*\u002Fmemory\u002F$(date +%Y-%m-%d).md\n\ncat >> \"$MEMORY_FILE\" \u003C\u003C EOF\n\n## Context Recovery — $(date +%H:%M)\n\n**Channel:** #\u003Cchannel-name>\n**Recovered context for:** \u003Cproject\u002Ftask summary>\n\n### Key State\n- \u003Cbullet points of critical context>\n\n### Pending Items\n- \u003Cincomplete actions>\n\nEOF\n```\n\nThis ensures context survives future compactions.\n\n### Step 7: Respond with Context\n\nPresent the recovered context, then prompt:\n\n> \"Context recovered. Your last request was [X]. This action [completed\u002Fdid not complete]. Shall I [continue\u002Fretry\u002Fclarify]?\"\n\n---\n\n## Channel-Specific Notes\n\n### Discord\n- Use `channelId` from the incoming message metadata\n- Guild channels have full history access\n- Thread recovery: check for `threadId` in message metadata\n- DMs may have limited history\n\n### Slack\n- Use `channel` parameter with Slack channel ID\n- Thread context requires `threadId` — always check for thread context first\n- Parent channel fetch provides surrounding conversation context\n- May need workspace-level permissions for full history\n\n### Telegram \u002F Signal \u002F Others\n- Same `message:read` interface\n- History depth may vary by platform\n- Group vs. DM context may differ\n\n---\n\n## Constraints\n\n- **MANDATORY:** Execute this protocol before responding \"insufficient data\" or asking clarifying questions when context appears missing\n- Adaptive depth: start with 50, expand to 100 max\n- Time-based goal: capture at least 2 hours of context when possible\n- Session log extraction: last 3 session files maximum\n- Memory cache: append to daily file, do not overwrite\n- If recovery fails, state what was attempted and what data sources were unavailable\n\n---\n\n## Auto-Trigger Detection\n\nAt session start, scan for compaction indicators:\n\n```python\n# Pseudocode for trigger detection\nif message contains \"\u003Csummary>\":\n    trigger_context_recovery()\nelif message contains any of [\"Summary unavailable\", \"context limits\", \"truncated\", \"compacted\"]:\n    trigger_context_recovery()\nelif message matches continuation_patterns:\n    # \"continue\", \"where were we\", \"did this happen\", etc.\n    trigger_context_recovery()\n```\n\n**Do not wait for user to ask** — if compaction is detected, proactively recover and present context.\n\n---\n\n## Example\n\n**Scenario:** Session starts with compaction summary\n\n```\nUser message: \"\u003Csummary>Summary unavailable due to context limits...\u003C\u002Fsummary>\"\nUser message: \"did this happen?\"\n```\n\n**Agent executes:**\n1. Detects compaction via `\u003Csummary>` tag\n2. `message:read channel=discord channelId=1460342116516364533 limit=50`\n3. Calculates time span: 2.5 hours — sufficient, no expansion needed\n4. Parses messages, finds last action: \"Now let me extract the key orchestration decisions...\"\n5. Checks session logs — extracts recent user requests\n6. Writes context summary to `memory\u002FYYYY-MM-DD.md`\n7. Responds:\n\n> \"Context recovered. Your last request was to extract orchestration decisions from Nexus archived sessions for PR #137 (Skills & Agents System). This action did not complete before context was truncated.\n>\n> **Recovered state:**\n> - PR #137: 15,053 additions, 91 files, CONFLICTING merge state\n> - Spec location: `content\u002Fspec-skills-agents-system.md` (2,067 lines)\n> - Nexus sessions: `~\u002F.clawdbot-duke-leto\u002Farchive\u002Fnexus-sessions\u002F` (96 files)\n>\n> Shall I proceed with the extraction?\"\n","# Context Recovery\n\nAutomatically recover working context after session compaction or when continuation is implied but context is missing. Works across Discord, Slack, Telegram, Signal, and other supported channels.\n\n**Use when**: Session starts with truncated context, user references prior work without specifying details, or compaction indicators appear.\n\n---\n\n## Triggers\n\n### Automatic Triggers\n- Session begins with a `\u003Csummary>` tag (compaction detected)\n- User message contains compaction indicators: \"Summary unavailable\", \"context limits\", \"truncated\"\n\n### Manual Triggers\n- User says \"continue\", \"did this happen?\", \"where were we?\", \"what was I working on?\"\n- User references \"the project\", \"the PR\", \"the branch\", \"the issue\" without specifying which\n- User implies prior work exists but context is unclear\n- User asks \"do you remember...?\" or \"we were working on...\"\n\n---\n\n## Execution Protocol\n\n### Step 1: Detect Active Channel\n\nExtract from runtime context:\n- `channel` — discord | slack | telegram | signal | etc.\n- `channelId` — the specific channel\u002Fconversation ID\n- `threadId` — for threaded conversations (Slack, Discord threads)\n\n### Step 2: Fetch Channel History (Adaptive Depth)\n\n**Initial fetch:**\n```\nmessage:read\n  channel: \u003Cdetected-channel>\n  channelId: \u003Cdetected-channel-id>\n  limit: 50\n```\n\n**Adaptive expansion logic:**\n1. Parse timestamps from returned messages\n2. Calculate time span: `newest_timestamp - oldest_timestamp`\n3. If time span \u003C 2 hours AND message count == limit:\n   - Fetch additional 50 messages (using `before` parameter if supported)\n   - Repeat until time span ≥ 2 hours OR total messages ≥ 100\n4. Hard cap: 100 messages maximum (token budget constraint)\n\n**Thread-aware recovery (Slack\u002FDiscord):**\n```\n# If threadId is present, fetch thread messages first\nmessage:read\n  channel: \u003Cdetected-channel>\n  threadId: \u003Cthread-id>\n  limit: 50\n\n# Then fetch parent channel for broader context\nmessage:read\n  channel: \u003Cdetected-channel>\n  channelId: \u003Cparent-channel-id>\n  limit: 30\n```\n\n**Parse for:**\n- Recent user requests (what was asked)\n- Recent assistant responses (what was done)\n- URLs, file paths, branch names, PR numbers\n- Incomplete actions (promises made but not fulfilled)\n- Project identifiers and working directories\n\n### Step 3: Fetch Session Logs (if available)\n\n```bash\n# Find most recent session files for this agent\nSESSION_DIR=$(ls -d ~\u002F.clawdbot-*\u002Fagents\u002F*\u002Fsessions 2>\u002Fdev\u002Fnull | head -1)\nSESSIONS=$(ls -t \"$SESSION_DIR\"\u002F*.jsonl 2>\u002Fdev\u002Fnull | head -3)\n\nfor SESSION in $SESSIONS; do\n  echo \"=== Session: $SESSION ===\"\n  \n  # Extract user requests\n  jq -r 'select(.message.role == \"user\") | .message.content[0].text \u002F\u002F empty' \"$SESSION\" | tail -20\n  \n  # Extract assistant actions (look for tool calls and responses)\n  jq -r 'select(.message.role == \"assistant\") | .message.content[]? | select(.type == \"text\") | .text \u002F\u002F empty' \"$SESSION\" | tail -50\ndone\n```\n\n### Step 4: Check Shared Memory\n\n```bash\n# Extract keywords from channel history (project names, PR numbers, branch names)\n# Search memory for relevant entries\ngrep -ri \"\u003Ckeyword>\" ~\u002Fclawd-*\u002Fmemory\u002F 2>\u002Fdev\u002Fnull | head -10\n\n# Check for recent daily logs\nls -t ~\u002Fclawd-*\u002Fmemory\u002F202*.md 2>\u002Fdev\u002Fnull | head -3 | xargs grep -l \"\u003Ckeyword>\" 2>\u002Fdev\u002Fnull\n```\n\n### Step 5: Synthesize Context\n\nCompile a structured summary:\n\n```markdown\n## Recovered Context\n\n**Channel:** #\u003Cchannel-name> (\u003Cplatform>)\n**Time Range:** \u003Coldest-message> to \u003Cnewest-message>\n**Messages Analyzed:** \u003Ccount>\n\n### Active Project\u002FTask\n- **Repository:** \u003Crepo-name>\n- **Branch:** \u003Cbranch-name>\n- **PR:** #\u003Cnumber> — \u003Ctitle>\n\n### Recent Work Timeline\n1. [\u003Ctimestamp>] \u003Caction\u002Frequest>\n2. [\u003Ctimestamp>] \u003Caction\u002Frequest>\n3. [\u003Ctimestamp>] \u003Caction\u002Frequest>\n\n### Pending\u002FIncomplete Actions\n- ⏳ \"\u003Cquoted incomplete action>\"\n- ⏳ \"\u003Canother incomplete item>\"\n\n### Key References\n| Type | Value |\n|------|-------|\n| PR | #\u003Cnumber> |\n| Branch | \u003Cname> |\n| Files | \u003Cpaths> |\n| URLs | \u003Clinks> |\n\n### Last User Request\n> \"\u003Cquoted request that may not have been completed>\"\n\n### Confidence Level\n- Channel context: \u003Chigh\u002Fmedium\u002Flow>\n- Session logs: \u003Cavailable\u002Fpartial\u002Funavailable>\n- Memory entries: \u003Cfound\u002Fnone>\n```\n\n### Step 6: Cache Recovered Context\n\n**Persist to memory for future reference:**\n\n```bash\n# Write to daily memory file\nMEMORY_FILE=~\u002Fclawd-*\u002Fmemory\u002F$(date +%Y-%m-%d).md\n\ncat >> \"$MEMORY_FILE\" \u003C\u003C EOF\n\n## Context Recovery — $(date +%H:%M)\n\n**Channel:** #\u003Cchannel-name>\n**Recovered context for:** \u003Cproject\u002Ftask summary>\n\n### Key State\n- \u003Cbullet points of critical context>\n\n### Pending Items\n- \u003Cincomplete actions>\n\nEOF\n```\n\nThis ensures context survives future compactions.\n\n### Step 7: Respond with Context\n\nPresent the recovered context, then prompt:\n\n> \"Context recovered. Your last request was [X]. This action [completed\u002Fdid not complete]. Shall I [continue\u002Fretry\u002Fclarify]?\"\n\n---\n\n## Channel-Specific Notes\n\n### Discord\n- Use `channelId` from the incoming message metadata\n- Guild channels have full history access\n- Thread recovery: check for `threadId` in message metadata\n- DMs may have limited history\n\n### Slack\n- Use `channel` parameter with Slack channel ID\n- Thread context requires `threadId` — always check for thread context first\n- Parent channel fetch provides surrounding conversation context\n- May need workspace-level permissions for full history\n\n### Telegram \u002F Signal \u002F Others\n- Same `message:read` interface\n- History depth may vary by platform\n- Group vs. DM context may differ\n\n---\n\n## Constraints\n\n- **MANDATORY:** Execute this protocol before responding \"insufficient data\" or asking clarifying questions when context appears missing\n- Adaptive depth: start with 50, expand to 100 max\n- Time-based goal: capture at least 2 hours of context when possible\n- Session log extraction: last 3 session files maximum\n- Memory cache: append to daily file, do not overwrite\n- If recovery fails, state what was attempted and what data sources were unavailable\n\n---\n\n## Auto-Trigger Detection\n\nAt session start, scan for compaction indicators:\n\n```python\n# Pseudocode for trigger detection\nif message contains \"\u003Csummary>\":\n    trigger_context_recovery()\nelif message contains any of [\"Summary unavailable\", \"context limits\", \"truncated\", \"compacted\"]:\n    trigger_context_recovery()\nelif message matches continuation_patterns:\n    # \"continue\", \"where were we\", \"did this happen\", etc.\n    trigger_context_recovery()\n```\n\n**Do not wait for user to ask** — if compaction is detected, proactively recover and present context.\n\n---\n\n## Example\n\n**Scenario:** Session starts with compaction summary\n\n```\nUser message: \"\u003Csummary>Summary unavailable due to context limits...\u003C\u002Fsummary>\"\nUser message: \"did this happen?\"\n```\n\n**Agent executes:**\n1. Detects compaction via `\u003Csummary>` tag\n2. `message:read channel=discord channelId=1460342116516364533 limit=50`\n3. Calculates time span: 2.5 hours — sufficient, no expansion needed\n4. Parses messages, finds last action: \"Now let me extract the key orchestration decisions...\"\n5. Checks session logs — extracts recent user requests\n6. Writes context summary to `memory\u002FYYYY-MM-DD.md`\n7. Responds:\n\n> \"Context recovered. Your last request was to extract orchestration decisions from Nexus archived sessions for PR #137 (Skills & Agents System). This action did not complete before context was truncated.\n>\n> **Recovered state:**\n> - PR #137: 15,053 additions, 91 files, CONFLICTING merge state\n> - Spec location: `content\u002Fspec-skills-agents-system.md` (2,067 lines)\n> - Nexus sessions: `~\u002F.clawdbot-duke-leto\u002Farchive\u002Fnexus-sessions\u002F` (96 files)\n>\n> Shall I proceed with the extraction?\"\n",{"name":5,"metadata":40,"description":7},{"clawdbot":41},{"emoji":42},"?","main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fjdrhyne\u002Fcontext-recovery",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add kbarbel640-del\u002Fskills --skill context-recovery",{"tool":56,"command":57},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill context-recovery",{"tool":59,"command":60},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill context-recovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjdrhyne\u002Fcontext-recovery\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"_meta.json","REFERENCE","参考文档",463,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fjdrhyne\u002Fcontext-recovery\u002F_meta.json",[71,102,129,150,156,176],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":35},"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",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"crowd prompting","prompting","api","with","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":111,"publishedAt":35},"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",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[112,85,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,90,128],"dilemm ai","arena","analyze","browser","openclaw agent","create","automation","browser automation","bot","openclaw","design","strategy","headless","compete","submit","matchmaking","use",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":138,"publishedAt":35},"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",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[139,140,141,142,143,144,145,86,146,126,128,147,85,148,149],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http","via",{"skillNo":151,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":35},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[154],{"categoryNo":136,"categoryName":137,"taxonomyType":20,"taxonomyTypeDesc":21},[142,141,140,139,149,144,145,86,143,126,128,146,147,85,148],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":35},"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",[],[163,164,165,166,167,168,169,170,171,172,173,174,175],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":186,"publishedAt":35},"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",[182,183],{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":184,"categoryName":185,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000037","律师与法务",[187,188,189,190,86,191,192,43,193,147,194,195,196,197,198,99,199,200,201],"agent constitution","constitution","contracts","tree","query","base","log","check","Rules","projects","compliance","actions","state","governance","github"]