[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5CFSK7MDKX1EP24V6E9ZG":3,"skill-same:01M7F5CFSK7MDKX1EP24V6E9ZG":50},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7F5CFSK7MDKX1EP24V6E9ZG","cloud-sync",null,"Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says \"set up cloud sync\", \"sync my memories\", \"cmem pro\", \"cloud backup\", \"sync status\", or wants their memory database backed up or synced to their cmem.ai account.","Prasanth595\u002Fclaude-mem-mirror","Prasanth595","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F85020330?v=4","01M7F59DKDR8Z9JKCPKAGA7T0P","Prasanth Arumugam","01M7F59PY83WFCMPV6J951X4TN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fcloud-sync\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: cloud-sync\ndescription: Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says \"set up cloud sync\", \"sync my memories\", \"cmem pro\", \"cloud backup\", \"sync status\", or wants their memory database backed up or synced to their cmem.ai account.\nallowed-tools:\n  - Bash\n  - Read\n  - AskUserQuestion\n---\n\n# Cloud Sync (cmem.ai Pro)\n\nThe installed worker syncs through SyncHub. There is one client, one durable\noperation log, and no separate sync daemon. This skill checks status and points\nthe user to the installer's cmem.ai sign-in, which writes the connection.\n\n**Security rule:** never ask the user to paste the sync token into this chat,\nand never put it in a command you write, print it, put it in argv, or log it. A\nsecret pasted into a chat lands in the transcript, which claude-mem itself can\ncapture and sync. The installer writes the token to\n`~\u002F.claude-mem\u002Fsettings.json` (mode `0600`) without it ever passing through\nthis conversation.\n\n## 1. Check status\n\nResolve the worker port and query the always-registered status route:\n\n```bash\nPORT=\"${CLAUDE_MEM_WORKER_PORT:-$(node -e \"const fs=require('fs'),p=require('path'),os=require('os');const uid=(typeof process.getuid==='function'?process.getuid():77);const fallback=String(37700+(uid%100));try{const s=JSON.parse(fs.readFileSync(p.join(os.homedir(),'.claude-mem','settings.json'),'utf-8'));process.stdout.write(String(s.CLAUDE_MEM_WORKER_PORT||fallback));}catch{process.stdout.write(fallback);}\" 2>\u002Fdev\u002Fnull)}\"\ncurl -s \"http:\u002F\u002F127.0.0.1:${PORT}\u002Fapi\u002Fsync\u002Fstatus\"\n```\n\n- `configured: true` and `hub.reachable: true` → the worker completed an\n  authenticated `GET \u002Fv1\u002Fsync\u002Fstatus` against SyncHub. Report `deviceId`,\n  pending counts, `lastFlushAt`, `lastError`, and the Hub head\u002Fcheckpoint;\n  stop unless the user asked to replace the connection.\n- `configured: true` and `hub.reachable: false` → report `hub.error` and say\n  the SyncHub connection is not verified. A zero pending count or\n  `lastError: null` is not success because an empty queue performs no push.\n- `configured: false` → continue.\n- Connection refused, 404, or 503 immediately after restart → retry every\n  three seconds for about 30 seconds before diagnosing the worker.\n\n## 2. Connect through the installer\n\nAsk the user to run this in their own terminal:\n\n```bash\nnpx claude-mem install\n```\n\nand to choose **CMEM Pro** when the installer asks. The installer signs them in\nthrough the browser (they approve a device code), then writes the sync token,\nuser id and SyncHub URL into `~\u002F.claude-mem\u002Fsettings.json` itself and restarts\nthe worker. Nothing secret is typed into this chat.\n\nIf the user cannot run the installer interactively (CI, a remote box), point\nthem to the headless setup guide, https:\u002F\u002Fdocs.claude-mem.ai\u002Fcmem-pro-headless,\nand let them apply its manual recipe in their own terminal or editor. Do not\ncollect the values yourself.\n\nThe worker mints and persists a device id on first start and defaults the device\nname to the hostname.\n\n## 3. Verify\n\nOnce the installer finishes, poll the status route every five seconds for up to\n30 seconds. If the worker was not restarted, restart it first:\n\n```bash\ncurl -s -X POST \"http:\u002F\u002F127.0.0.1:${PORT}\u002Fapi\u002Fadmin\u002Frestart\"\n```\n\nSuccess means `configured: true`, `hub.reachable: true`, and `lastError: null`.\nThe local route always makes an authenticated, read-only SyncHub status probe,\neven when every pending count is zero; it never uses a legacy cmem.ai Pro status\nroute and never appends or advances sync state. Pending counts describe only\nwrites made after the SyncHub launch baseline; setup does not migrate a\npre-launch local corpus.\n\nIf `hub.reachable` is false, report `hub.error`. If `lastError` is non-null,\nreport it too, and suggest running `npx claude-mem install` again to refresh the\nconnection. Never include the token.\n\n## 4. Report\n\nReport device id, pending counts, last successful flush, Hub reachability and\ncheckpoint, and any Hub\u002Fflush error. End with this privacy note:\n\n> Cloud sync uploads your observation narratives and full prompt text to your\n> cmem.ai account.\n","# Cloud Sync (cmem.ai Pro)\n\nThe installed worker syncs through SyncHub. There is one client, one durable\noperation log, and no separate sync daemon. This skill checks status and points\nthe user to the installer's cmem.ai sign-in, which writes the connection.\n\n**Security rule:** never ask the user to paste the sync token into this chat,\nand never put it in a command you write, print it, put it in argv, or log it. A\nsecret pasted into a chat lands in the transcript, which claude-mem itself can\ncapture and sync. The installer writes the token to\n`~\u002F.claude-mem\u002Fsettings.json` (mode `0600`) without it ever passing through\nthis conversation.\n\n## 1. Check status\n\nResolve the worker port and query the always-registered status route:\n\n```bash\nPORT=\"${CLAUDE_MEM_WORKER_PORT:-$(node -e \"const fs=require('fs'),p=require('path'),os=require('os');const uid=(typeof process.getuid==='function'?process.getuid():77);const fallback=String(37700+(uid%100));try{const s=JSON.parse(fs.readFileSync(p.join(os.homedir(),'.claude-mem','settings.json'),'utf-8'));process.stdout.write(String(s.CLAUDE_MEM_WORKER_PORT||fallback));}catch{process.stdout.write(fallback);}\" 2>\u002Fdev\u002Fnull)}\"\ncurl -s \"http:\u002F\u002F127.0.0.1:${PORT}\u002Fapi\u002Fsync\u002Fstatus\"\n```\n\n- `configured: true` and `hub.reachable: true` → the worker completed an\n  authenticated `GET \u002Fv1\u002Fsync\u002Fstatus` against SyncHub. Report `deviceId`,\n  pending counts, `lastFlushAt`, `lastError`, and the Hub head\u002Fcheckpoint;\n  stop unless the user asked to replace the connection.\n- `configured: true` and `hub.reachable: false` → report `hub.error` and say\n  the SyncHub connection is not verified. A zero pending count or\n  `lastError: null` is not success because an empty queue performs no push.\n- `configured: false` → continue.\n- Connection refused, 404, or 503 immediately after restart → retry every\n  three seconds for about 30 seconds before diagnosing the worker.\n\n## 2. Connect through the installer\n\nAsk the user to run this in their own terminal:\n\n```bash\nnpx claude-mem install\n```\n\nand to choose **CMEM Pro** when the installer asks. The installer signs them in\nthrough the browser (they approve a device code), then writes the sync token,\nuser id and SyncHub URL into `~\u002F.claude-mem\u002Fsettings.json` itself and restarts\nthe worker. Nothing secret is typed into this chat.\n\nIf the user cannot run the installer interactively (CI, a remote box), point\nthem to the headless setup guide, https:\u002F\u002Fdocs.claude-mem.ai\u002Fcmem-pro-headless,\nand let them apply its manual recipe in their own terminal or editor. Do not\ncollect the values yourself.\n\nThe worker mints and persists a device id on first start and defaults the device\nname to the hostname.\n\n## 3. Verify\n\nOnce the installer finishes, poll the status route every five seconds for up to\n30 seconds. If the worker was not restarted, restart it first:\n\n```bash\ncurl -s -X POST \"http:\u002F\u002F127.0.0.1:${PORT}\u002Fapi\u002Fadmin\u002Frestart\"\n```\n\nSuccess means `configured: true`, `hub.reachable: true`, and `lastError: null`.\nThe local route always makes an authenticated, read-only SyncHub status probe,\neven when every pending count is zero; it never uses a legacy cmem.ai Pro status\nroute and never appends or advances sync state. Pending counts describe only\nwrites made after the SyncHub launch baseline; setup does not migrate a\npre-launch local corpus.\n\nIf `hub.reachable` is false, report `hub.error`. If `lastError` is non-null,\nreport it too, and suggest running `npx claude-mem install` again to refresh the\nconnection. Never include the token.\n\n## 4. Report\n\nReport device id, pending counts, last successful flush, Hub reachability and\ncheckpoint, and any Hub\u002Fflush error. End with this privacy note:\n\n> Cloud sync uploads your observation narratives and full prompt text to your\n> cmem.ai account.\n",{"name":5,"description":7,"allowed-tools":24},[25,26,27],"Bash","Read","AskUserQuestion","main","3fae1eb45ba1a7fbd4818527f48b439991a273da","plugin\u002Fskills\u002Fcloud-sync","https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror","https:\u002F\u002Fgithub.com\u002FPrasanth595","https:\u002F\u002Flinktr.ee\u002Fprasanth_","Senior DevOps Engineer · Kubernetes | Terraform | AWS · Azure · GCP — open to remote opportunities","2026-10-19 20:21:01",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Prasanth595\u002Fclaude-mem-mirror --skill cloud-sync",{"tool":42,"command":43},"bunx","bunx skills add Prasanth595\u002Fclaude-mem-mirror --skill cloud-sync",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Prasanth595\u002Fclaude-mem-mirror --skill cloud-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fcloud-sync\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7F5FKF932NX0T4D2KFWECC0","wowerpoint","Turn one document into a kawaii NotebookLM slide deck. Use for \"wowerpoint this\", \"make a deck about \u003Cfile>\", \"turn this report into slides\", or any request to render a single document as shareable narrative slides.","https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwowerpoint\u002FSKILL.md",[],[],{"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":19},"01M7F5FH7ASJYF41X6F8SGYH2Y","what-the","What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.","https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwhat-the\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7F5FA3S3BFG7Q8YXBG5AA3Z","weekly-digests","Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for \"weekly digests\", \"week-by-week story\", \"serial timeline\", or \"narrative chapters\" of a project's history.","https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fweekly-digests\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7F5F5SKSTF4161VCS1PJXWQ","version-bump","Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. Ends with the agent running npm publish itself using the maintainer's npm token.","https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fversion-bump\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7F5F1W1TNCJWDJFSNV133Z7","timeline-report","Generate a \"Journey Into [Project]\" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.","https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Ftimeline-report\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7F5EYXHFVZPB3PYD4296NJY","standup","Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.","https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fstandup\u002FSKILL.md",[],[]]