[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7384FK6EC7SV0REFGZ6KNKJ":3,"skill-same:01M7384FK6EC7SV0REFGZ6KNKJ":59},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7384FK6EC7SV0REFGZ6KNKJ","decommission-validated-system",null,"Decommission a validated computerized system at end-of-life. Covers data retention assessment by regulation, data migration validation (mapping, transformation, reconciliation), archival strategy, access revocation, documentation archival, and stakeholder notification. Use when a validated system is being replaced, reaching end-of-life without replacement, vendor support is discontinued, multiple systems are consolidating, or regulatory changes render a system obsolete.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdecommission-validated-system\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: decommission-validated-system\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-04-19\"\ndescription: >\n  Decommission a validated computerized system at end-of-life. Covers data\n  retention assessment by regulation, data migration validation (mapping,\n  transformation, reconciliation), archival strategy, access revocation,\n  documentation archival, and stakeholder notification. Use when a validated\n  system is being replaced, reaching end-of-life without replacement, vendor\n  support is discontinued, multiple systems are consolidating, or regulatory\n  changes render a system obsolete.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: compliance\n  complexity: intermediate\n  language: multi\n  tags: gxp, decommission, data-retention, migration, archival, compliance\n---\n\n# Decommission Validated System\n\nPlan and execute the controlled retirement of a validated computerized system while preserving data integrity and meeting regulatory retention requirements.\n\n## When to Use\n\n- A validated system is being replaced by a new system\n- A system is reaching end-of-life with no replacement (business process eliminated)\n- Vendor discontinues support for a validated product\n- Consolidation of multiple systems into a single platform\n- Regulatory or business changes render a system obsolete\n\n## Inputs\n\n- **Required**: System to be decommissioned (name, version, validation status)\n- **Required**: Data retention requirements by regulation (21 CFR Part 11, GLP, GCP)\n- **Required**: Replacement system (if applicable) and migration scope\n- **Optional**: Current validation documentation package\n- **Optional**: Data volume and format inventory\n- **Optional**: Business owner and stakeholder list\n\n## Procedure\n\n### Step 1: Assess Data Retention Requirements\n\nDetermine how long data must be retained and in what form:\n\n```markdown\n# Data Retention Assessment\n## Document ID: DRA-[SYS]-[YYYY]-[NNN]\n\n### Regulatory Retention Requirements\n| Regulation | Data Type | Retention Period | Format Requirements |\n|-----------|-----------|-----------------|-------------------|\n| 21 CFR 211 (GMP) | Batch records, test results | 1 year past product expiry or 3 years after distribution | Readable, retrievable |\n| 21 CFR 58 (GLP) | Study data and records | Duration of study + retention agreement | Original or certified copy |\n| ICH E6 (GCP) | Clinical trial records | 2 years after last marketing approval or formal discontinuation | Accessible for inspection |\n| 21 CFR Part 11 | Electronic records | Per predicate rule | Original format or validated migration |\n| EU Annex 11 | Computerized system records | Per applicable GxP | Readable and available |\n| Tax\u002Ffinancial | Financial records | 7-10 years (jurisdiction-dependent) | Readable |\n\n### System Data Inventory\n| Data Category | Volume | Format | Retention Required Until | Disposition |\n|---------------|--------|--------|------------------------|-------------|\n| [e.g., Batch records] | [e.g., 50,000 records] | [e.g., Database + PDF reports] | [Date] | Migrate \u002F Archive \u002F Destroy |\n| [e.g., Audit trail] | [e.g., 2M entries] | [e.g., Database] | [Same as parent records] | Archive |\n| [e.g., User data] | [e.g., 200 profiles] | [e.g., LDAP\u002FDatabase] | [Employment + 2 years] | Anonymise and archive |\n```\n\n**Got:** Every data category has a defined retention period, format requirement, and planned disposition.\n**If fail:** If retention requirements are unclear, consult regulatory affairs and legal. Default to the longest applicable retention period.\n\n### Step 2: Plan Data Migration (If Applicable)\n\nIf data is migrating to a replacement system:\n\n```markdown\n# Data Migration Plan\n## Document ID: DMP-[SYS]-[YYYY]-[NNN]\n\n### Migration Scope\n| Source | Target | Data Category | Records | Migration Method |\n|--------|--------|---------------|---------|-----------------|\n| [Old system] | [New system] | [Category] | [Count] | ETL \u002F Manual \u002F API |\n\n### Data Mapping\n| Source Field | Source Format | Target Field | Target Format | Transformation |\n|-------------|-------------|-------------|---------------|---------------|\n| [e.g., test_result] | FLOAT(8,2) | [e.g., result_value] | DECIMAL(10,3) | Precision conversion |\n| [e.g., operator_id] | VARCHAR(20) | [e.g., user_id] | UUID | Lookup table mapping |\n\n### Validation Approach\n| Check | Method | Acceptance Criteria |\n|-------|--------|-------------------|\n| Record count reconciliation | Source count vs target count | 100% match |\n| Field-level comparison | Sample 5% of records, all fields | 100% match after transformation |\n| Checksum verification | Hash source vs target for key fields | Checksums match |\n| Business rule validation | Verify key calculations in target | Results match source |\n| Audit trail continuity | Verify historical audit trail migrated | All entries present with original timestamps |\n```\n\n**Got:** Migration plan includes mapping, transformation rules, and validation checks that prove data integrity was maintained.\n**If fail:** If migration validation fails, do not proceed to decommission. Fix the migration issues and re-validate.\n\n### Step 3: Define Archival Strategy\n\nFor data that will be archived rather than migrated:\n\n```markdown\n# Archival Strategy\n\n### Archive Format\n| Consideration | Decision | Rationale |\n|--------------|----------|-----------|\n| Format | [PDF\u002FA, CSV, XML, database backup] | [Why this format survives the retention period] |\n| Medium | [Network storage, cloud archive, tape, optical] | [Durability and accessibility] |\n| Encryption | [Yes\u002FNo — method if yes] | [Security vs long-term accessibility trade-off] |\n| Integrity verification | [SHA-256 checksums, periodic verification schedule] | [Prove archive is uncorrupted] |\n\n### Archive Verification\n- [ ] Archived data is readable without the source system\n- [ ] All required data categories are included in the archive\n- [ ] Checksums recorded at time of archival\n- [ ] Archive can be searched and retrieved within [defined SLA, e.g., 5 business days]\n- [ ] Periodic integrity checks scheduled (annually)\n\n### Archive Access\n| Role | Access Level | Authorisation |\n|------|-------------|--------------|\n| QA Director | Read access to all archived data | Standing authorisation |\n| Regulatory Affairs | Read access for inspection support | Standing authorisation |\n| System Owner (former) | Read access for business queries | Request-based |\n| External auditors | Read access, supervised | Per audit plan |\n```\n\n**Got:** Archived data is readable, searchable, and verifiable without the original system.\n**If fail:** If data cannot be read independently of the source system, the archive is not compliant. Consider exporting to an open, standard format (PDF\u002FA, CSV) before decommission.\n\n### Step 4: Execute Decommissioning\n\n```markdown\n# Decommission Checklist\n## Document ID: DC-[SYS]-[YYYY]-[NNN]\n\n### Pre-Decommission\n- [ ] All stakeholders notified of decommission date and data disposition\n- [ ] Data migration completed and validated (if applicable)\n- [ ] Data archive created and verified (if applicable)\n- [ ] Final backup of complete system taken and stored separately\n- [ ] All open change requests resolved or transferred\n- [ ] All open CAPAs resolved or transferred to successor system\n- [ ] All active users informed and redirected to replacement system (if applicable)\n\n### Decommission Execution\n- [ ] User access revoked for all accounts\n- [ ] System removed from production environment\n- [ ] Network connections disconnected\n- [ ] Licenses returned or terminated\n- [ ] System entry removed from active system inventory\n- [ ] System moved to \"Decommissioned\" status in compliance architecture\n\n### Post-Decommission\n- [ ] Validation documentation archived (URS, VP, IQ\u002FOQ\u002FPQ, TM, VSR)\n- [ ] SOPs retired or updated to remove references to decommissioned system\n- [ ] Training records archived\n- [ ] Change control records archived\n- [ ] Audit trail archived\n- [ ] Decommission report completed and approved\n\n### Decommission Report\n| Section | Content |\n|---------|---------|\n| System description | Name, version, purpose, GxP classification |\n| Decommission rationale | Why the system is being retired |\n| Data disposition summary | What data went where (migrated, archived, destroyed) |\n| Validation evidence | Migration validation results, archive verification |\n| Residual risk | Any ongoing data retention obligations |\n| Approval | System owner, QA, IT signatures |\n```\n\n**Got:** Decommissioning is controlled, documented, and approved — not just \"turn it off.\"\n**If fail:** If any checklist item cannot be completed, document the exception and obtain QA approval before proceeding.\n\n## Validation\n\n- [ ] Data retention requirements assessed for all data categories\n- [ ] Data migration validated with record counts, sampling, and checksums (if applicable)\n- [ ] Archive created in a format readable without the source system\n- [ ] Archive integrity verified with checksums\n- [ ] All user access revoked\n- [ ] Validation documentation archived with defined retention period\n- [ ] SOPs updated to remove references to decommissioned system\n- [ ] Decommission report approved by system owner, QA, and IT\n\n## Pitfalls\n\n- **Premature decommission**: Turning off a system before data migration is validated risks permanent data loss. Complete all validation before pulling the plug.\n- **Unreadable archives**: Storing data in a proprietary format that requires the original system to read defeats the purpose of archival. Use open formats.\n- **Forgotten audit trails**: Archiving the data but not the audit trail means the data provenance cannot be demonstrated. Always archive audit trails with their parent records.\n- **Orphaned SOPs**: SOPs that still reference a decommissioned system confuse users and create compliance gaps. Update or retire all affected SOPs.\n- **No periodic archive verification**: Archives degrade. Without periodic integrity checks, data loss may go undetected until the data is needed for an inspection.\n\n## Related Skills\n\n- `design-compliance-architecture` — update the system inventory and compliance architecture after decommission\n- `manage-change-control` — decommissioning is a major change requiring change control\n- `write-validation-documentation` — migration validation follows the same IQ\u002FOQ methodology\n- `write-standard-operating-procedure` — retire or update SOPs referencing the decommissioned system\n- `prepare-inspection-readiness` — archived data must remain accessible for regulatory inspections\n","# Decommission Validated System\n\nPlan and execute the controlled retirement of a validated computerized system while preserving data integrity and meeting regulatory retention requirements.\n\n## When to Use\n\n- A validated system is being replaced by a new system\n- A system is reaching end-of-life with no replacement (business process eliminated)\n- Vendor discontinues support for a validated product\n- Consolidation of multiple systems into a single platform\n- Regulatory or business changes render a system obsolete\n\n## Inputs\n\n- **Required**: System to be decommissioned (name, version, validation status)\n- **Required**: Data retention requirements by regulation (21 CFR Part 11, GLP, GCP)\n- **Required**: Replacement system (if applicable) and migration scope\n- **Optional**: Current validation documentation package\n- **Optional**: Data volume and format inventory\n- **Optional**: Business owner and stakeholder list\n\n## Procedure\n\n### Step 1: Assess Data Retention Requirements\n\nDetermine how long data must be retained and in what form:\n\n```markdown\n# Data Retention Assessment\n## Document ID: DRA-[SYS]-[YYYY]-[NNN]\n\n### Regulatory Retention Requirements\n| Regulation | Data Type | Retention Period | Format Requirements |\n|-----------|-----------|-----------------|-------------------|\n| 21 CFR 211 (GMP) | Batch records, test results | 1 year past product expiry or 3 years after distribution | Readable, retrievable |\n| 21 CFR 58 (GLP) | Study data and records | Duration of study + retention agreement | Original or certified copy |\n| ICH E6 (GCP) | Clinical trial records | 2 years after last marketing approval or formal discontinuation | Accessible for inspection |\n| 21 CFR Part 11 | Electronic records | Per predicate rule | Original format or validated migration |\n| EU Annex 11 | Computerized system records | Per applicable GxP | Readable and available |\n| Tax\u002Ffinancial | Financial records | 7-10 years (jurisdiction-dependent) | Readable |\n\n### System Data Inventory\n| Data Category | Volume | Format | Retention Required Until | Disposition |\n|---------------|--------|--------|------------------------|-------------|\n| [e.g., Batch records] | [e.g., 50,000 records] | [e.g., Database + PDF reports] | [Date] | Migrate \u002F Archive \u002F Destroy |\n| [e.g., Audit trail] | [e.g., 2M entries] | [e.g., Database] | [Same as parent records] | Archive |\n| [e.g., User data] | [e.g., 200 profiles] | [e.g., LDAP\u002FDatabase] | [Employment + 2 years] | Anonymise and archive |\n```\n\n**Got:** Every data category has a defined retention period, format requirement, and planned disposition.\n**If fail:** If retention requirements are unclear, consult regulatory affairs and legal. Default to the longest applicable retention period.\n\n### Step 2: Plan Data Migration (If Applicable)\n\nIf data is migrating to a replacement system:\n\n```markdown\n# Data Migration Plan\n## Document ID: DMP-[SYS]-[YYYY]-[NNN]\n\n### Migration Scope\n| Source | Target | Data Category | Records | Migration Method |\n|--------|--------|---------------|---------|-----------------|\n| [Old system] | [New system] | [Category] | [Count] | ETL \u002F Manual \u002F API |\n\n### Data Mapping\n| Source Field | Source Format | Target Field | Target Format | Transformation |\n|-------------|-------------|-------------|---------------|---------------|\n| [e.g., test_result] | FLOAT(8,2) | [e.g., result_value] | DECIMAL(10,3) | Precision conversion |\n| [e.g., operator_id] | VARCHAR(20) | [e.g., user_id] | UUID | Lookup table mapping |\n\n### Validation Approach\n| Check | Method | Acceptance Criteria |\n|-------|--------|-------------------|\n| Record count reconciliation | Source count vs target count | 100% match |\n| Field-level comparison | Sample 5% of records, all fields | 100% match after transformation |\n| Checksum verification | Hash source vs target for key fields | Checksums match |\n| Business rule validation | Verify key calculations in target | Results match source |\n| Audit trail continuity | Verify historical audit trail migrated | All entries present with original timestamps |\n```\n\n**Got:** Migration plan includes mapping, transformation rules, and validation checks that prove data integrity was maintained.\n**If fail:** If migration validation fails, do not proceed to decommission. Fix the migration issues and re-validate.\n\n### Step 3: Define Archival Strategy\n\nFor data that will be archived rather than migrated:\n\n```markdown\n# Archival Strategy\n\n### Archive Format\n| Consideration | Decision | Rationale |\n|--------------|----------|-----------|\n| Format | [PDF\u002FA, CSV, XML, database backup] | [Why this format survives the retention period] |\n| Medium | [Network storage, cloud archive, tape, optical] | [Durability and accessibility] |\n| Encryption | [Yes\u002FNo — method if yes] | [Security vs long-term accessibility trade-off] |\n| Integrity verification | [SHA-256 checksums, periodic verification schedule] | [Prove archive is uncorrupted] |\n\n### Archive Verification\n- [ ] Archived data is readable without the source system\n- [ ] All required data categories are included in the archive\n- [ ] Checksums recorded at time of archival\n- [ ] Archive can be searched and retrieved within [defined SLA, e.g., 5 business days]\n- [ ] Periodic integrity checks scheduled (annually)\n\n### Archive Access\n| Role | Access Level | Authorisation |\n|------|-------------|--------------|\n| QA Director | Read access to all archived data | Standing authorisation |\n| Regulatory Affairs | Read access for inspection support | Standing authorisation |\n| System Owner (former) | Read access for business queries | Request-based |\n| External auditors | Read access, supervised | Per audit plan |\n```\n\n**Got:** Archived data is readable, searchable, and verifiable without the original system.\n**If fail:** If data cannot be read independently of the source system, the archive is not compliant. Consider exporting to an open, standard format (PDF\u002FA, CSV) before decommission.\n\n### Step 4: Execute Decommissioning\n\n```markdown\n# Decommission Checklist\n## Document ID: DC-[SYS]-[YYYY]-[NNN]\n\n### Pre-Decommission\n- [ ] All stakeholders notified of decommission date and data disposition\n- [ ] Data migration completed and validated (if applicable)\n- [ ] Data archive created and verified (if applicable)\n- [ ] Final backup of complete system taken and stored separately\n- [ ] All open change requests resolved or transferred\n- [ ] All open CAPAs resolved or transferred to successor system\n- [ ] All active users informed and redirected to replacement system (if applicable)\n\n### Decommission Execution\n- [ ] User access revoked for all accounts\n- [ ] System removed from production environment\n- [ ] Network connections disconnected\n- [ ] Licenses returned or terminated\n- [ ] System entry removed from active system inventory\n- [ ] System moved to \"Decommissioned\" status in compliance architecture\n\n### Post-Decommission\n- [ ] Validation documentation archived (URS, VP, IQ\u002FOQ\u002FPQ, TM, VSR)\n- [ ] SOPs retired or updated to remove references to decommissioned system\n- [ ] Training records archived\n- [ ] Change control records archived\n- [ ] Audit trail archived\n- [ ] Decommission report completed and approved\n\n### Decommission Report\n| Section | Content |\n|---------|---------|\n| System description | Name, version, purpose, GxP classification |\n| Decommission rationale | Why the system is being retired |\n| Data disposition summary | What data went where (migrated, archived, destroyed) |\n| Validation evidence | Migration validation results, archive verification |\n| Residual risk | Any ongoing data retention obligations |\n| Approval | System owner, QA, IT signatures |\n```\n\n**Got:** Decommissioning is controlled, documented, and approved — not just \"turn it off.\"\n**If fail:** If any checklist item cannot be completed, document the exception and obtain QA approval before proceeding.\n\n## Validation\n\n- [ ] Data retention requirements assessed for all data categories\n- [ ] Data migration validated with record counts, sampling, and checksums (if applicable)\n- [ ] Archive created in a format readable without the source system\n- [ ] Archive integrity verified with checksums\n- [ ] All user access revoked\n- [ ] Validation documentation archived with defined retention period\n- [ ] SOPs updated to remove references to decommissioned system\n- [ ] Decommission report approved by system owner, QA, and IT\n\n## Pitfalls\n\n- **Premature decommission**: Turning off a system before data migration is validated risks permanent data loss. Complete all validation before pulling the plug.\n- **Unreadable archives**: Storing data in a proprietary format that requires the original system to read defeats the purpose of archival. Use open formats.\n- **Forgotten audit trails**: Archiving the data but not the audit trail means the data provenance cannot be demonstrated. Always archive audit trails with their parent records.\n- **Orphaned SOPs**: SOPs that still reference a decommissioned system confuse users and create compliance gaps. Update or retire all affected SOPs.\n- **No periodic archive verification**: Archives degrade. Without periodic integrity checks, data loss may go undetected until the data is needed for an inspection.\n\n## Related Skills\n\n- `design-compliance-architecture` — update the system inventory and compliance architecture after decommission\n- `manage-change-control` — decommissioning is a major change requiring change control\n- `write-validation-documentation` — migration validation follows the same IQ\u002FOQ methodology\n- `write-standard-operating-procedure` — retire or update SOPs referencing the decommissioned system\n- `prepare-inspection-readiness` — archived data must remain accessible for regulatory inspections\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"gxp, decommission, data-retention, migration, archival, compliance","Philipp Thoss","compliance","1.0","multi","intermediate","Julius Brussee homage — caveman","Decommission a validated computerized system at end-of-life. Covers data retention assessment by regulation, data migration validation (mapping, transformation, reconciliation), archival strategy, access revocation, documentation archival, and stakeholder notification. Use when a validated system is being replaced, reaching end-of-life without replacement, vendor support is discontinued, multiple systems are consolidating, or regulatory changes render a system obsolete.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-04-19","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fdecommission-validated-system",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill decommission-validated-system",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill decommission-validated-system",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill decommission-validated-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdecommission-validated-system\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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",[],[]]