[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75K0ETYZDPZ5659MFSRKQK5":3,"skill-same:01M75K0ETYZDPZ5659MFSRKQK5":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},"01M75K0ETYZDPZ5659MFSRKQK5","release-tracker",null,"Track GitHub repository releases and generate prioritized summaries. Supports multiple repos, custom priority keywords, and delivery to Discord (forum posts or channel messages), Telegram, Slack, or plain text. Use when setting up automated release monitoring, checking for new versions of any GitHub repo, or generating changelog summaries. Triggers on track releases, monitor repo, check for updates, new version, release notes, changelog summary, setting up cron jobs for release monitoring, or any request to watch GitHub repos for new releases.","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\u002Fjo9900\u002Frelease-tracker\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: release-tracker\ndescription: >\n  Track GitHub repository releases and generate prioritized summaries.\n  Supports multiple repos, custom priority keywords, and delivery to\n  Discord (forum posts or channel messages), Telegram, Slack, or plain text.\n  Use when setting up automated release monitoring, checking for new versions\n  of any GitHub repo, or generating changelog summaries. Triggers on track\n  releases, monitor repo, check for updates, new version, release notes,\n  changelog summary, setting up cron jobs for release monitoring, or any\n  request to watch GitHub repos for new releases.\n---\n\n# Release Tracker\n\nMonitor one or more GitHub repositories for new releases, generate prioritized summaries, and deliver them to configured channels.\n\n## Prerequisites\n\n- `gh` CLI installed and authenticated (`gh auth status`)\n- For Discord delivery: Discord channel configured in OpenClaw\n\n## Quick Start\n\n### Single Repo Setup\n\nSet up tracking for one repo with a cron job:\n\n```\n1. Create a config file at \u003Cworkspace>\u002Frelease-tracker.json (see Configuration)\n2. Create a cron job (isolated, daily) that runs the check\n3. The cron reads config, checks GitHub, compares versions, posts if new\n```\n\n### Multi-Repo Setup\n\nAdd multiple repos to the `repos` array in config. Each repo has independent version tracking and priority rules.\n\n## Configuration\n\nStore config at `\u003Cworkspace>\u002Frelease-tracker.json`:\n\n```json\n{\n  \"repos\": [\n    {\n      \"owner\": \"openclaw\",\n      \"repo\": \"openclaw\",\n      \"displayName\": \"OpenClaw\",\n      \"priorities\": [\"discord\", \"voice\", \"telegram\", \"cron\", \"agent\"],\n      \"outputChannel\": \"\u003Cyour-discord-channel-id>\",\n      \"outputFormat\": \"discord-forum\",\n      \"language\": \"en\",\n      \"includePrerelease\": false\n    }\n  ],\n  \"versionStore\": \"release-tracker-state.json\",\n  \"schedule\": \"0 10 * * *\",\n  \"timezone\": \"UTC\"\n}\n```\n\n### Config Fields\n\n- `repos[].owner` \u002F `repos[].repo` — GitHub owner\u002Frepo\n- `repos[].displayName` — friendly name for output header\n- `repos[].priorities` — keywords to sort higher in summary (matched against changelog text)\n- `repos[].outputChannel` — Discord channel\u002Fforum ID for delivery\n- `repos[].outputFormat` — `discord-forum` | `discord-channel` | `telegram` | `slack` | `text`\n  - `discord-forum`: create a new forum post per release\n  - `discord-channel`: send a message to a Discord channel\n  - `telegram`: send a message to a Telegram chat\u002Fchannel\u002Fgroup\n  - `slack`: send a message to a Slack channel\n  - `text`: return plain text (for piping to other tools)\n- `repos[].language` — `zh` | `en` (summary language)\n- `repos[].includePrerelease` — track pre-release\u002FRC versions\n- `repos[].filter` — optional, `stable` | `all` (default: `stable`)\n- `versionStore` — filename for tracking last-seen versions (relative to workspace)\n- `schedule` — cron expression for check frequency\n- `timezone` — timezone for cron schedule\n\n## Workflow\n\n### Check for New Releases\n\n1. Read config from `release-tracker.json`\n2. Read version state from `\u003CversionStore>`\n3. For each repo:\n   ```bash\n   gh release list --repo \u003Cowner>\u002F\u003Crepo> --limit 5 --json tagName,publishedAt,isPrerelease\n   ```\n4. Compare latest tag against stored version\n5. If new version found, proceed to summarize\n\n### Generate Summary\n\n1. Fetch release content:\n   ```bash\n   gh release view \u003Ctag> --repo \u003Cowner>\u002F\u003Crepo> --json body\n   ```\n2. If release body is sparse, also check local CHANGELOG if the package is installed:\n   ```bash\n   cat \u002Fopt\u002Fhomebrew\u002Flib\u002Fnode_modules\u002F\u003Cpackage>\u002FCHANGELOG.md\n   ```\n3. Parse and categorize changes into sections:\n   - **Priority items** — lines matching any `priorities` keywords, shown first\n   - **Features** — new capabilities\n   - **Breaking changes** — marked with ⚠️\n   - **Fixes** — bug fixes relevant to user (skip internal\u002FCI fixes)\n   - **Security** — collapsed at bottom unless critical\n   - Skip: CI\u002Ftest-only changes, dependency bumps, internal refactors\n\n### Prioritization Rules\n\nSort entries within each section:\n1. Lines matching `priorities` keywords → top\n2. User-facing changes → middle\n3. Internal\u002Finfrastructure → bottom\n4. Omit: trivial fixes, test-only changes, doc typos\n\n### Format Output\n\n#### Discord Forum (`discord-forum`)\n\n```\nTitle: 📦 v{version}\n\nBody:\n## {displayName} v{version}\n\n### ⭐ Key Features\n{priority matches + features, formatted as bold headers with descriptions}\n\n### ⚠️ Breaking Changes\n{breaking changes with migration notes}\n\n### 🔧 Fixes\n{relevant fixes, grouped by area}\n\n### 🛡️ Security\n{security fixes, brief}\n```\n\n#### Discord Channel (`discord-channel`)\n\nCompact single-message format, max 2000 chars.\n\n#### Telegram (`telegram`)\n\nSame structure as Discord Channel but respects Telegram formatting (markdown v2). Max 4096 chars.\n\n#### Slack (`slack`)\n\nSame structure, uses Slack mrkdwn formatting. Max 3000 chars.\n\n#### Text (`text`)\n\nPlain markdown, no emoji headers.\n\n### Deliver\n\nBased on `outputFormat`:\n- `discord-forum`: `message(action=thread-create, channelId=\u003CoutputChannel>, threadName=\u003Ctitle>, message=\u003Cbody>)`\n- `discord-channel`: `message(action=send, channel=discord, target=\u003CoutputChannel>, message=\u003Cbody>)`\n- `telegram`: `message(action=send, channel=telegram, target=\u003CoutputChannel>, message=\u003Cbody>)`\n- `slack`: `message(action=send, channel=slack, target=\u003CoutputChannel>, message=\u003Cbody>)`\n- `text`: return as tool result\n\n### Update State\n\nAfter successful delivery, update version store:\n```json\n{\n  \"openclaw\u002Fopenclaw\": {\n    \"lastVersion\": \"2026.2.22-2\",\n    \"lastCheckedAt\": \"2026-02-24T10:00:00+09:00\",\n    \"lastPublishedAt\": \"2026-02-22T...\"\n  }\n}\n```\n\n## Cron Setup\n\nCreate the cron job for automated checking:\n\n```\nName: release-tracker\nSchedule: {config.schedule} with tz {config.timezone}\nSession: isolated\nPayload: agentTurn with message referencing this skill\nDelivery: none (skill handles its own delivery)\n```\n\nThe cron message should instruct the agent to:\n1. Read `release-tracker.json` for config\n2. Read `release-tracker-state.json` for last versions\n3. Check each repo via `gh release list`\n4. If new releases found, generate summaries and deliver\n5. Update state file\n\n## Manual Check\n\nUser can trigger manually: \"check for new releases\" or \"any updates on openclaw?\"\n\nThe agent should:\n1. Load config\n2. Run the check workflow\n3. Report findings conversationally (not necessarily in forum format)\n","# Release Tracker\n\nMonitor one or more GitHub repositories for new releases, generate prioritized summaries, and deliver them to configured channels.\n\n## Prerequisites\n\n- `gh` CLI installed and authenticated (`gh auth status`)\n- For Discord delivery: Discord channel configured in OpenClaw\n\n## Quick Start\n\n### Single Repo Setup\n\nSet up tracking for one repo with a cron job:\n\n```\n1. Create a config file at \u003Cworkspace>\u002Frelease-tracker.json (see Configuration)\n2. Create a cron job (isolated, daily) that runs the check\n3. The cron reads config, checks GitHub, compares versions, posts if new\n```\n\n### Multi-Repo Setup\n\nAdd multiple repos to the `repos` array in config. Each repo has independent version tracking and priority rules.\n\n## Configuration\n\nStore config at `\u003Cworkspace>\u002Frelease-tracker.json`:\n\n```json\n{\n  \"repos\": [\n    {\n      \"owner\": \"openclaw\",\n      \"repo\": \"openclaw\",\n      \"displayName\": \"OpenClaw\",\n      \"priorities\": [\"discord\", \"voice\", \"telegram\", \"cron\", \"agent\"],\n      \"outputChannel\": \"\u003Cyour-discord-channel-id>\",\n      \"outputFormat\": \"discord-forum\",\n      \"language\": \"en\",\n      \"includePrerelease\": false\n    }\n  ],\n  \"versionStore\": \"release-tracker-state.json\",\n  \"schedule\": \"0 10 * * *\",\n  \"timezone\": \"UTC\"\n}\n```\n\n### Config Fields\n\n- `repos[].owner` \u002F `repos[].repo` — GitHub owner\u002Frepo\n- `repos[].displayName` — friendly name for output header\n- `repos[].priorities` — keywords to sort higher in summary (matched against changelog text)\n- `repos[].outputChannel` — Discord channel\u002Fforum ID for delivery\n- `repos[].outputFormat` — `discord-forum` | `discord-channel` | `telegram` | `slack` | `text`\n  - `discord-forum`: create a new forum post per release\n  - `discord-channel`: send a message to a Discord channel\n  - `telegram`: send a message to a Telegram chat\u002Fchannel\u002Fgroup\n  - `slack`: send a message to a Slack channel\n  - `text`: return plain text (for piping to other tools)\n- `repos[].language` — `zh` | `en` (summary language)\n- `repos[].includePrerelease` — track pre-release\u002FRC versions\n- `repos[].filter` — optional, `stable` | `all` (default: `stable`)\n- `versionStore` — filename for tracking last-seen versions (relative to workspace)\n- `schedule` — cron expression for check frequency\n- `timezone` — timezone for cron schedule\n\n## Workflow\n\n### Check for New Releases\n\n1. Read config from `release-tracker.json`\n2. Read version state from `\u003CversionStore>`\n3. For each repo:\n   ```bash\n   gh release list --repo \u003Cowner>\u002F\u003Crepo> --limit 5 --json tagName,publishedAt,isPrerelease\n   ```\n4. Compare latest tag against stored version\n5. If new version found, proceed to summarize\n\n### Generate Summary\n\n1. Fetch release content:\n   ```bash\n   gh release view \u003Ctag> --repo \u003Cowner>\u002F\u003Crepo> --json body\n   ```\n2. If release body is sparse, also check local CHANGELOG if the package is installed:\n   ```bash\n   cat \u002Fopt\u002Fhomebrew\u002Flib\u002Fnode_modules\u002F\u003Cpackage>\u002FCHANGELOG.md\n   ```\n3. Parse and categorize changes into sections:\n   - **Priority items** — lines matching any `priorities` keywords, shown first\n   - **Features** — new capabilities\n   - **Breaking changes** — marked with ⚠️\n   - **Fixes** — bug fixes relevant to user (skip internal\u002FCI fixes)\n   - **Security** — collapsed at bottom unless critical\n   - Skip: CI\u002Ftest-only changes, dependency bumps, internal refactors\n\n### Prioritization Rules\n\nSort entries within each section:\n1. Lines matching `priorities` keywords → top\n2. User-facing changes → middle\n3. Internal\u002Finfrastructure → bottom\n4. Omit: trivial fixes, test-only changes, doc typos\n\n### Format Output\n\n#### Discord Forum (`discord-forum`)\n\n```\nTitle: 📦 v{version}\n\nBody:\n## {displayName} v{version}\n\n### ⭐ Key Features\n{priority matches + features, formatted as bold headers with descriptions}\n\n### ⚠️ Breaking Changes\n{breaking changes with migration notes}\n\n### 🔧 Fixes\n{relevant fixes, grouped by area}\n\n### 🛡️ Security\n{security fixes, brief}\n```\n\n#### Discord Channel (`discord-channel`)\n\nCompact single-message format, max 2000 chars.\n\n#### Telegram (`telegram`)\n\nSame structure as Discord Channel but respects Telegram formatting (markdown v2). Max 4096 chars.\n\n#### Slack (`slack`)\n\nSame structure, uses Slack mrkdwn formatting. Max 3000 chars.\n\n#### Text (`text`)\n\nPlain markdown, no emoji headers.\n\n### Deliver\n\nBased on `outputFormat`:\n- `discord-forum`: `message(action=thread-create, channelId=\u003CoutputChannel>, threadName=\u003Ctitle>, message=\u003Cbody>)`\n- `discord-channel`: `message(action=send, channel=discord, target=\u003CoutputChannel>, message=\u003Cbody>)`\n- `telegram`: `message(action=send, channel=telegram, target=\u003CoutputChannel>, message=\u003Cbody>)`\n- `slack`: `message(action=send, channel=slack, target=\u003CoutputChannel>, message=\u003Cbody>)`\n- `text`: return as tool result\n\n### Update State\n\nAfter successful delivery, update version store:\n```json\n{\n  \"openclaw\u002Fopenclaw\": {\n    \"lastVersion\": \"2026.2.22-2\",\n    \"lastCheckedAt\": \"2026-02-24T10:00:00+09:00\",\n    \"lastPublishedAt\": \"2026-02-22T...\"\n  }\n}\n```\n\n## Cron Setup\n\nCreate the cron job for automated checking:\n\n```\nName: release-tracker\nSchedule: {config.schedule} with tz {config.timezone}\nSession: isolated\nPayload: agentTurn with message referencing this skill\nDelivery: none (skill handles its own delivery)\n```\n\nThe cron message should instruct the agent to:\n1. Read `release-tracker.json` for config\n2. Read `release-tracker-state.json` for last versions\n3. Check each repo via `gh release list`\n4. If new releases found, generate summaries and deliver\n5. Update state file\n\n## Manual Check\n\nUser can trigger manually: \"check for new releases\" or \"any updates on openclaw?\"\n\nThe agent should:\n1. Load config\n2. Run the check workflow\n3. Report findings conversationally (not necessarily in forum format)\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fjo9900\u002Frelease-tracker",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 release-tracker",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill release-tracker",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill release-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fjo9900\u002Frelease-tracker\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",[],[]]