[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5CCD9759PWXD8S2AXJ20P":3,"skill-same:01M7F5CCD9759PWXD8S2AXJ20P":46},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F5CCD9759PWXD8S2AXJ20P","childhood",null,"Babysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.","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\u002Fchildhood\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: childhood\ndescription: Babysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.\n---\n\n# Childhood\n\nStay with a release after it ships. Verify what users receive and what production serves, then fix verified regressions within the user's authorized scope. A successful merge or publish command is the start of this work.\n\n## Establish the release\n\n- Identify the repository, release version, immutable tag commit, merge commit, production deployment, and affected delivery surfaces. Use the release receipt and actual provider\u002Fregistry state; do not guess from the current branch or today's latest build.\n- Record the release, observation start\u002Fend, checks, findings, and next action with `work_state_write` when available. Keep announcements and unrelated infrastructure failures distinguishable from product regressions.\n- Carry forward existing authorization. Monitoring does not itself authorize another release, rollback, production migration, or external announcement. Prepare and validate a concrete fix before requesting any authorization still missing.\n\n## Verify the delivered release\n\nChoose the checks relevant to its delivery surfaces; independent checks can run in parallel.\n\n| Surface | Evidence to collect |\n| --- | --- |\n| Source and CI | Confirm the tag resolves to the shipped commit. Inspect CI for that commit and any release\u002Fchangelog commits, including late failures. Paginate new issue reports, merged-PR comments, reviews, and review threads since release; verify actionable reports against the shipped code. |\n| Published package | Check the exact registry version and the intended distribution tag separately. Verify package hash, entry points, and required files in the downloaded artifact; run a small installed CLI smoke from an isolated directory. Preserve the command's actual exit code when filtering output. |\n| Hosted service | Confirm the live production alias serves the intended deployment\u002Fcommit. Check health and the changed user path through the real authenticated interface, plus relevant error signals. For schema changes, verify the normal migration ledger reports no pending migrations or drift. |\n| Installed plugin | Discover the user's actual enabled registration\u002Fcache, not just the marketplace copy. Compare changed source\u002Fdistribution artifacts and open a fresh tool connection. Compare the running worker's version\u002Fpath to the enabled install; an updated cache can still talk to a stale process. Exercise the affected install\u002Fupgrade handoff where authorized. Check hooks or watcher configuration in their real project\u002Fruntime scope; label behavior you did not exercise as unverified. |\n\nFor a claude-mem search release, exercise guided steps 1, 2, and 3, automatic search, and readable invalid-input guidance through fresh local and hosted MCP connections when those surfaces shipped. Verify selected evidence, short opaque continuations, and concise text without pure JSON or duplicated structured metadata. Keep probes read-only unless writes are part of the explicit test scope. Never print credentials or private result bodies.\n\nPublication can lag behind a successful command. An exact-version 404 or stale distribution tag remains pending until the registry agrees; use bounded retries and investigate the actual publish target\u002Fstatus before republishing. A warning alone is not a regression: verify the final artifact. Likewise, a failed automated publish job may be superseded by a verified authorized manual publish; retain the workflow failure as a separate finding.\n\n## Observe and repair\n\n- Honor the requested observation window. Without one, watch through 30 minutes after the release first becomes publicly available or production becomes ready, whichever affected surface is later. For an older release, do a fresh sweep and inspect the completed late CI and reports covering that interval.\n- Poll pending or changing checks every 30–60 seconds; check steady signals every 2–5 minutes. Keep individual waits at most 60 seconds so user steering and progress updates remain responsive. An unavailable API is a coverage gap, not evidence that the release is healthy.\n- Verify each finding before changing code. Distinguish a release regression, a pre-existing issue, an operational failure, and a resolved\u002Ftransient signal; give each its own evidence and next action.\n- Make focused fixes, run checks appropriate to the change, and use the repository's normal PR\u002Frelease\u002Fdeployment process. Use [babysit](..\u002Fbabysit\u002FSKILL.md) for a repair PR and [version-bump](..\u002Fversion-bump\u002FSKILL.md) when a new claude-mem release is authorized. Published versions and existing tags stay immutable.\n- After a repair ships, restart observation for the changed delivery surface and rerun its affected user path. Preserve unrelated worktrees, workers, registrations, user settings, and inference\u002Fprovider policy.\n- A repeated infrastructure failure or deleted notification webhook needs a concrete follow-up. Keep it pending with its cause and owner action; do not repeatedly retry it or announce success to another destination.\n\n## Finish with evidence\n\nFinish when the relevant CI is settled, delivered artifacts and affected user paths pass, no actionable release regression remains, and the observation window is satisfied. Do one final fresh sweep before reporting.\n\nIf a required check cannot be completed, report the release as partially verified with that coverage gap and next action. Separate an externally blocked operational follow-up from verified product health; do not silently mark either as resolved.\n\nReturn concise purpose-specific text: release\u002Ftag\u002Fdeployment identity, checks and observation times, verified findings and repairs, and anything still pending. Keep raw API envelopes, internal metadata, and complete logs out of model-facing output. Link to a compact receipt when useful.\n","# Childhood\n\nStay with a release after it ships. Verify what users receive and what production serves, then fix verified regressions within the user's authorized scope. A successful merge or publish command is the start of this work.\n\n## Establish the release\n\n- Identify the repository, release version, immutable tag commit, merge commit, production deployment, and affected delivery surfaces. Use the release receipt and actual provider\u002Fregistry state; do not guess from the current branch or today's latest build.\n- Record the release, observation start\u002Fend, checks, findings, and next action with `work_state_write` when available. Keep announcements and unrelated infrastructure failures distinguishable from product regressions.\n- Carry forward existing authorization. Monitoring does not itself authorize another release, rollback, production migration, or external announcement. Prepare and validate a concrete fix before requesting any authorization still missing.\n\n## Verify the delivered release\n\nChoose the checks relevant to its delivery surfaces; independent checks can run in parallel.\n\n| Surface | Evidence to collect |\n| --- | --- |\n| Source and CI | Confirm the tag resolves to the shipped commit. Inspect CI for that commit and any release\u002Fchangelog commits, including late failures. Paginate new issue reports, merged-PR comments, reviews, and review threads since release; verify actionable reports against the shipped code. |\n| Published package | Check the exact registry version and the intended distribution tag separately. Verify package hash, entry points, and required files in the downloaded artifact; run a small installed CLI smoke from an isolated directory. Preserve the command's actual exit code when filtering output. |\n| Hosted service | Confirm the live production alias serves the intended deployment\u002Fcommit. Check health and the changed user path through the real authenticated interface, plus relevant error signals. For schema changes, verify the normal migration ledger reports no pending migrations or drift. |\n| Installed plugin | Discover the user's actual enabled registration\u002Fcache, not just the marketplace copy. Compare changed source\u002Fdistribution artifacts and open a fresh tool connection. Compare the running worker's version\u002Fpath to the enabled install; an updated cache can still talk to a stale process. Exercise the affected install\u002Fupgrade handoff where authorized. Check hooks or watcher configuration in their real project\u002Fruntime scope; label behavior you did not exercise as unverified. |\n\nFor a claude-mem search release, exercise guided steps 1, 2, and 3, automatic search, and readable invalid-input guidance through fresh local and hosted MCP connections when those surfaces shipped. Verify selected evidence, short opaque continuations, and concise text without pure JSON or duplicated structured metadata. Keep probes read-only unless writes are part of the explicit test scope. Never print credentials or private result bodies.\n\nPublication can lag behind a successful command. An exact-version 404 or stale distribution tag remains pending until the registry agrees; use bounded retries and investigate the actual publish target\u002Fstatus before republishing. A warning alone is not a regression: verify the final artifact. Likewise, a failed automated publish job may be superseded by a verified authorized manual publish; retain the workflow failure as a separate finding.\n\n## Observe and repair\n\n- Honor the requested observation window. Without one, watch through 30 minutes after the release first becomes publicly available or production becomes ready, whichever affected surface is later. For an older release, do a fresh sweep and inspect the completed late CI and reports covering that interval.\n- Poll pending or changing checks every 30–60 seconds; check steady signals every 2–5 minutes. Keep individual waits at most 60 seconds so user steering and progress updates remain responsive. An unavailable API is a coverage gap, not evidence that the release is healthy.\n- Verify each finding before changing code. Distinguish a release regression, a pre-existing issue, an operational failure, and a resolved\u002Ftransient signal; give each its own evidence and next action.\n- Make focused fixes, run checks appropriate to the change, and use the repository's normal PR\u002Frelease\u002Fdeployment process. Use [babysit](..\u002Fbabysit\u002FSKILL.md) for a repair PR and [version-bump](..\u002Fversion-bump\u002FSKILL.md) when a new claude-mem release is authorized. Published versions and existing tags stay immutable.\n- After a repair ships, restart observation for the changed delivery surface and rerun its affected user path. Preserve unrelated worktrees, workers, registrations, user settings, and inference\u002Fprovider policy.\n- A repeated infrastructure failure or deleted notification webhook needs a concrete follow-up. Keep it pending with its cause and owner action; do not repeatedly retry it or announce success to another destination.\n\n## Finish with evidence\n\nFinish when the relevant CI is settled, delivered artifacts and affected user paths pass, no actionable release regression remains, and the observation window is satisfied. Do one final fresh sweep before reporting.\n\nIf a required check cannot be completed, report the release as partially verified with that coverage gap and next action. Separate an externally blocked operational follow-up from verified product health; do not silently mark either as resolved.\n\nReturn concise purpose-specific text: release\u002Ftag\u002Fdeployment identity, checks and observation times, verified findings and repairs, and anything still pending. Keep raw API envelopes, internal metadata, and complete logs out of model-facing output. Link to a compact receipt when useful.\n",{"name":5,"description":7},"main","3fae1eb45ba1a7fbd4818527f48b439991a273da","plugin\u002Fskills\u002Fchildhood","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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Prasanth595\u002Fclaude-mem-mirror --skill childhood",{"tool":38,"command":39},"bunx","bunx skills add Prasanth595\u002Fclaude-mem-mirror --skill childhood",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Prasanth595\u002Fclaude-mem-mirror --skill childhood","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrasanth595\u002Fclaude-mem-mirror\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fchildhood\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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",[],[]]