[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV1F1BHJX0DFY65493GF3F":3,"skill-same:01M7EV1F1BHJX0DFY65493GF3F":93},{"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":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":6,"ownerHtmlUrl":70,"ownerBlogUrl":6,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M7EV1F1BHJX0DFY65493GF3F","validating-backup-integrity-for-recovery",null,"Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: validating-backup-integrity-for-recovery\ndescription: Validates backup integrity through cryptographic hash verification,\n  automated restore testing, corruption detection, and recoverability checks to\n  confirm backups are reliable for disaster recovery and ransomware response. Use\n  before relying on backups for recovery, when building post-backup validation\n  pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped\n  backups for silent corruption or tampering.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- incident-response\n- backup\n- integrity\n- hash-verification\n- restore-testing\n- disaster-recovery\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.MA-01\n- RS.MA-02\n- RS.AN-03\n- RC.RP-01\nmitre_attack:\n- T1486\n- T1490\n- T1070\n- T1078\n- T1489\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - positioning\n  - monetization\n  techniques:\n  - id: T1531\n    name: Account Access Removal\n    tactic: positioning\n    source: attack\n  - id: F1018\n    name: Convert to Cryptocurrency\n    tactic: monetization\n    source: f3\n  - id: F1047\n    name: Transfer of funds\n    tactic: monetization\n    source: f3\n  - id: F1017.001\n    name: 'Conversion to Physical Monetary Instruments: Cash'\n    tactic: monetization\n    source: f3\n---\n# Validating Backup Integrity for Recovery\n\n## When to Use\n\nUse this skill when:\n- Verifying backup integrity before relying on backups for ransomware recovery\n- Building automated backup validation pipelines that run after each backup job\n- Auditing backup infrastructure to confirm recoverability for compliance (SOC 2, ISO 27001, NIST CSF RC.RP-03)\n- Detecting silent data corruption (bit rot) in backup storage before a disaster occurs\n- Validating that immutable or air-gapped backups have not been tampered with\n\n**Do not use** for initial backup configuration or scheduling. This skill focuses on post-backup validation.\n\n## Prerequisites\n\n- Access to backup storage (local, NAS, S3, Azure Blob, GCS)\n- Python 3.9+ with `hashlib` (standard library)\n- Backup manifests or baseline hash files for comparison\n- Isolated restore environment for restore testing\n- Backup tool CLI access (restic, borgbackup, rclone, or vendor-specific)\n\n## Workflow\n\n### Step 1: Generate Baseline Hash Manifest\n\nCreate a cryptographic fingerprint of every file at backup time:\n\n```bash\n# Generate SHA-256 manifest for a directory\nfind \u002Fdata\u002Fproduction -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Fprod_baseline_$(date +%Y%m%d).sha256\n\n# Verify manifest format\nhead -5 \u002Fmanifests\u002Fprod_baseline_20260319.sha256\n# e3b0c44298fc1c149afbf4c8996fb924...  \u002Fdata\u002Fproduction\u002Fconfig.yaml\n# a7ffc6f8bf1ed76651c14756a061d662...  \u002Fdata\u002Fproduction\u002Fdatabase.sql\n```\n\n### Step 2: Verify Backup Archive Integrity\n\nCheck that the backup archive itself is not corrupted:\n\n```bash\n# Restic: verify backup repository integrity\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket check --read-data\n\n# Borg: verify backup archive\nborg check --verify-data \u002Fbackup\u002Frepo::archive-2026-03-19\n\n# Tar with gzip: verify archive integrity\ngzip -t backup_20260319.tar.gz && echo \"Archive OK\" || echo \"Archive CORRUPTED\"\n\n# AWS S3: verify object checksums\naws s3api head-object --bucket backup-bucket --key daily\u002F2026-03-19.tar.gz \\\n  --checksum-mode ENABLED\n```\n\n### Step 3: Perform Restore Test to Isolated Environment\n\n```bash\n# Restore to isolated test directory\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket restore latest --target \u002Frestore-test\u002F\n\n# Generate hash manifest of restored data\nfind \u002Frestore-test -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Frestored_$(date +%Y%m%d).sha256\n\n# Compare baseline and restored manifests\ndiff \u003C(sort \u002Fmanifests\u002Fprod_baseline_20260319.sha256) \\\n     \u003C(sort \u002Fmanifests\u002Frestored_20260319.sha256)\n```\n\n### Step 4: Validate Data Completeness\n\n```bash\n# Count files in original vs restored\necho \"Original: $(find \u002Fdata\u002Fproduction -type f | wc -l) files\"\necho \"Restored: $(find \u002Frestore-test -type f | wc -l) files\"\n\n# Check total size\necho \"Original: $(du -sh \u002Fdata\u002Fproduction | cut -f1)\"\necho \"Restored: $(du -sh \u002Frestore-test | cut -f1)\"\n\n# Database consistency check after restore\npg_restore --list backup.dump | wc -l  # Count objects in dump\npsql -c \"SELECT schemaname, tablename FROM pg_tables WHERE schemaname='public';\" restored_db\n```\n\n### Step 5: Detect Ransomware Artifacts in Backups\n\nBefore trusting a backup for recovery, scan for ransomware indicators:\n\n```bash\n# Check for common ransomware file extensions\nfind \u002Frestore-test -type f \\( \\\n  -name \"*.encrypted\" -o -name \"*.locked\" -o -name \"*.crypt\" \\\n  -o -name \"*.ransom\" -o -name \"*.pay\" -o -name \"*.wncry\" \\\n  -o -name \"*.cerber\" -o -name \"*.locky\" -o -name \"*.zepto\" \\\n\\) -print\n\n# Check for ransom notes\nfind \u002Frestore-test -type f \\( \\\n  -name \"README_TO_DECRYPT*\" -o -name \"HOW_TO_RECOVER*\" \\\n  -o -name \"DECRYPT_INSTRUCTIONS*\" -o -name \"HELP_DECRYPT*\" \\\n\\) -print\n\n# Check file entropy (high entropy = possible encryption)\n# Files with entropy > 7.9 out of 8.0 are likely encrypted\npython agent.py --entropy-scan \u002Frestore-test\n```\n\n### Step 6: Automate and Schedule Validation\n\n```yaml\n# cron-based validation schedule\n# Run nightly after backup window\n0 4 * * * \u002Fopt\u002Fbackup-validator\u002Fagent.py --validate-latest --notify-on-failure\n# Weekly full restore test\n0 6 * * 0 \u002Fopt\u002Fbackup-validator\u002Fagent.py --full-restore-test --config \u002Fetc\u002Fbackup-validator\u002Fconfig.json\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Hash Manifest** | File containing cryptographic hashes (SHA-256) for every file in a dataset, used as integrity baseline |\n| **Bit Rot** | Gradual data corruption on storage media that silently alters file contents |\n| **Immutable Backup** | Backup that cannot be modified or deleted for a defined retention period |\n| **Restore Test** | Process of recovering data from backup to an isolated environment to verify recoverability |\n| **File Entropy** | Measure of randomness in file contents; encrypted files have entropy near 8.0 bits\u002Fbyte |\n| **3-2-1 Rule** | Keep 3 copies of data, on 2 different media types, with 1 offsite copy |\n| **Backup Chain** | Sequence of full and incremental backups that must all be intact for recovery |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Restic | Encrypted, deduplicated backup with built-in integrity verification |\n| BorgBackup | Deduplicating backup with archive verification |\n| Rclone | Cloud storage sync with checksum verification |\n| AWS S3 Object Lock | Immutable backup storage with WORM compliance |\n| Azure Immutable Blob | Tamper-proof backup storage for compliance |\n| sha256sum | Standard hash computation for file integrity |\n| pg_restore | PostgreSQL backup validation and restore testing |\n\n## Common Pitfalls\n\n- **Never testing restores**: The most common failure mode. Backups that are never restored are untested assumptions.\n- **Checking only archive integrity, not data integrity**: A valid tar.gz can contain corrupted file contents. Always hash individual files.\n- **Trusting last backup without scanning for ransomware**: Backups may contain encrypted files if the infection predates the backup.\n- **Ignoring incremental chain integrity**: A single corrupted incremental backup can break the entire restore chain.\n- **No alerting on validation failures**: Backup validation must be monitored with alerts, not just logged silently.\n- **Using MD5 for integrity**: MD5 is cryptographically broken. Use SHA-256 or SHA-3 for integrity verification.\n\n## References\n\n- NIST SP 800-184: Guide for Cybersecurity Event Recovery\n- NIST CSF 2.0 RC.RP-03: Backup Integrity Verification\n- CIS Controls v8: Control 11 - Data Recovery\n- CISA Ransomware Guide: https:\u002F\u002Fwww.cisa.gov\u002Fstopransomware\n","# Validating Backup Integrity for Recovery\n\n## When to Use\n\nUse this skill when:\n- Verifying backup integrity before relying on backups for ransomware recovery\n- Building automated backup validation pipelines that run after each backup job\n- Auditing backup infrastructure to confirm recoverability for compliance (SOC 2, ISO 27001, NIST CSF RC.RP-03)\n- Detecting silent data corruption (bit rot) in backup storage before a disaster occurs\n- Validating that immutable or air-gapped backups have not been tampered with\n\n**Do not use** for initial backup configuration or scheduling. This skill focuses on post-backup validation.\n\n## Prerequisites\n\n- Access to backup storage (local, NAS, S3, Azure Blob, GCS)\n- Python 3.9+ with `hashlib` (standard library)\n- Backup manifests or baseline hash files for comparison\n- Isolated restore environment for restore testing\n- Backup tool CLI access (restic, borgbackup, rclone, or vendor-specific)\n\n## Workflow\n\n### Step 1: Generate Baseline Hash Manifest\n\nCreate a cryptographic fingerprint of every file at backup time:\n\n```bash\n# Generate SHA-256 manifest for a directory\nfind \u002Fdata\u002Fproduction -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Fprod_baseline_$(date +%Y%m%d).sha256\n\n# Verify manifest format\nhead -5 \u002Fmanifests\u002Fprod_baseline_20260319.sha256\n# e3b0c44298fc1c149afbf4c8996fb924...  \u002Fdata\u002Fproduction\u002Fconfig.yaml\n# a7ffc6f8bf1ed76651c14756a061d662...  \u002Fdata\u002Fproduction\u002Fdatabase.sql\n```\n\n### Step 2: Verify Backup Archive Integrity\n\nCheck that the backup archive itself is not corrupted:\n\n```bash\n# Restic: verify backup repository integrity\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket check --read-data\n\n# Borg: verify backup archive\nborg check --verify-data \u002Fbackup\u002Frepo::archive-2026-03-19\n\n# Tar with gzip: verify archive integrity\ngzip -t backup_20260319.tar.gz && echo \"Archive OK\" || echo \"Archive CORRUPTED\"\n\n# AWS S3: verify object checksums\naws s3api head-object --bucket backup-bucket --key daily\u002F2026-03-19.tar.gz \\\n  --checksum-mode ENABLED\n```\n\n### Step 3: Perform Restore Test to Isolated Environment\n\n```bash\n# Restore to isolated test directory\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket restore latest --target \u002Frestore-test\u002F\n\n# Generate hash manifest of restored data\nfind \u002Frestore-test -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Frestored_$(date +%Y%m%d).sha256\n\n# Compare baseline and restored manifests\ndiff \u003C(sort \u002Fmanifests\u002Fprod_baseline_20260319.sha256) \\\n     \u003C(sort \u002Fmanifests\u002Frestored_20260319.sha256)\n```\n\n### Step 4: Validate Data Completeness\n\n```bash\n# Count files in original vs restored\necho \"Original: $(find \u002Fdata\u002Fproduction -type f | wc -l) files\"\necho \"Restored: $(find \u002Frestore-test -type f | wc -l) files\"\n\n# Check total size\necho \"Original: $(du -sh \u002Fdata\u002Fproduction | cut -f1)\"\necho \"Restored: $(du -sh \u002Frestore-test | cut -f1)\"\n\n# Database consistency check after restore\npg_restore --list backup.dump | wc -l  # Count objects in dump\npsql -c \"SELECT schemaname, tablename FROM pg_tables WHERE schemaname='public';\" restored_db\n```\n\n### Step 5: Detect Ransomware Artifacts in Backups\n\nBefore trusting a backup for recovery, scan for ransomware indicators:\n\n```bash\n# Check for common ransomware file extensions\nfind \u002Frestore-test -type f \\( \\\n  -name \"*.encrypted\" -o -name \"*.locked\" -o -name \"*.crypt\" \\\n  -o -name \"*.ransom\" -o -name \"*.pay\" -o -name \"*.wncry\" \\\n  -o -name \"*.cerber\" -o -name \"*.locky\" -o -name \"*.zepto\" \\\n\\) -print\n\n# Check for ransom notes\nfind \u002Frestore-test -type f \\( \\\n  -name \"README_TO_DECRYPT*\" -o -name \"HOW_TO_RECOVER*\" \\\n  -o -name \"DECRYPT_INSTRUCTIONS*\" -o -name \"HELP_DECRYPT*\" \\\n\\) -print\n\n# Check file entropy (high entropy = possible encryption)\n# Files with entropy > 7.9 out of 8.0 are likely encrypted\npython agent.py --entropy-scan \u002Frestore-test\n```\n\n### Step 6: Automate and Schedule Validation\n\n```yaml\n# cron-based validation schedule\n# Run nightly after backup window\n0 4 * * * \u002Fopt\u002Fbackup-validator\u002Fagent.py --validate-latest --notify-on-failure\n# Weekly full restore test\n0 6 * * 0 \u002Fopt\u002Fbackup-validator\u002Fagent.py --full-restore-test --config \u002Fetc\u002Fbackup-validator\u002Fconfig.json\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Hash Manifest** | File containing cryptographic hashes (SHA-256) for every file in a dataset, used as integrity baseline |\n| **Bit Rot** | Gradual data corruption on storage media that silently alters file contents |\n| **Immutable Backup** | Backup that cannot be modified or deleted for a defined retention period |\n| **Restore Test** | Process of recovering data from backup to an isolated environment to verify recoverability |\n| **File Entropy** | Measure of randomness in file contents; encrypted files have entropy near 8.0 bits\u002Fbyte |\n| **3-2-1 Rule** | Keep 3 copies of data, on 2 different media types, with 1 offsite copy |\n| **Backup Chain** | Sequence of full and incremental backups that must all be intact for recovery |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Restic | Encrypted, deduplicated backup with built-in integrity verification |\n| BorgBackup | Deduplicating backup with archive verification |\n| Rclone | Cloud storage sync with checksum verification |\n| AWS S3 Object Lock | Immutable backup storage with WORM compliance |\n| Azure Immutable Blob | Tamper-proof backup storage for compliance |\n| sha256sum | Standard hash computation for file integrity |\n| pg_restore | PostgreSQL backup validation and restore testing |\n\n## Common Pitfalls\n\n- **Never testing restores**: The most common failure mode. Backups that are never restored are untested assumptions.\n- **Checking only archive integrity, not data integrity**: A valid tar.gz can contain corrupted file contents. Always hash individual files.\n- **Trusting last backup without scanning for ransomware**: Backups may contain encrypted files if the infection predates the backup.\n- **Ignoring incremental chain integrity**: A single corrupted incremental backup can break the entire restore chain.\n- **No alerting on validation failures**: Backup validation must be monitored with alerts, not just logged silently.\n- **Using MD5 for integrity**: MD5 is cryptographically broken. Use SHA-256 or SHA-3 for integrity verification.\n\n## References\n\n- NIST SP 800-184: Guide for Cybersecurity Event Recovery\n- NIST CSF 2.0 RC.RP-03: Backup Integrity Verification\n- CIS Controls v8: Control 11 - Data Recovery\n- CISA Ransomware Guide: https:\u002F\u002Fwww.cisa.gov\u002Fstopransomware\n",{"name":5,"tags":24,"author":31,"domain":32,"license":15,"version":33,"mitre_f3":34,"nist_csf":54,"subdomain":25,"description":7,"mitre_attack":59},[25,26,27,28,29,30],"incident-response","backup","integrity","hash-verification","restore-testing","disaster-recovery","mahipal","cybersecurity","1.0",{"tactics":35,"version":38,"techniques":39},[36,37],"positioning","monetization","1.1",[40,44,48,51],{"id":41,"name":42,"source":43,"tactic":36},"T1531","Account Access Removal","attack",{"id":45,"name":46,"source":47,"tactic":37},"F1018","Convert to Cryptocurrency","f3",{"id":49,"name":50,"source":47,"tactic":37},"F1047","Transfer of funds",{"id":52,"name":53,"source":47,"tactic":37},"F1017.001","Conversion to Physical Monetary Instruments: Cash",[55,56,57,58],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01",[60,61,62,63,64],"T1486","T1490","T1070","T1078","T1489","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fvalidating-backup-integrity-for-recovery",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":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill validating-backup-integrity-for-recovery",{"tool":79,"command":80},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill validating-backup-integrity-for-recovery",{"tool":82,"command":83},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill validating-backup-integrity-for-recovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",true,[87],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fapi-reference.md","REFERENCE","参考文档",4005,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fvalidating-backup-integrity-for-recovery\u002Freferences\u002Fapi-reference.md",[94,103,108,115,122,129],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":102},"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.","MIT","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":104,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":102},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":102},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":102},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":102},"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":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":102},"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",[],[]]