[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76Z4337ZR17TSMRXQAPWHZ7":3,"skill-same:01M76Z4337ZR17TSMRXQAPWHZ7":57},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M76Z4337ZR17TSMRXQAPWHZ7","sentry",null,"Add observability to your OpenClaw instance — errors, logs, and traces sent to Sentry. Set up monitoring with the Sentry plugin, then investigate issues with the `sentry` CLI.","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\u002Fsergical\u002Fsentry-observability\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: sentry\ndescription: \"Add observability to your OpenClaw instance — errors, logs, and traces sent to Sentry. Set up monitoring with the Sentry plugin, then investigate issues with the `sentry` CLI.\"\nmetadata:\n  {\n    \"openclaw\":\n      {\n        \"emoji\": \"🐛\",\n        \"requires\": { \"bins\": [\"sentry\"] },\n        \"install\":\n          [\n            {\n              \"id\": \"npm\",\n              \"kind\": \"npm\",\n              \"package\": \"sentry\",\n              \"global\": true,\n              \"bins\": [\"sentry\"],\n              \"label\": \"Install Sentry CLI (npm)\",\n            },\n          ],\n      },\n  }\n---\n\n# Sentry — OpenClaw Observability\n\nSee what your OpenClaw instance is doing: errors, structured logs, and performance traces — all in Sentry.\n\nTwo halves: **setup** (get telemetry flowing) and **investigation** (query it with the CLI).\n\n---\n\n## Setup\n\n### 1. Authenticate\n\n```bash\nsentry auth login\n```\n\nOAuth device flow — follow the browser prompt. Credentials stored in `~\u002F.sentry\u002Fcli.db`.\n\nAlternatives (one-liners):\n- `sentry auth login --token \u003CTOKEN>` — paste an auth token directly\n- `SENTRY_AUTH_TOKEN=\u003Ctoken>` — env var, useful in CI\n\n### 2. Create a Project\n\nCreate a dedicated Sentry project for your OpenClaw instance:\n\n```bash\nsentry api \u002Fteams\u002F\u003Corg>\u002F\u003Cteam>\u002Fprojects\u002F \\\n  --method POST \\\n  --field name=\"my-openclaw\" \\\n  --field platform=node\n```\n\nDon't know your org\u002Fteam slugs? List them:\n\n```bash\nsentry api \u002Forganizations\u002F                          # list orgs\nsentry api \u002Forganizations\u002F\u003Corg>\u002Fteams\u002F              # list teams in org\n```\n\n### 3. Get the DSN\n\n```bash\nsentry project view \u003Corg>\u002Fmy-openclaw --json | jq -r '.dsn'\n```\n\nOr via the keys endpoint:\n\n```bash\nsentry api \u002Fprojects\u002F\u003Corg>\u002Fmy-openclaw\u002Fkeys\u002F | jq '.[0].dsn.public'\n```\n\n### 4. Configure OpenClaw\n\nAdd the DSN to your `openclaw.json`:\n\n```json\n{\n  \"plugins\": {\n    \"entries\": {\n      \"sentry\": {\n        \"enabled\": true,\n        \"config\": {\n          \"dsn\": \"https:\u002F\u002FexamplePublicKey@o0.ingest.sentry.io\u002F0\",\n          \"enableLogs\": true\n        }\n      }\n    }\n  }\n}\n```\n\n> **Note:** Config goes under `plugins.entries.sentry.config`, not directly under `sentry`.\n\nThen install the Sentry plugin. See `references\u002Fplugin-setup.md` for the full plugin implementation using `@sentry\u002Fnode`.\n\n> **Log buffer gotcha:** Sentry's structured logs buffer up to 100 items before auto-flushing. For low-volume services like OpenClaw, logs may sit in the buffer for a long time. The plugin should call `_INTERNAL_flushLogsBuffer(client)` periodically (e.g. every 30s) and before `Sentry.flush()` on shutdown. See `references\u002Fplugin-setup.md` for the implementation.\n\n### 5. Verify\n\nRestart your OpenClaw gateway, then check Sentry for incoming events:\n\n```bash\nsentry issue list \u003Corg>\u002Fmy-openclaw --limit 5\n```\n\n---\n\n## Investigation\n\nOnce telemetry is flowing, use the CLI to query your OpenClaw's errors, traces, and events.\n\n### List Issues\n\n```bash\nsentry issue list \u003Corg>\u002F\u003Cproject>\nsentry issue list \u003Corg>\u002F\u003Cproject> --query \"is:unresolved\" --sort freq --limit 20\nsentry issue list \u003Corg>\u002F                              # all projects in org\n```\n\n### View an Issue\n\n```bash\nsentry issue view \u003Cshort-id>                          # e.g. MY-OPENCLAW-42\nsentry issue view \u003Cshort-id> --json                   # structured output\n```\n\n### AI Root Cause Analysis\n\n```bash\nsentry issue explain \u003Cissue-id>                       # Seer analyzes the root cause\nsentry issue explain \u003Cissue-id> --force               # force fresh analysis\nsentry issue plan \u003Cissue-id>                          # generate a fix plan (run explain first)\n```\n\n### Structured Logs\n\n```bash\nsentry log list \u003Corg>\u002F\u003Cproject>                       # last 100 logs\nsentry log list \u003Corg>\u002F\u003Cproject> --limit 50            # last 50\nsentry log list \u003Corg>\u002F\u003Cproject> -q 'level:error'      # filter by level\nsentry log list \u003Corg>\u002F\u003Cproject> -q 'database'         # filter by message\nsentry log list \u003Corg>\u002F\u003Cproject> -f                    # stream in real-time (2s poll)\nsentry log list \u003Corg>\u002F\u003Cproject> -f 5                  # stream with 5s poll\nsentry log list \u003Corg>\u002F\u003Cproject> --json                # structured output\n```\n\nView a specific log entry:\n\n```bash\nsentry log view \u003Clog-id>                              # 32-char hex ID\nsentry log view \u003Clog-id> --json\nsentry log view \u003Clog-id> --web                        # open in browser\n```\n\n### Inspect Events\n\n```bash\nsentry event view \u003Cevent-id>                          # full stack trace + context\nsentry event view \u003Cevent-id> --json\n```\n\n### Direct API Calls\n\n```bash\nsentry api \u002Fprojects\u002F\u003Corg>\u002F\u003Cproject>\u002Fissues\u002F --paginate\nsentry api \u002Fissues\u002F\u003Cid>\u002F --method PUT --field status=resolved\nsentry api \u002Fissues\u002F\u003Cid>\u002F --method PUT --field assignedTo=\"user@example.com\"\n```\n\n### Workflow: Investigate an Error\n\n1. `sentry issue list \u003Corg>\u002F\u003Cproject> --query \"is:unresolved\" --sort date --limit 5`\n2. `sentry issue view \u003Cshort-id>` — context, affected users, timeline\n3. `sentry issue explain \u003Cissue-id>` — AI root cause analysis\n4. `sentry issue plan \u003Cissue-id>` — concrete fix steps\n5. Fix → `sentry api \u002Fissues\u002F\u003Cid>\u002F --method PUT --field status=resolved`\n\n---\n\n## Reference\n\n- Full CLI commands: `references\u002Fcli-commands.md`\n- Plugin implementation: `references\u002Fplugin-setup.md`\n- CLI docs: https:\u002F\u002Fcli.sentry.dev\n- Sentry API: https:\u002F\u002Fdocs.sentry.io\u002Fapi\u002F\n- Node SDK: https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fguides\u002Fnode\u002F\n","# Sentry — OpenClaw Observability\n\nSee what your OpenClaw instance is doing: errors, structured logs, and performance traces — all in Sentry.\n\nTwo halves: **setup** (get telemetry flowing) and **investigation** (query it with the CLI).\n\n---\n\n## Setup\n\n### 1. Authenticate\n\n```bash\nsentry auth login\n```\n\nOAuth device flow — follow the browser prompt. Credentials stored in `~\u002F.sentry\u002Fcli.db`.\n\nAlternatives (one-liners):\n- `sentry auth login --token \u003CTOKEN>` — paste an auth token directly\n- `SENTRY_AUTH_TOKEN=\u003Ctoken>` — env var, useful in CI\n\n### 2. Create a Project\n\nCreate a dedicated Sentry project for your OpenClaw instance:\n\n```bash\nsentry api \u002Fteams\u002F\u003Corg>\u002F\u003Cteam>\u002Fprojects\u002F \\\n  --method POST \\\n  --field name=\"my-openclaw\" \\\n  --field platform=node\n```\n\nDon't know your org\u002Fteam slugs? List them:\n\n```bash\nsentry api \u002Forganizations\u002F                          # list orgs\nsentry api \u002Forganizations\u002F\u003Corg>\u002Fteams\u002F              # list teams in org\n```\n\n### 3. Get the DSN\n\n```bash\nsentry project view \u003Corg>\u002Fmy-openclaw --json | jq -r '.dsn'\n```\n\nOr via the keys endpoint:\n\n```bash\nsentry api \u002Fprojects\u002F\u003Corg>\u002Fmy-openclaw\u002Fkeys\u002F | jq '.[0].dsn.public'\n```\n\n### 4. Configure OpenClaw\n\nAdd the DSN to your `openclaw.json`:\n\n```json\n{\n  \"plugins\": {\n    \"entries\": {\n      \"sentry\": {\n        \"enabled\": true,\n        \"config\": {\n          \"dsn\": \"https:\u002F\u002FexamplePublicKey@o0.ingest.sentry.io\u002F0\",\n          \"enableLogs\": true\n        }\n      }\n    }\n  }\n}\n```\n\n> **Note:** Config goes under `plugins.entries.sentry.config`, not directly under `sentry`.\n\nThen install the Sentry plugin. See `references\u002Fplugin-setup.md` for the full plugin implementation using `@sentry\u002Fnode`.\n\n> **Log buffer gotcha:** Sentry's structured logs buffer up to 100 items before auto-flushing. For low-volume services like OpenClaw, logs may sit in the buffer for a long time. The plugin should call `_INTERNAL_flushLogsBuffer(client)` periodically (e.g. every 30s) and before `Sentry.flush()` on shutdown. See `references\u002Fplugin-setup.md` for the implementation.\n\n### 5. Verify\n\nRestart your OpenClaw gateway, then check Sentry for incoming events:\n\n```bash\nsentry issue list \u003Corg>\u002Fmy-openclaw --limit 5\n```\n\n---\n\n## Investigation\n\nOnce telemetry is flowing, use the CLI to query your OpenClaw's errors, traces, and events.\n\n### List Issues\n\n```bash\nsentry issue list \u003Corg>\u002F\u003Cproject>\nsentry issue list \u003Corg>\u002F\u003Cproject> --query \"is:unresolved\" --sort freq --limit 20\nsentry issue list \u003Corg>\u002F                              # all projects in org\n```\n\n### View an Issue\n\n```bash\nsentry issue view \u003Cshort-id>                          # e.g. MY-OPENCLAW-42\nsentry issue view \u003Cshort-id> --json                   # structured output\n```\n\n### AI Root Cause Analysis\n\n```bash\nsentry issue explain \u003Cissue-id>                       # Seer analyzes the root cause\nsentry issue explain \u003Cissue-id> --force               # force fresh analysis\nsentry issue plan \u003Cissue-id>                          # generate a fix plan (run explain first)\n```\n\n### Structured Logs\n\n```bash\nsentry log list \u003Corg>\u002F\u003Cproject>                       # last 100 logs\nsentry log list \u003Corg>\u002F\u003Cproject> --limit 50            # last 50\nsentry log list \u003Corg>\u002F\u003Cproject> -q 'level:error'      # filter by level\nsentry log list \u003Corg>\u002F\u003Cproject> -q 'database'         # filter by message\nsentry log list \u003Corg>\u002F\u003Cproject> -f                    # stream in real-time (2s poll)\nsentry log list \u003Corg>\u002F\u003Cproject> -f 5                  # stream with 5s poll\nsentry log list \u003Corg>\u002F\u003Cproject> --json                # structured output\n```\n\nView a specific log entry:\n\n```bash\nsentry log view \u003Clog-id>                              # 32-char hex ID\nsentry log view \u003Clog-id> --json\nsentry log view \u003Clog-id> --web                        # open in browser\n```\n\n### Inspect Events\n\n```bash\nsentry event view \u003Cevent-id>                          # full stack trace + context\nsentry event view \u003Cevent-id> --json\n```\n\n### Direct API Calls\n\n```bash\nsentry api \u002Fprojects\u002F\u003Corg>\u002F\u003Cproject>\u002Fissues\u002F --paginate\nsentry api \u002Fissues\u002F\u003Cid>\u002F --method PUT --field status=resolved\nsentry api \u002Fissues\u002F\u003Cid>\u002F --method PUT --field assignedTo=\"user@example.com\"\n```\n\n### Workflow: Investigate an Error\n\n1. `sentry issue list \u003Corg>\u002F\u003Cproject> --query \"is:unresolved\" --sort date --limit 5`\n2. `sentry issue view \u003Cshort-id>` — context, affected users, timeline\n3. `sentry issue explain \u003Cissue-id>` — AI root cause analysis\n4. `sentry issue plan \u003Cissue-id>` — concrete fix steps\n5. Fix → `sentry api \u002Fissues\u002F\u003Cid>\u002F --method PUT --field status=resolved`\n\n---\n\n## Reference\n\n- Full CLI commands: `references\u002Fcli-commands.md`\n- Plugin implementation: `references\u002Fplugin-setup.md`\n- CLI docs: https:\u002F\u002Fcli.sentry.dev\n- Sentry API: https:\u002F\u002Fdocs.sentry.io\u002Fapi\u002F\n- Node SDK: https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fguides\u002Fnode\u002F\n",{"name":5,"metadata":24,"description":7},{"openclaw":25},{"emoji":26,"install":27,"requires":33},"🐛",[28],{"id":29,"bins":30,"kind":29,"label":31,"global":32,"package":5},"npm",[5],"Install Sentry CLI (npm)",true,{"bins":34},[5],"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fsergical\u002Fsentry-observability",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":45,"prompt":55,"zipAvailable":32},[46,49,52],{"tool":47,"command":48},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill sentry",{"tool":50,"command":51},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill sentry",{"tool":53,"command":54},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill sentry","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsergical\u002Fsentry-observability\u002FSKILL.md",[],[58,66,73,80,87,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":65},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":65},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":65},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":65},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":65},"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",[],[]]