[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76Z2J345A7MA44M6HESTPQS":3,"skill-same:01M76Z2J345A7MA44M6HESTPQS":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},"01M76Z2J345A7MA44M6HESTPQS","upstream-recon",null,"Investigate an open-source project before interacting with it — PRs, issues, or comments. Use BEFORE: filing an issue, submitting a PR, or commenting on an existing thread. Triggers on: \"upstream recon\", \"should I PR this\", \"will they merge\", \"check the project\", \"investigate the repo\", \"PR strategy\", \"file an issue\", \"check existing issues\", \"should I comment\", or any time the user wants to interact with a repo they don't maintain. Also use proactively when about to file an issue or PR — checking existing threads prevents duplicates and wasted effort.","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\u002Fsemmyt\u002Fupstream-recon\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: upstream-recon\ndescription: >\n  Investigate an open-source project before interacting with it — PRs, issues, or comments.\n  Use BEFORE: filing an issue, submitting a PR, or commenting on an existing thread.\n  Triggers on: \"upstream recon\", \"should I PR this\", \"will they merge\",\n  \"check the project\", \"investigate the repo\", \"PR strategy\", \"file an issue\",\n  \"check existing issues\", \"should I comment\", or any time the user wants to\n  interact with a repo they don't maintain.\n  Also use proactively when about to file an issue or PR — checking existing\n  threads prevents duplicates and wasted effort.\n---\n\n# Upstream Recon\n\nInvestigate a repo's culture and existing threads before interacting. Prevents\nduplicate issues, wasted PR effort, and uninformed comments.\n\n**Arguments**: `\u003Cowner\u002Frepo> [topic-keyword]`\n\n## Procedure\n\nUse `gh` CLI throughout. Run independent queries in parallel.\n\n1. **Repo metadata** — stars, forks, license, last push date, archived status\n2. **Top 10 contributors** — commit counts. Is it one person with 90%+ commits?\n3. **Existing issues search** — search open AND closed issues for the topic keyword.\n   Check for duplicates, prior art, and maintainer responses. Report what was found.\n4. **Recent 30 PRs** (all states) — get the lay of the land\n5. **Merged PRs** (last 20) — who merges them? How fast? What types get accepted?\n6. **Closed-without-merge PRs** (last 50, filter `mergedAt == null`) — deep-dive\n   2-3 notable rejections: read comments for maintainer reasoning\n7. **Open PRs** — how many sit with 0 reviews? For how long?\n8. **Topic deep-dive** (if keyword given) — read comments on 2-3 most relevant\n   existing issues\u002FPRs to understand maintainer sentiment and community workarounds\n\n## Analysis Dimensions\n\n- **Governance**: Solo maintainer \u002F small team \u002F community-driven\n- **External PR reception**: Welcoming \u002F selective (bugs yes, features no) \u002F closed shop\n- **Issue responsiveness**: How fast do maintainers respond to issues? Do they engage or auto-close?\n- **Merge velocity**: Days from open to merge for external contributors\n- **Rejection patterns**: Ghosted? \"Building it myself\"? \"File issue first\"? Bot auto-closed?\n- **Topic overlap**: Has this been attempted or discussed before? Active workarounds?\n\n## Recommendation\n\nEnd the report with one of:\n\n- **MERGE-LIKELY** — project merges external feature PRs, no competing work, maintainer receptive\n- **MERGE-UNLIKELY** — maintainer builds features themselves, similar PRs closed\u002Fignored, feature contradicts direction\n- **FILE-ISSUE-FIRST** — feature not yet discussed, maintainer is selective but responsive to issues, gauge interest before coding\n- **COMMENT-ON-EXISTING** — existing issue\u002FPR already covers this, add your workaround or +1 there instead\n- **DUPLICATE-EXISTS** — exact issue already filed, do not create another\n\nInclude concrete next steps (e.g., \"comment on #13738 with your workaround\",\n\"start with a bug fix PR to build credibility\", \"file an issue referencing #189\",\n\"fork and maintain independently\").\n","# Upstream Recon\n\nInvestigate a repo's culture and existing threads before interacting. Prevents\nduplicate issues, wasted PR effort, and uninformed comments.\n\n**Arguments**: `\u003Cowner\u002Frepo> [topic-keyword]`\n\n## Procedure\n\nUse `gh` CLI throughout. Run independent queries in parallel.\n\n1. **Repo metadata** — stars, forks, license, last push date, archived status\n2. **Top 10 contributors** — commit counts. Is it one person with 90%+ commits?\n3. **Existing issues search** — search open AND closed issues for the topic keyword.\n   Check for duplicates, prior art, and maintainer responses. Report what was found.\n4. **Recent 30 PRs** (all states) — get the lay of the land\n5. **Merged PRs** (last 20) — who merges them? How fast? What types get accepted?\n6. **Closed-without-merge PRs** (last 50, filter `mergedAt == null`) — deep-dive\n   2-3 notable rejections: read comments for maintainer reasoning\n7. **Open PRs** — how many sit with 0 reviews? For how long?\n8. **Topic deep-dive** (if keyword given) — read comments on 2-3 most relevant\n   existing issues\u002FPRs to understand maintainer sentiment and community workarounds\n\n## Analysis Dimensions\n\n- **Governance**: Solo maintainer \u002F small team \u002F community-driven\n- **External PR reception**: Welcoming \u002F selective (bugs yes, features no) \u002F closed shop\n- **Issue responsiveness**: How fast do maintainers respond to issues? Do they engage or auto-close?\n- **Merge velocity**: Days from open to merge for external contributors\n- **Rejection patterns**: Ghosted? \"Building it myself\"? \"File issue first\"? Bot auto-closed?\n- **Topic overlap**: Has this been attempted or discussed before? Active workarounds?\n\n## Recommendation\n\nEnd the report with one of:\n\n- **MERGE-LIKELY** — project merges external feature PRs, no competing work, maintainer receptive\n- **MERGE-UNLIKELY** — maintainer builds features themselves, similar PRs closed\u002Fignored, feature contradicts direction\n- **FILE-ISSUE-FIRST** — feature not yet discussed, maintainer is selective but responsive to issues, gauge interest before coding\n- **COMMENT-ON-EXISTING** — existing issue\u002FPR already covers this, add your workaround or +1 there instead\n- **DUPLICATE-EXISTS** — exact issue already filed, do not create another\n\nInclude concrete next steps (e.g., \"comment on #13738 with your workaround\",\n\"start with a bug fix PR to build credibility\", \"file an issue referencing #189\",\n\"fork and maintain independently\").\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fsemmyt\u002Fupstream-recon",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 upstream-recon",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill upstream-recon",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill upstream-recon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsemmyt\u002Fupstream-recon\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",[],[]]