[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BPNMD762QP98K60PJ2NP3":3,"skill-same:01M71BPNMD762QP98K60PJ2NP3":73},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M71BPNMD762QP98K60PJ2NP3","cyber-validating-backup-integrity-for-recovery",null,"Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-validating-backup-integrity-for-recovery\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"validating backup integrity for recovery","cyber validating backup integrity for recovery","for","backup","recovery","integrity","disaster recovery","restore","true","domain","restore-testing","ransomware response","disaster-recovery","subdomain","verification","ransomware","false","cybersecurity","testing","incident","2026-11-10 10:12:30",false,"---\nname: cyber-validating-backup-integrity-for-recovery\ndescription: \"Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.\"\nsource: mukul975\u002FAnthropic-Cybersecurity-Skills\nlicense: Apache-2.0\nauthorized_lab: false\norigin_frontmatter: \"name: validating-backup-integrity-for-recovery | description: Validate backup integrity through cryptographic hash verification, automated |   restore testing, corruption detection, and recoverability checks to ensure backups |   are reliable for disaster recovery and ransomware response scenarios. | domain: cybersecurity | subdomain: incident-response | tags: | - incident-response | - backup | - integrity | - hash-verification | - restore-testing | - disaster-recovery | version: '1.0' | author:\"\nhide: true\n---\n\n> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\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","> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\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",{"hide":49,"name":5,"source":50,"license":15,"description":7,"authorized_lab":45,"origin_frontmatter":51},true,"mukul975\u002FAnthropic-Cybersecurity-Skills","name: validating-backup-integrity-for-recovery | description: Validate backup integrity through cryptographic hash verification, automated |   restore testing, corruption detection, and recoverability checks to ensure backups |   are reliable for disaster recovery and ransomware response scenarios. | domain: cybersecurity | subdomain: incident-response | tags: | - incident-response | - backup | - integrity | - hash-verification | - restore-testing | - disaster-recovery | version: '1.0' | author:","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Fcyber-validating-backup-integrity-for-recovery",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-14 03:05:17",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-validating-backup-integrity-for-recovery",{"tool":66,"command":67},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-validating-backup-integrity-for-recovery",{"tool":69,"command":70},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-validating-backup-integrity-for-recovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-validating-backup-integrity-for-recovery\u002FSKILL.md",[],[74,97,120,148,177,196],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":44},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[82,83,84,85,86,87,88,32,89,90,91,92,93,94,95,96],"zoom out","zoom","with","harness","how","section","re","understand","use","perspective","when","you","code","it","context",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":44},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[104,105,85,106,107,26,108,109,110,111,112,90,113,92,114,115,116,117,118,119],"yuri shura","parallel","architecture review","planning","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":44},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",[130,131,132,133,134,135,136,137,138,92,139,140,141,142,143,144,145,26,146,147],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":162,"publishedAt":44},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[154,157],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[163,94,164,130,85,165,166,167,26,168,169,170,171,172,173,174,175,176,90,92],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":44},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[184,185,186,187,188,189,190,191,192,92,193,114,194,195],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":212,"publishedAt":44},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[202,203,206,209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":204,"categoryName":205,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":207,"categoryName":208,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":210,"categoryName":211,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000036","内容创作者",[213,214,215,92,114,216,85,217,108,90,218],"writing","writing skills","new","work","editing","Existing"]