[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ER0WK3FWRVGSBD5X176WGY":3,"skill-same:01M7ER0WK3FWRVGSBD5X176WGY":52},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7ER0WK3FWRVGSBD5X176WGY","repo-maintainer",null,"Audit and repair repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. Use for repository maintenance, cleanup, health checks, or pre-release hardening.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Frepo-maintainer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: repo-maintainer\ndescription: \"Audit and repair repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. Use for repository maintenance, cleanup, health checks, or pre-release hardening.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Ftree\u002Fmain\u002Fskills\u002Frepo-maintainer\nsource_repo: Wolfe-Jam\u002Ffaf-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Repository Maintainer\n\n## Overview\n\nAudit repository health, apply authorized repairs narrowly, and finish through the repository's own protected workflow.\n\n## When to Use\n\nUse when the user asks to maintain, clean, audit, harden, or prepare a repository for release. Use a more specific security, database, deployment, or release skill when that is the dominant task.\n\n## Repository Policy Gate\n\nBefore mutation:\n\n1. Read root and nested `AGENTS.md`, contributor guidance, maintainer docs, and release instructions.\n2. Inspect the current branch, worktree, staged files, remotes, default branch, and effective branch protection.\n3. Discover repository-native validation, synchronization, merge, and release commands.\n4. Preserve unrelated user work and generated outputs that are not in scope.\n\nIf the repository names a mandatory maintainer skill or guarded command, delegate to it instead of inventing a parallel branch, merge, sync, or release path. In `agentic-awesome-skills`, use `antigravity-maintainer-batch-release` and `npm run merge:batch`; `main` is pull-request-only.\n\nThe routine protected checks for `agentic-awesome-skills` are `pr-policy`, `pr-evidence`, `source-validation`, and `artifact-preview`. The supported AAS Core preview uses targeted unit tests plus one packed Linux\u002FNode LTS smoke path and Workbench review. Do not resurrect the retired certified-v1 baseline, benchmark, tuning-gold, transaction-fault, race, or frozen OS\u002Fruntime matrix as routine merge gates.\n\n## Usage\n\n### 1. Establish the baseline\n\n```bash\ngit status --short --branch\ngit diff --stat\ngit diff --cached --stat\ngit remote -v\ngit log -5 --oneline\n```\n\nRecord the repository's required runtime versions and test commands. Use a clean temporary clone or worktree when existing user changes cannot be isolated safely.\n\n### 2. Audit independent lanes\n\nRun independent read-only checks in parallel where possible.\n\n#### Artifacts and Git hygiene\n\n- untracked caches, coverage, build output, editor files, and test leftovers;\n- tracked large or binary files, accidental secrets, executable-mode drift, and ignored-file gaps;\n- stale branches, detached HEAD, existing staged changes, submodules, and symlinks;\n- generated files whose ownership belongs to CI or a canonical-sync workflow.\n\nDo not delete or rewrite history during the audit.\n\n#### Dependencies and packaging\n\n- lockfile and manifest agreement;\n- outdated, vulnerable, duplicate, unused, or end-of-life dependencies;\n- runtime imports incorrectly placed in development dependencies;\n- clean-install, package-content, and executable-entrypoint behavior.\n\nTreat audit-tool output as evidence to verify, not automatic permission to upgrade or remove packages.\n\n#### CI and release health\n\n- failing, cancelled, skipped, or stale workflow runs;\n- stale, redundant, or unjustifiably broad runtime matrices and unpinned or obsolete actions;\n- required checks, branch protection, release permissions, and secret boundaries;\n- mismatch between documented and implemented release commands.\n\n#### Documentation and repository metadata\n\n- README, changelog, version, examples, links, badges, credits, and support metadata;\n- contribution instructions and PR templates versus current CI policy;\n- generated catalog, site, or API documentation drift.\n\n#### Code-quality signals\n\n- dead code, stale implementation markers, debug logging, commented-out code, and missing tests;\n- unsafe defaults, suppressed errors, credential exposure, and environment-specific paths.\n\nFor FAF projects only, also inspect declared `.faf`, `.faf-dna`, sync, score, and MCP contracts with the project's installed FAF commands.\n\n### 3. Produce a prioritized decision set\n\nFor each finding report:\n\n- evidence and affected paths;\n- severity and user impact;\n- whether it is safe to fix now, needs approval, or belongs to another workflow;\n- exact validation that proves the repair.\n\nDeduplicate symptoms with the same root cause. Do not mix optional modernization with release blockers.\n\n### 4. Apply authorized repairs\n\nMake the smallest coherent change set. Keep source and generated-file ownership separate, update tests with behavior changes, and rerun the targeted failing check after each repair group.\n\nNever delete data, rewrite history, rotate credentials, change branch protection, or upgrade across breaking versions without explicit authorization.\n\n### 5. Validate and publish safely\n\nRun the repository's required pre-PR suite, then inspect the final diff for unrelated files and secrets. Commit on a topic branch and create a pull request when the target branch is protected.\n\nUse required checks and the repository-native merge path. A user request to “push to main” describes the desired final state; it does not bypass branch protection. For releases, use the scripted release workflow and verify external publication rather than inferring success from a local tag.\n\n## Stop Condition\n\nFinish when every in-scope finding is repaired or has one exact blocker, required validation passes, the remote integration path is verified when requested, and unrelated user work remains unchanged.\n\n## Limitations\n\n- Maintenance findings can depend on repository-specific ownership and release policy; read local instructions before acting.\n- Dependency and security scanners can produce false positives or incomplete reachability evidence.\n- This skill does not authorize destructive cleanup, branch-policy changes, direct protected-branch pushes, merges, deployments, or releases beyond the user's request.\n","# Repository Maintainer\n\n## Overview\n\nAudit repository health, apply authorized repairs narrowly, and finish through the repository's own protected workflow.\n\n## When to Use\n\nUse when the user asks to maintain, clean, audit, harden, or prepare a repository for release. Use a more specific security, database, deployment, or release skill when that is the dominant task.\n\n## Repository Policy Gate\n\nBefore mutation:\n\n1. Read root and nested `AGENTS.md`, contributor guidance, maintainer docs, and release instructions.\n2. Inspect the current branch, worktree, staged files, remotes, default branch, and effective branch protection.\n3. Discover repository-native validation, synchronization, merge, and release commands.\n4. Preserve unrelated user work and generated outputs that are not in scope.\n\nIf the repository names a mandatory maintainer skill or guarded command, delegate to it instead of inventing a parallel branch, merge, sync, or release path. In `agentic-awesome-skills`, use `antigravity-maintainer-batch-release` and `npm run merge:batch`; `main` is pull-request-only.\n\nThe routine protected checks for `agentic-awesome-skills` are `pr-policy`, `pr-evidence`, `source-validation`, and `artifact-preview`. The supported AAS Core preview uses targeted unit tests plus one packed Linux\u002FNode LTS smoke path and Workbench review. Do not resurrect the retired certified-v1 baseline, benchmark, tuning-gold, transaction-fault, race, or frozen OS\u002Fruntime matrix as routine merge gates.\n\n## Usage\n\n### 1. Establish the baseline\n\n```bash\ngit status --short --branch\ngit diff --stat\ngit diff --cached --stat\ngit remote -v\ngit log -5 --oneline\n```\n\nRecord the repository's required runtime versions and test commands. Use a clean temporary clone or worktree when existing user changes cannot be isolated safely.\n\n### 2. Audit independent lanes\n\nRun independent read-only checks in parallel where possible.\n\n#### Artifacts and Git hygiene\n\n- untracked caches, coverage, build output, editor files, and test leftovers;\n- tracked large or binary files, accidental secrets, executable-mode drift, and ignored-file gaps;\n- stale branches, detached HEAD, existing staged changes, submodules, and symlinks;\n- generated files whose ownership belongs to CI or a canonical-sync workflow.\n\nDo not delete or rewrite history during the audit.\n\n#### Dependencies and packaging\n\n- lockfile and manifest agreement;\n- outdated, vulnerable, duplicate, unused, or end-of-life dependencies;\n- runtime imports incorrectly placed in development dependencies;\n- clean-install, package-content, and executable-entrypoint behavior.\n\nTreat audit-tool output as evidence to verify, not automatic permission to upgrade or remove packages.\n\n#### CI and release health\n\n- failing, cancelled, skipped, or stale workflow runs;\n- stale, redundant, or unjustifiably broad runtime matrices and unpinned or obsolete actions;\n- required checks, branch protection, release permissions, and secret boundaries;\n- mismatch between documented and implemented release commands.\n\n#### Documentation and repository metadata\n\n- README, changelog, version, examples, links, badges, credits, and support metadata;\n- contribution instructions and PR templates versus current CI policy;\n- generated catalog, site, or API documentation drift.\n\n#### Code-quality signals\n\n- dead code, stale implementation markers, debug logging, commented-out code, and missing tests;\n- unsafe defaults, suppressed errors, credential exposure, and environment-specific paths.\n\nFor FAF projects only, also inspect declared `.faf`, `.faf-dna`, sync, score, and MCP contracts with the project's installed FAF commands.\n\n### 3. Produce a prioritized decision set\n\nFor each finding report:\n\n- evidence and affected paths;\n- severity and user impact;\n- whether it is safe to fix now, needs approval, or belongs to another workflow;\n- exact validation that proves the repair.\n\nDeduplicate symptoms with the same root cause. Do not mix optional modernization with release blockers.\n\n### 4. Apply authorized repairs\n\nMake the smallest coherent change set. Keep source and generated-file ownership separate, update tests with behavior changes, and rerun the targeted failing check after each repair group.\n\nNever delete data, rewrite history, rotate credentials, change branch protection, or upgrade across breaking versions without explicit authorization.\n\n### 5. Validate and publish safely\n\nRun the repository's required pre-PR suite, then inspect the final diff for unrelated files and secrets. Commit on a topic branch and create a pull request when the target branch is protected.\n\nUse required checks and the repository-native merge path. A user request to “push to main” describes the desired final state; it does not bypass branch protection. For releases, use the scripted release workflow and verify external publication rather than inferring success from a local tag.\n\n## Stop Condition\n\nFinish when every in-scope finding is repaired or has one exact blocker, required validation passes, the remote integration path is verified when requested, and unrelated user work remains unchanged.\n\n## Limitations\n\n- Maintenance findings can depend on repository-specific ownership and release policy; read local instructions before acting.\n- Dependency and security scanners can produce false positives or incomplete reachability evidence.\n- This skill does not authorize destructive cleanup, branch-policy changes, direct protected-branch pushes, merges, deployments, or releases beyond the user's request.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Ftree\u002Fmain\u002Fskills\u002Frepo-maintainer",1782864000000,"Wolfe-Jam\u002Ffaf-skills","community","https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Fblob\u002Fmain\u002FLICENSE","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Frepo-maintainer",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill repo-maintainer",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill repo-maintainer",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill repo-maintainer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Frepo-maintainer\u002FSKILL.md",true,[],[53,61,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":62,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":60},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":60},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":60},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":60},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":60},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]