[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CXNSATTWHH7FP993EYPRB":3,"skill-same:01M73CXNSATTWHH7FP993EYPRB":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M73CXNSATTWHH7FP993EYPRB","utility-update-pm-skills",null,"Validates internet access, compares the locally installed pm-skills version against the latest public release, and updates local files with conflict-aware overwrite-or-skip options. Produces an update report listing changed files, skipped files, and new capabilities. Use when you want to bring a local pm-skills installation up to date.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Futility-update-pm-skills\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: utility-update-pm-skills\ndescription: Validates internet access, compares the locally installed pm-skills version against the latest public release, and updates local files with conflict-aware overwrite-or-skip options. Produces an update report listing changed files, skipped files, and new capabilities. Use when you want to bring a local pm-skills installation up to date.\nclassification: utility\nversion: \"1.0.0\"\nupdated: 2026-04-09\nlicense: Apache-2.0\nmetadata:\n  category: coordination\n  frameworks: [triple-diamond]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n\n# PM Skills Updater\n\nThis skill updates a local pm-skills installation to the latest public\nrelease. It validates connectivity, compares versions, detects local\nmodifications, gives the user control over conflict resolution, and\nproduces a structured update report documenting every change.\n\nThe updater operates in three phases:\n- **Pre-flight** -- validate internet access and determine version delta.\n- **Update** -- fetch the latest release and apply changes with\n  conflict-aware overwrite-or-skip logic.\n- **Report** -- generate a markdown report summarizing what changed,\n  what was skipped, and what new capabilities are available.\n\n## When to Use\n\n- When you want to update your local pm-skills to the latest release\n- After a new pm-skills version is announced and you want to pull it in\n- When you're unsure whether your local copy is current\n- When onboarding to a team that uses pm-skills and you want the latest version\n- When you want a structured summary of what changed between your version and the latest\n\n## When NOT to Use\n\n- To create or edit individual skills -> use `\u002Fpm-skill-builder` or `\u002Fpm-skill-iterate`\n- To validate skills against conventions -> use `\u002Fpm-skill-validate`\n- If you are a maintainer working directly on the pm-skills repo (use git instead)\n- If you need to pin a specific older version (this skill always targets the latest release)\n\n## Instructions\n\nWhen asked to update pm-skills, follow these steps:\n\n### Step 1: Validate Internet Access\n\nBefore attempting any remote operations, confirm connectivity to GitHub.\n\n**How to validate:**\n1. Attempt to reach the GitHub API or the public repository URL:\n   `https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills`\n2. Use any available method: `curl`, `wget`, `fetch`, GitHub CLI (`gh`),\n   or the GitHub MCP tools.\n\n**If connectivity fails:**\n- Report the failure clearly with the error details.\n- Suggest troubleshooting steps: check network, proxy settings, VPN,\n  or firewall rules.\n- Stop execution. Do not proceed to Step 2.\n\n**If connectivity succeeds:**\n- Report: \"Internet access validated. Connected to GitHub.\"\n- Proceed to Step 2.\n\n### Step 2: Determine Local Version\n\nRead the local version from these sources (in priority order):\n\n1. `.claude-plugin\u002Fplugin.json` -- `version` field\n2. `marketplace.json` -- `plugins[0].version` field\n3. `CHANGELOG.md` -- most recent version header\n4. Git tags -- most recent `v*` tag\n\nRecord:\n- **Local version**: the version string (e.g., `2.8.2`)\n- **Local version source**: which file provided the version\n\nIf no version can be determined, warn the user and default to `0.0.0`\n(treat as a fresh install requiring full update).\n\n### Step 3: Fetch Latest Public Release\n\nQuery the public repository for the latest release:\n\n**Methods (try in order):**\n1. GitHub API: `GET \u002Frepos\u002Fproduct-on-purpose\u002Fpm-skills\u002Freleases\u002Flatest`\n2. GitHub CLI: `gh release list --repo product-on-purpose\u002Fpm-skills --limit 1`\n3. Git: `git ls-remote --tags https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills.git`\n\nRecord:\n- **Latest version**: the version string from the latest release\n- **Release date**: when the release was published\n- **Release notes URL**: link to the release page\n- **Release notes body**: the release description (for capability diff in Step 8)\n\n### Step 4: Compare Versions\n\nCompare the local version against the latest public version.\n\n**If local version >= latest version:**\n- Report: \"Your pm-skills installation is up to date (v{local}).\"\n- Offer to generate a version report anyway (skip to Step 8 with\n  no changes to report).\n- Stop execution unless the user requests a forced update.\n\n**If local version \u003C latest version:**\n- Report the version delta:\n  ```\n  Local version:  v{local}\n  Latest version: v{latest}\n  Update type:    {major | minor | patch}\n  ```\n- If the update is a **major** version bump, warn:\n  \"This is a major version update. It may include breaking changes to\n  skill contracts. Review the release notes before proceeding.\"\n- Ask: \"Proceed with update? [yes \u002F no]\"\n- If no, stop execution.\n\n### Step 5: Scan for Local Modifications\n\nBefore fetching new files, scan the local installation for user\nmodifications. This protects customizations from being silently\noverwritten.\n\n**How to detect modifications:**\n\n1. **If the local install is a git repo** (preferred):\n   - Run `git status --porcelain` to find uncommitted changes.\n   - Run `git diff HEAD` to see the actual modifications.\n   - Any file with local changes is flagged as \"locally modified.\"\n\n2. **If the local install is NOT a git repo** (downloaded release):\n   - Compare file checksums (SHA-256) against a manifest if available.\n   - If no manifest is available, skip modification detection and note\n     this limitation in the report.\n\nRecord a list of locally modified files with their modification type:\n- `modified` -- content differs from the installed version\n- `added` -- file exists locally but not in the original release\n- `deleted` -- file was removed locally\n\nPresent the findings:\n```\nLocally modified files detected: {n}\n- {status} | {file-path}\n- {status} | {file-path}\n...\n```\n\nIf no modifications are detected, report: \"No local modifications\ndetected. Safe to update all files.\"\n\n### Step 6: Fetch and Apply Updates\n\nFetch the latest release content and apply updates file by file.\n\n**Update method (try in order):**\n1. **Git pull\u002Fmerge** (if local is a git repo):\n   - `git fetch origin`\n   - `git merge origin\u002Fmain` (or the tagged release)\n   - If merge conflicts arise, handle per the conflict resolution\n     rules below.\n\n2. **Release archive download** (if not a git repo):\n   - Download the release archive (`.tar.gz` or `.zip`).\n   - Extract to a temporary directory.\n   - Copy files to the local installation per the rules below.\n\n**File-by-file application rules:**\n\nFor each file in the update:\n\n| Local status | Action | User prompt |\n|-------------|--------|-------------|\n| Unmodified | Overwrite silently | None |\n| Locally modified | Prompt user | \"File `{path}` has local changes. [overwrite \u002F skip \u002F diff]\" |\n| New file (not in local) | Add silently | None |\n| Deleted locally | Prompt user | \"File `{path}` was deleted locally but exists in the update. [restore \u002F skip]\" |\n\n**Conflict resolution options:**\n- **overwrite**: Replace the local file with the upstream version.\n  The original is backed up to `{path}.local-backup` before overwriting.\n- **skip**: Keep the local version. Record as skipped in the report.\n- **diff**: Show a side-by-side or unified diff of the local vs. upstream\n  version, then re-prompt with [overwrite \u002F skip].\n- **restore**: Add the file back from the upstream version.\n- **overwrite-all**: Apply overwrite to all remaining conflicts without\n  further prompting.\n- **skip-all**: Apply skip to all remaining conflicts without further\n  prompting.\n\n### Step 7: Post-Update Validation\n\nAfter applying updates, run a quick health check:\n\n1. **Version consistency**: Verify that `.claude-plugin\u002Fplugin.json`,\n   `marketplace.json`, and `CHANGELOG.md` all reflect the new version.\n2. **File integrity**: Confirm that key files exist:\n   - `AGENTS.md`\n   - `skills\u002F` directory with expected skill count\n   - `commands\u002F` directory\n   - `_workflows\u002F` directory\n3. **Skill count delta**: Compare the number of skills before and after\n   the update. Report any additions or removals.\n\nIf validation fails, warn the user with specific details about what\nlooks wrong. Do not roll back automatically -- the user may want to\ninvestigate.\n\n### Step 8: Generate Update Report\n\nProduce the update report using the template in\n`references\u002FTEMPLATE.md`. This is the primary output artifact.\n\nThe report includes:\n\n1. **Version summary**: local (before) -> latest (after), update type.\n2. **Files changed**: every file that was updated, with a one-line\n   summary of what changed.\n3. **Files skipped**: files the user chose to skip due to local\n   modifications, with the reason.\n4. **Files added**: new files not present in the previous version.\n5. **Files removed**: files present in the old version but not in the\n   new one.\n6. **New capabilities**: skills added, skills updated (with version\n   deltas), workflows added, and any breaking changes -- derived from\n   release notes and file diff analysis.\n7. **Skipped file recovery**: instructions for how to manually update\n   any files that were skipped.\n\n**Report delivery:**\n- Display the report in the conversation.\n- Offer to save it as a file: `updates\u002Fupdate-{from}-to-{to}-{date}.md`\n  (e.g., `updates\u002Fupdate-v2.8.2-to-v2.9.0-2026-04-09.md`).\n\n### Step 9: Present Next Steps\n\nAfter the update completes, suggest next steps:\n\n```\n## Next Steps\n\n- Review the update report for any skipped files\n- Run `\u002Fpm-skill-validate --all` to verify skill integrity\n- Run local CI: `bash scripts\u002Flint-skills-frontmatter.sh`\n- Check the release notes for any migration steps: {release-url}\n- If you skipped files with local changes, consider merging manually\n```\n\n## Degraded Mode\n\nIf running in an environment without direct file system or network\naccess (e.g., MCP or embedded environment):\n\n1. **No network access**: Cannot perform the update. Report the\n   limitation and provide the user with manual update instructions:\n   - Link to the latest release page\n   - List the steps to download and extract manually\n2. **No file system access**: Cannot scan for local modifications or\n   write updated files. Provide:\n   - Version comparison (if the user pastes their local version info)\n   - Capability diff from release notes\n   - A checklist of files the user should update manually\n3. **Partial access**: Do what you can. Clearly note which steps were\n   skipped and why in the report.\n\n## Output Contract\n\nThe updater MUST produce an update report following the format in\n`references\u002FTEMPLATE.md`.\n\nThe report:\n- Uses the exact section headings defined in the template\n- Includes version information for both local and upstream\n- Lists every file with its disposition (updated, skipped, added, removed)\n- Describes new capabilities derived from the version delta\n- Provides recovery instructions for any skipped files\n\nThe updater MUST:\n- Validate internet access before attempting any remote operations\n- Determine the local version before comparing against upstream\n- Never silently overwrite a locally modified file\n- Back up locally modified files before overwriting (if user chooses overwrite)\n- Present a clear prompt for each conflict with diff capability\n- Support batch conflict resolution (overwrite-all \u002F skip-all)\n- Run post-update validation to confirm a healthy state\n\nThe updater MUST NOT:\n- Proceed without internet access confirmation\n- Overwrite locally modified files without user consent\n- Delete local files that don't exist in the upstream release\n- Auto-rollback on validation failure (inform the user instead)\n- Modify files outside the pm-skills directory\n\n## Quality Checklist\n\nBefore delivering the update report, verify:\n\n- [ ] Internet access was validated before any remote operations\n- [ ] Local version was correctly identified from available sources\n- [ ] Latest public version was fetched and compared\n- [ ] User was warned about major version updates (if applicable)\n- [ ] All locally modified files were detected and presented\n- [ ] User was prompted for each file conflict (or batch mode was used)\n- [ ] Backups were created for overwritten locally modified files\n- [ ] Post-update validation passed (or failures were reported)\n- [ ] Update report follows the template format exactly\n- [ ] New capabilities section accurately reflects the version delta\n- [ ] Skipped file recovery instructions are provided\n- [ ] Next steps are presented\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed update report demonstrating\na minor version update with local modifications, conflict resolution,\nand new capability discovery.\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n\n# PM Skills Updater\n\nThis skill updates a local pm-skills installation to the latest public\nrelease. It validates connectivity, compares versions, detects local\nmodifications, gives the user control over conflict resolution, and\nproduces a structured update report documenting every change.\n\nThe updater operates in three phases:\n- **Pre-flight** -- validate internet access and determine version delta.\n- **Update** -- fetch the latest release and apply changes with\n  conflict-aware overwrite-or-skip logic.\n- **Report** -- generate a markdown report summarizing what changed,\n  what was skipped, and what new capabilities are available.\n\n## When to Use\n\n- When you want to update your local pm-skills to the latest release\n- After a new pm-skills version is announced and you want to pull it in\n- When you're unsure whether your local copy is current\n- When onboarding to a team that uses pm-skills and you want the latest version\n- When you want a structured summary of what changed between your version and the latest\n\n## When NOT to Use\n\n- To create or edit individual skills -> use `\u002Fpm-skill-builder` or `\u002Fpm-skill-iterate`\n- To validate skills against conventions -> use `\u002Fpm-skill-validate`\n- If you are a maintainer working directly on the pm-skills repo (use git instead)\n- If you need to pin a specific older version (this skill always targets the latest release)\n\n## Instructions\n\nWhen asked to update pm-skills, follow these steps:\n\n### Step 1: Validate Internet Access\n\nBefore attempting any remote operations, confirm connectivity to GitHub.\n\n**How to validate:**\n1. Attempt to reach the GitHub API or the public repository URL:\n   `https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills`\n2. Use any available method: `curl`, `wget`, `fetch`, GitHub CLI (`gh`),\n   or the GitHub MCP tools.\n\n**If connectivity fails:**\n- Report the failure clearly with the error details.\n- Suggest troubleshooting steps: check network, proxy settings, VPN,\n  or firewall rules.\n- Stop execution. Do not proceed to Step 2.\n\n**If connectivity succeeds:**\n- Report: \"Internet access validated. Connected to GitHub.\"\n- Proceed to Step 2.\n\n### Step 2: Determine Local Version\n\nRead the local version from these sources (in priority order):\n\n1. `.claude-plugin\u002Fplugin.json` -- `version` field\n2. `marketplace.json` -- `plugins[0].version` field\n3. `CHANGELOG.md` -- most recent version header\n4. Git tags -- most recent `v*` tag\n\nRecord:\n- **Local version**: the version string (e.g., `2.8.2`)\n- **Local version source**: which file provided the version\n\nIf no version can be determined, warn the user and default to `0.0.0`\n(treat as a fresh install requiring full update).\n\n### Step 3: Fetch Latest Public Release\n\nQuery the public repository for the latest release:\n\n**Methods (try in order):**\n1. GitHub API: `GET \u002Frepos\u002Fproduct-on-purpose\u002Fpm-skills\u002Freleases\u002Flatest`\n2. GitHub CLI: `gh release list --repo product-on-purpose\u002Fpm-skills --limit 1`\n3. Git: `git ls-remote --tags https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills.git`\n\nRecord:\n- **Latest version**: the version string from the latest release\n- **Release date**: when the release was published\n- **Release notes URL**: link to the release page\n- **Release notes body**: the release description (for capability diff in Step 8)\n\n### Step 4: Compare Versions\n\nCompare the local version against the latest public version.\n\n**If local version >= latest version:**\n- Report: \"Your pm-skills installation is up to date (v{local}).\"\n- Offer to generate a version report anyway (skip to Step 8 with\n  no changes to report).\n- Stop execution unless the user requests a forced update.\n\n**If local version \u003C latest version:**\n- Report the version delta:\n  ```\n  Local version:  v{local}\n  Latest version: v{latest}\n  Update type:    {major | minor | patch}\n  ```\n- If the update is a **major** version bump, warn:\n  \"This is a major version update. It may include breaking changes to\n  skill contracts. Review the release notes before proceeding.\"\n- Ask: \"Proceed with update? [yes \u002F no]\"\n- If no, stop execution.\n\n### Step 5: Scan for Local Modifications\n\nBefore fetching new files, scan the local installation for user\nmodifications. This protects customizations from being silently\noverwritten.\n\n**How to detect modifications:**\n\n1. **If the local install is a git repo** (preferred):\n   - Run `git status --porcelain` to find uncommitted changes.\n   - Run `git diff HEAD` to see the actual modifications.\n   - Any file with local changes is flagged as \"locally modified.\"\n\n2. **If the local install is NOT a git repo** (downloaded release):\n   - Compare file checksums (SHA-256) against a manifest if available.\n   - If no manifest is available, skip modification detection and note\n     this limitation in the report.\n\nRecord a list of locally modified files with their modification type:\n- `modified` -- content differs from the installed version\n- `added` -- file exists locally but not in the original release\n- `deleted` -- file was removed locally\n\nPresent the findings:\n```\nLocally modified files detected: {n}\n- {status} | {file-path}\n- {status} | {file-path}\n...\n```\n\nIf no modifications are detected, report: \"No local modifications\ndetected. Safe to update all files.\"\n\n### Step 6: Fetch and Apply Updates\n\nFetch the latest release content and apply updates file by file.\n\n**Update method (try in order):**\n1. **Git pull\u002Fmerge** (if local is a git repo):\n   - `git fetch origin`\n   - `git merge origin\u002Fmain` (or the tagged release)\n   - If merge conflicts arise, handle per the conflict resolution\n     rules below.\n\n2. **Release archive download** (if not a git repo):\n   - Download the release archive (`.tar.gz` or `.zip`).\n   - Extract to a temporary directory.\n   - Copy files to the local installation per the rules below.\n\n**File-by-file application rules:**\n\nFor each file in the update:\n\n| Local status | Action | User prompt |\n|-------------|--------|-------------|\n| Unmodified | Overwrite silently | None |\n| Locally modified | Prompt user | \"File `{path}` has local changes. [overwrite \u002F skip \u002F diff]\" |\n| New file (not in local) | Add silently | None |\n| Deleted locally | Prompt user | \"File `{path}` was deleted locally but exists in the update. [restore \u002F skip]\" |\n\n**Conflict resolution options:**\n- **overwrite**: Replace the local file with the upstream version.\n  The original is backed up to `{path}.local-backup` before overwriting.\n- **skip**: Keep the local version. Record as skipped in the report.\n- **diff**: Show a side-by-side or unified diff of the local vs. upstream\n  version, then re-prompt with [overwrite \u002F skip].\n- **restore**: Add the file back from the upstream version.\n- **overwrite-all**: Apply overwrite to all remaining conflicts without\n  further prompting.\n- **skip-all**: Apply skip to all remaining conflicts without further\n  prompting.\n\n### Step 7: Post-Update Validation\n\nAfter applying updates, run a quick health check:\n\n1. **Version consistency**: Verify that `.claude-plugin\u002Fplugin.json`,\n   `marketplace.json`, and `CHANGELOG.md` all reflect the new version.\n2. **File integrity**: Confirm that key files exist:\n   - `AGENTS.md`\n   - `skills\u002F` directory with expected skill count\n   - `commands\u002F` directory\n   - `_workflows\u002F` directory\n3. **Skill count delta**: Compare the number of skills before and after\n   the update. Report any additions or removals.\n\nIf validation fails, warn the user with specific details about what\nlooks wrong. Do not roll back automatically -- the user may want to\ninvestigate.\n\n### Step 8: Generate Update Report\n\nProduce the update report using the template in\n`references\u002FTEMPLATE.md`. This is the primary output artifact.\n\nThe report includes:\n\n1. **Version summary**: local (before) -> latest (after), update type.\n2. **Files changed**: every file that was updated, with a one-line\n   summary of what changed.\n3. **Files skipped**: files the user chose to skip due to local\n   modifications, with the reason.\n4. **Files added**: new files not present in the previous version.\n5. **Files removed**: files present in the old version but not in the\n   new one.\n6. **New capabilities**: skills added, skills updated (with version\n   deltas), workflows added, and any breaking changes -- derived from\n   release notes and file diff analysis.\n7. **Skipped file recovery**: instructions for how to manually update\n   any files that were skipped.\n\n**Report delivery:**\n- Display the report in the conversation.\n- Offer to save it as a file: `updates\u002Fupdate-{from}-to-{to}-{date}.md`\n  (e.g., `updates\u002Fupdate-v2.8.2-to-v2.9.0-2026-04-09.md`).\n\n### Step 9: Present Next Steps\n\nAfter the update completes, suggest next steps:\n\n```\n## Next Steps\n\n- Review the update report for any skipped files\n- Run `\u002Fpm-skill-validate --all` to verify skill integrity\n- Run local CI: `bash scripts\u002Flint-skills-frontmatter.sh`\n- Check the release notes for any migration steps: {release-url}\n- If you skipped files with local changes, consider merging manually\n```\n\n## Degraded Mode\n\nIf running in an environment without direct file system or network\naccess (e.g., MCP or embedded environment):\n\n1. **No network access**: Cannot perform the update. Report the\n   limitation and provide the user with manual update instructions:\n   - Link to the latest release page\n   - List the steps to download and extract manually\n2. **No file system access**: Cannot scan for local modifications or\n   write updated files. Provide:\n   - Version comparison (if the user pastes their local version info)\n   - Capability diff from release notes\n   - A checklist of files the user should update manually\n3. **Partial access**: Do what you can. Clearly note which steps were\n   skipped and why in the report.\n\n## Output Contract\n\nThe updater MUST produce an update report following the format in\n`references\u002FTEMPLATE.md`.\n\nThe report:\n- Uses the exact section headings defined in the template\n- Includes version information for both local and upstream\n- Lists every file with its disposition (updated, skipped, added, removed)\n- Describes new capabilities derived from the version delta\n- Provides recovery instructions for any skipped files\n\nThe updater MUST:\n- Validate internet access before attempting any remote operations\n- Determine the local version before comparing against upstream\n- Never silently overwrite a locally modified file\n- Back up locally modified files before overwriting (if user chooses overwrite)\n- Present a clear prompt for each conflict with diff capability\n- Support batch conflict resolution (overwrite-all \u002F skip-all)\n- Run post-update validation to confirm a healthy state\n\nThe updater MUST NOT:\n- Proceed without internet access confirmation\n- Overwrite locally modified files without user consent\n- Delete local files that don't exist in the upstream release\n- Auto-rollback on validation failure (inform the user instead)\n- Modify files outside the pm-skills directory\n\n## Quality Checklist\n\nBefore delivering the update report, verify:\n\n- [ ] Internet access was validated before any remote operations\n- [ ] Local version was correctly identified from available sources\n- [ ] Latest public version was fetched and compared\n- [ ] User was warned about major version updates (if applicable)\n- [ ] All locally modified files were detected and presented\n- [ ] User was prompted for each file conflict (or batch mode was used)\n- [ ] Backups were created for overwritten locally modified files\n- [ ] Post-update validation passed (or failures were reported)\n- [ ] Update report follows the template format exactly\n- [ ] New capabilities section accurately reflects the version delta\n- [ ] Skipped file recovery instructions are provided\n- [ ] Next steps are presented\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed update report demonstrating\na minor version update with local modifications, conflict resolution,\nand new capability discovery.\n",{"name":5,"license":14,"updated":23,"version":24,"metadata":25,"description":7,"classification":30},1775692800000,"1.0.0",{"author":26,"category":27,"frameworks":28},"product-on-purpose","coordination",[29],"triple-diamond","utility","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Futility-update-pm-skills",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add roohe\u002Fagentic-super-skills --skill utility-update-pm-skills",{"tool":45,"command":46},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill utility-update-pm-skills",{"tool":48,"command":49},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill utility-update-pm-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Futility-update-pm-skills\u002FSKILL.md",true,[53,59],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002FEXAMPLE.md","REFERENCE","参考文档",7057,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Futility-update-pm-skills\u002Freferences\u002FEXAMPLE.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002FTEMPLATE.md",3856,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Futility-update-pm-skills\u002Freferences\u002FTEMPLATE.md",[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]