[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75GKPJ0W3K3ERTGF2FNTP7Y":3,"skill-same:01M75GKPJ0W3K3ERTGF2FNTP7Y":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75GKPJ0W3K3ERTGF2FNTP7Y","agent-autonomy-primitives",null,"Build long-running autonomous agent loops using ClawVault primitives (tasks, projects, memory types, templates, heartbeats). Use when setting up agent autonomy, creating task-driven execution loops, customizing primitive schemas, wiring heartbeat-based work queues, or teaching an agent to manage its own backlog. Also use when adapting primitives to an existing agent setup or designing multi-agent collaboration through shared vaults.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fg9pedro\u002Fagent-autonomy-primitives\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: agent-autonomy-primitives\ndescription: Build long-running autonomous agent loops using ClawVault primitives (tasks, projects, memory types, templates, heartbeats). Use when setting up agent autonomy, creating task-driven execution loops, customizing primitive schemas, wiring heartbeat-based work queues, or teaching an agent to manage its own backlog. Also use when adapting primitives to an existing agent setup or designing multi-agent collaboration through shared vaults.\n---\n\n# Agent Autonomy Primitives\n\nTurn any AI agent into a self-directing worker using five composable primitives: **typed memory**, **task files**, **project grouping**, **template schemas**, and **heartbeat loops**.\n\n## Prerequisites\n\n```bash\nnpm install -g clawvault\nclawvault init\n```\n\n## The Five Primitives\n\n### 1. Typed Memory\n\nEvery memory has a type. The type determines where it lives and how it's retrieved.\n\n| Type | Directory | When to Use |\n|------|-----------|-------------|\n| `decision` | `decisions\u002F` | Recording a choice with rationale |\n| `lesson` | `lessons\u002F` | Something learned from experience |\n| `person` | `people\u002F` | Contact info, relationship context |\n| `commitment` | `commitments\u002F` | Promise made, deliverable owed |\n| `preference` | `preferences\u002F` | How someone likes things done |\n| `fact` | `inbox\u002F` | Raw information to file later |\n| `project` | `projects\u002F` | Workstream with goals and status |\n\nStore with type:\n```bash\nclawvault remember decision \"Chose Resend over SendGrid\" --content \"Lower cost, better DX, webhook support\"\nclawvault remember lesson \"LLMs rewrite keywords during compression\" --content \"Always post-process with regex\"\n```\n\n**Rule:** If you know WHAT KIND of thing it is, use the right command. Dumping everything into daily notes defeats retrieval later.\n\n### 2. Task Primitives\n\nA task is a markdown file with YAML frontmatter in `tasks\u002F`:\n\n```yaml\n---\nstatus: open\npriority: high\nowner: your-agent-name\nproject: my-project\ndue: 2026-03-01\ntags: [infrastructure, deploy]\nestimate: 2h\n---\n# Deploy API to production\n\n## Context\nServer provisioned. Need Dockerfile fix.\n\n## Next Steps\n- Fix binding to 0.0.0.0\n- Add health endpoint\n- Push and verify\n```\n\nCreate tasks:\n```bash\nclawvault task add \"Deploy API to production\" \\\n  --priority high \\\n  --owner my-agent \\\n  --project my-project \\\n  --due 2026-03-01 \\\n  --tags \"infrastructure,deploy\"\n```\n\nUpdate status:\n```bash\nclawvault task update deploy-api-to-production --status in-progress\nclawvault task done deploy-api-to-production --reason \"Deployed, health check passing\"\n```\n\n**Statuses:** `open` → `in-progress` → `done` (or `blocked`)\n**Priorities:** `critical` > `high` > `medium` > `low`\n\n### 3. Project Grouping\n\nProjects group related tasks with metadata:\n\n```bash\nclawvault project add \"Outbound Engine\" \\\n  --owner pedro \\\n  --client versatly \\\n  --tags \"gtm,sales\" \\\n  --deadline 2026-03-15\n```\n\nTasks reference projects via the `project` field. Filter tasks by project:\n```bash\nclawvault task list --project outbound-engine\n```\n\n### 4. Template Schemas\n\nTemplates are YAML schema definitions that control what fields exist on every primitive. They live in `templates\u002F` in your vault.\n\nSee [references\u002Ftemplate-customization.md](references\u002Ftemplate-customization.md) for full customization guide.\n\nKey points:\n- Vault templates override builtins — drop a `task.md` in `templates\u002F` to change the schema\n- Add fields (e.g., `sprint`, `effort`, `client`) by editing the template\n- Remove fields you don't need\n- Change defaults (e.g., default priority = `high`)\n- Validation is advisory — warns but never blocks\n\n### 5. Heartbeat Loop\n\nThe heartbeat is the autonomy mechanism. Wire it into your agent's periodic wake cycle.\n\n**Every heartbeat (e.g., every 30 minutes):**\n\n```\n1. clawvault task list --owner \u003Cagent-name> --status open\n2. Sort by: priority (critical first), then due date (soonest first)\n3. Pick the highest-impact task executable RIGHT NOW\n4. Execute it\n5. On completion: clawvault task done \u003Cslug> --reason \"what was done\"\n6. On blocker: clawvault task update \u003Cslug> --status blocked --blocked-by \"reason\"\n7. If new work discovered: clawvault task add \"new task\" --priority \u003Cp> --project \u003Cproj>\n8. If lesson learned: clawvault remember lesson \"what happened\"\n9. Go back to sleep\n```\n\n**Implementation for OpenClaw agents:**\n\nAdd to your `HEARTBEAT.md`:\n```markdown\n## Task-Driven Autonomy\n\nEvery heartbeat:\n1. `clawvault task list --owner \u003Cyour-name> --status open` → your work queue\n2. Sort by priority + due date\n3. Pick highest-impact task you can execute NOW\n4. Work it. Update status. Mark done. Report.\n5. Check for tasks due within 24h — those get priority\n```\n\nFor cron-based agents, schedule a recurring job:\n```\nSchedule: every 30 minutes\nAction: Read task queue, pick highest priority, execute, report\n```\n\n## Composing Primitives into Autonomy\n\nThe power is in composition, not any single primitive:\n\n```\nWake → Read memory → Check tasks → Execute → Learn → Update memory → Sleep\n         ↑                                      |\n         └──────────────────────────────────────┘\n```\n\nEach cycle compounds:\n- **Memory** feeds context into task execution (decisions, lessons, preferences inform how work gets done)\n- **Task execution** generates new memories (lessons learned, decisions made, commitments created)\n- **Lessons** improve future execution (mistakes aren't repeated)\n- **Wiki-links** (`[[entity-name]]`) build a knowledge graph across all files\n- **Projects** provide scope boundaries so the agent doesn't drift\n\n## Adapting to Your Setup\n\nSee [references\u002Fadaptation-guide.md](references\u002Fadaptation-guide.md) for detailed patterns on:\n- Wiring primitives into existing agent frameworks (OpenClaw, LangChain, CrewAI, custom)\n- Choosing which primitives to adopt (start minimal, add as needed)\n- Multi-agent collaboration through shared vaults\n- Migrating from other memory systems\n\n## Quick Start: Zero to Autonomous in 5 Minutes\n\n```bash\n# 1. Install and init\nnpm install -g clawvault\nclawvault init\n\n# 2. Create your first project\nclawvault project add \"My Project\" --owner my-agent\n\n# 3. Create tasks\nclawvault task add \"Set up monitoring\" --priority high --owner my-agent --project my-project\nclawvault task add \"Write API docs\" --priority medium --owner my-agent --project my-project\n\n# 4. Wire into heartbeat (add to HEARTBEAT.md or cron)\n# \"Every 30min: clawvault task list --owner my-agent --status open, pick top task, execute\"\n\n# 5. Start working\nclawvault task update set-up-monitoring --status in-progress\n# ... do the work ...\nclawvault task done set-up-monitoring --reason \"Prometheus + Grafana configured\"\nclawvault remember lesson \"UptimeRobot free tier only checks every 5min\" --content \"Use Better Stack for \u003C1min checks\"\n```\n\n## Anti-Patterns\n\n| Don't | Do Instead |\n|-------|-----------|\n| Store everything in one big memory file | Use typed memory — decisions\u002F, lessons\u002F, people\u002F |\n| Create tasks without owner\u002Fproject | Always set `--owner` and `--project` |\n| Ask \"what should I work on?\" | Read your task queue and decide |\n| Forget lessons after learning them | `clawvault remember lesson` immediately |\n| Skip marking tasks done | Always `task done --reason` — the ledger tracks transitions |\n| Create tasks for vague ideas | Put ideas in `backlog\u002F`, promote to `tasks\u002F` when ready |\n| Modify template schemas constantly | Stabilize schemas early — field renames break existing files |\n\n## Obsidian Integration\n\nBecause everything is markdown + YAML frontmatter, Obsidian renders your agent's workspace as a human-readable dashboard:\n\n- **Kanban board** — open `all-tasks.base` in Obsidian Bases, drag between status columns\n- **Blocked view** — `blocked.base` shows what needs human input\n- **By owner** — `by-owner.base` shows what each agent is working on\n- **By project** — `by-project.base` scopes views per workstream\n\nThe same file is both the agent's data structure AND the human's UI. No sync layer needed.\n","# Agent Autonomy Primitives\n\nTurn any AI agent into a self-directing worker using five composable primitives: **typed memory**, **task files**, **project grouping**, **template schemas**, and **heartbeat loops**.\n\n## Prerequisites\n\n```bash\nnpm install -g clawvault\nclawvault init\n```\n\n## The Five Primitives\n\n### 1. Typed Memory\n\nEvery memory has a type. The type determines where it lives and how it's retrieved.\n\n| Type | Directory | When to Use |\n|------|-----------|-------------|\n| `decision` | `decisions\u002F` | Recording a choice with rationale |\n| `lesson` | `lessons\u002F` | Something learned from experience |\n| `person` | `people\u002F` | Contact info, relationship context |\n| `commitment` | `commitments\u002F` | Promise made, deliverable owed |\n| `preference` | `preferences\u002F` | How someone likes things done |\n| `fact` | `inbox\u002F` | Raw information to file later |\n| `project` | `projects\u002F` | Workstream with goals and status |\n\nStore with type:\n```bash\nclawvault remember decision \"Chose Resend over SendGrid\" --content \"Lower cost, better DX, webhook support\"\nclawvault remember lesson \"LLMs rewrite keywords during compression\" --content \"Always post-process with regex\"\n```\n\n**Rule:** If you know WHAT KIND of thing it is, use the right command. Dumping everything into daily notes defeats retrieval later.\n\n### 2. Task Primitives\n\nA task is a markdown file with YAML frontmatter in `tasks\u002F`:\n\n```yaml\n---\nstatus: open\npriority: high\nowner: your-agent-name\nproject: my-project\ndue: 2026-03-01\ntags: [infrastructure, deploy]\nestimate: 2h\n---\n# Deploy API to production\n\n## Context\nServer provisioned. Need Dockerfile fix.\n\n## Next Steps\n- Fix binding to 0.0.0.0\n- Add health endpoint\n- Push and verify\n```\n\nCreate tasks:\n```bash\nclawvault task add \"Deploy API to production\" \\\n  --priority high \\\n  --owner my-agent \\\n  --project my-project \\\n  --due 2026-03-01 \\\n  --tags \"infrastructure,deploy\"\n```\n\nUpdate status:\n```bash\nclawvault task update deploy-api-to-production --status in-progress\nclawvault task done deploy-api-to-production --reason \"Deployed, health check passing\"\n```\n\n**Statuses:** `open` → `in-progress` → `done` (or `blocked`)\n**Priorities:** `critical` > `high` > `medium` > `low`\n\n### 3. Project Grouping\n\nProjects group related tasks with metadata:\n\n```bash\nclawvault project add \"Outbound Engine\" \\\n  --owner pedro \\\n  --client versatly \\\n  --tags \"gtm,sales\" \\\n  --deadline 2026-03-15\n```\n\nTasks reference projects via the `project` field. Filter tasks by project:\n```bash\nclawvault task list --project outbound-engine\n```\n\n### 4. Template Schemas\n\nTemplates are YAML schema definitions that control what fields exist on every primitive. They live in `templates\u002F` in your vault.\n\nSee [references\u002Ftemplate-customization.md](references\u002Ftemplate-customization.md) for full customization guide.\n\nKey points:\n- Vault templates override builtins — drop a `task.md` in `templates\u002F` to change the schema\n- Add fields (e.g., `sprint`, `effort`, `client`) by editing the template\n- Remove fields you don't need\n- Change defaults (e.g., default priority = `high`)\n- Validation is advisory — warns but never blocks\n\n### 5. Heartbeat Loop\n\nThe heartbeat is the autonomy mechanism. Wire it into your agent's periodic wake cycle.\n\n**Every heartbeat (e.g., every 30 minutes):**\n\n```\n1. clawvault task list --owner \u003Cagent-name> --status open\n2. Sort by: priority (critical first), then due date (soonest first)\n3. Pick the highest-impact task executable RIGHT NOW\n4. Execute it\n5. On completion: clawvault task done \u003Cslug> --reason \"what was done\"\n6. On blocker: clawvault task update \u003Cslug> --status blocked --blocked-by \"reason\"\n7. If new work discovered: clawvault task add \"new task\" --priority \u003Cp> --project \u003Cproj>\n8. If lesson learned: clawvault remember lesson \"what happened\"\n9. Go back to sleep\n```\n\n**Implementation for OpenClaw agents:**\n\nAdd to your `HEARTBEAT.md`:\n```markdown\n## Task-Driven Autonomy\n\nEvery heartbeat:\n1. `clawvault task list --owner \u003Cyour-name> --status open` → your work queue\n2. Sort by priority + due date\n3. Pick highest-impact task you can execute NOW\n4. Work it. Update status. Mark done. Report.\n5. Check for tasks due within 24h — those get priority\n```\n\nFor cron-based agents, schedule a recurring job:\n```\nSchedule: every 30 minutes\nAction: Read task queue, pick highest priority, execute, report\n```\n\n## Composing Primitives into Autonomy\n\nThe power is in composition, not any single primitive:\n\n```\nWake → Read memory → Check tasks → Execute → Learn → Update memory → Sleep\n         ↑                                      |\n         └──────────────────────────────────────┘\n```\n\nEach cycle compounds:\n- **Memory** feeds context into task execution (decisions, lessons, preferences inform how work gets done)\n- **Task execution** generates new memories (lessons learned, decisions made, commitments created)\n- **Lessons** improve future execution (mistakes aren't repeated)\n- **Wiki-links** (`[[entity-name]]`) build a knowledge graph across all files\n- **Projects** provide scope boundaries so the agent doesn't drift\n\n## Adapting to Your Setup\n\nSee [references\u002Fadaptation-guide.md](references\u002Fadaptation-guide.md) for detailed patterns on:\n- Wiring primitives into existing agent frameworks (OpenClaw, LangChain, CrewAI, custom)\n- Choosing which primitives to adopt (start minimal, add as needed)\n- Multi-agent collaboration through shared vaults\n- Migrating from other memory systems\n\n## Quick Start: Zero to Autonomous in 5 Minutes\n\n```bash\n# 1. Install and init\nnpm install -g clawvault\nclawvault init\n\n# 2. Create your first project\nclawvault project add \"My Project\" --owner my-agent\n\n# 3. Create tasks\nclawvault task add \"Set up monitoring\" --priority high --owner my-agent --project my-project\nclawvault task add \"Write API docs\" --priority medium --owner my-agent --project my-project\n\n# 4. Wire into heartbeat (add to HEARTBEAT.md or cron)\n# \"Every 30min: clawvault task list --owner my-agent --status open, pick top task, execute\"\n\n# 5. Start working\nclawvault task update set-up-monitoring --status in-progress\n# ... do the work ...\nclawvault task done set-up-monitoring --reason \"Prometheus + Grafana configured\"\nclawvault remember lesson \"UptimeRobot free tier only checks every 5min\" --content \"Use Better Stack for \u003C1min checks\"\n```\n\n## Anti-Patterns\n\n| Don't | Do Instead |\n|-------|-----------|\n| Store everything in one big memory file | Use typed memory — decisions\u002F, lessons\u002F, people\u002F |\n| Create tasks without owner\u002Fproject | Always set `--owner` and `--project` |\n| Ask \"what should I work on?\" | Read your task queue and decide |\n| Forget lessons after learning them | `clawvault remember lesson` immediately |\n| Skip marking tasks done | Always `task done --reason` — the ledger tracks transitions |\n| Create tasks for vague ideas | Put ideas in `backlog\u002F`, promote to `tasks\u002F` when ready |\n| Modify template schemas constantly | Stabilize schemas early — field renames break existing files |\n\n## Obsidian Integration\n\nBecause everything is markdown + YAML frontmatter, Obsidian renders your agent's workspace as a human-readable dashboard:\n\n- **Kanban board** — open `all-tasks.base` in Obsidian Bases, drag between status columns\n- **Blocked view** — `blocked.base` shows what needs human input\n- **By owner** — `by-owner.base` shows what each agent is working on\n- **By project** — `by-project.base` scopes views per workstream\n\nThe same file is both the agent's data structure AND the human's UI. No sync layer needed.\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fg9pedro\u002Fagent-autonomy-primitives",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill agent-autonomy-primitives",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill agent-autonomy-primitives",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill agent-autonomy-primitives","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fg9pedro\u002Fagent-autonomy-primitives\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","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\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","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\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]