[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73A8APF9YJZ5CKVM88ATNTP":3,"skill-same:01M73A8APF9YJZ5CKVM88ATNTP":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},"01M73A8APF9YJZ5CKVM88ATNTP","manage-change-control",null,"Manage change control for validated computerized systems. Covers change request triage (emergency, standard, minor), impact assessment on validated state, revalidation scope determination, approval workflows, implementation tracking, and post-change verification. Use when a validated system requires a software upgrade, patch, or configuration change; when infrastructure changes affect validated systems; when a CAPA requires system modification; or when emergency changes need expedited approval and retrospective documentation.","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\u002Fmanage-change-control\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: manage-change-control\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-04-24\"\ndescription: >\n  Manage change control for validated computerized systems. Covers change\n  request triage (emergency, standard, minor), impact assessment on validated\n  state, revalidation scope determination, approval workflows, implementation\n  tracking, and post-change verification. Use when a validated system requires\n  a software upgrade, patch, or configuration change; when infrastructure\n  changes affect validated systems; when a CAPA requires system modification;\n  or when emergency changes need expedited approval and retrospective\n  documentation.\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, change-control, revalidation, impact-assessment, compliance\n---\n\n# Manage Change Control\n\nEvaluate, approve, implement, and verify changes to validated computerized systems while maintaining their validated state.\n\n## When to Use\n\n- A validated system requires a software upgrade, patch, or configuration change\n- Infrastructure changes (server migration, OS upgrade, network change) affect validated systems\n- A CAPA or audit finding requires system modification\n- Business process changes require system reconfiguration\n- Emergency changes need expedited approval and retrospective documentation\n\n## Inputs\n\n- **Required**: Change description (what is changing and why)\n- **Required**: System(s) affected and their current validated state\n- **Required**: Change requestor and business justification\n- **Optional**: Vendor release notes or technical documentation\n- **Optional**: Related CAPA or audit finding references\n- **Optional**: Existing validation documentation for affected system(s)\n\n## Procedure\n\n### Step 1: Create and Classify the Change Request\n\n```markdown\n# Change Request\n## Document ID: CR-[SYS]-[YYYY]-[NNN]\n\n### 1. Change Description\n**Requestor:** [Name, Department]\n**Date:** [YYYY-MM-DD]\n**System:** [System name and version]\n**Current State:** [Current configuration\u002Fversion]\n**Proposed State:** [Target configuration\u002Fversion]\n\n### 2. Justification\n[Business, regulatory, or technical reason for the change]\n\n### 3. Classification\n| Type | Definition | Approval Path | Timeline |\n|------|-----------|--------------|----------|\n| **Emergency** | Urgent fix for safety, data integrity, or regulatory compliance | System owner + QA (retrospective CCB) | Implement immediately, document within 5 days |\n| **Standard** | Planned change with potential impact on validated state | CCB approval before implementation | Per CCB schedule |\n| **Minor** | Low-risk change with no impact on validated state | System owner approval | Documented before implementation |\n\n**This change is classified as:** [Emergency \u002F Standard \u002F Minor]\n**Rationale:** [Why this classification]\n```\n\n**Got:** Change request has a unique ID, clear description, and justified classification.\n**If fail:** If classification is disputed, default to Standard and let the CCB adjudicate.\n\n### Step 2: Perform Impact Assessment\n\nEvaluate the change against all dimensions of the validated state:\n\n```markdown\n# Impact Assessment\n## Change Request: CR-[SYS]-[YYYY]-[NNN]\n\n### Impact Matrix\n| Dimension | Affected? | Details | Risk |\n|-----------|-----------|---------|------|\n| Software configuration | Yes\u002FNo | [Specific parameters changing] | [H\u002FM\u002FL] |\n| Source code | Yes\u002FNo | [Modules, functions, or scripts affected] | [H\u002FM\u002FL] |\n| Database schema | Yes\u002FNo | [Tables, fields, constraints changing] | [H\u002FM\u002FL] |\n| Infrastructure | Yes\u002FNo | [Servers, network, storage affected] | [H\u002FM\u002FL] |\n| Interfaces | Yes\u002FNo | [Upstream\u002Fdownstream system connections] | [H\u002FM\u002FL] |\n| User access\u002Froles | Yes\u002FNo | [Role changes, new access requirements] | [H\u002FM\u002FL] |\n| SOPs\u002Fwork instructions | Yes\u002FNo | [Procedures requiring update] | [H\u002FM\u002FL] |\n| Training | Yes\u002FNo | [Users requiring retraining] | [H\u002FM\u002FL] |\n| Data migration | Yes\u002FNo | [Data transformation or migration needed] | [H\u002FM\u002FL] |\n| Audit trail | Yes\u002FNo | [Impact on audit trail continuity] | [H\u002FM\u002FL] |\n\n### Regulatory Impact\n- [ ] Change affects 21 CFR Part 11 controls\n- [ ] Change affects EU Annex 11 controls\n- [ ] Change affects data integrity (ALCOA+)\n- [ ] Change requires regulatory notification\n```\n\n**Got:** Every dimension is assessed with a clear yes\u002Fno and rationale.\n**If fail:** If impact cannot be determined without testing, classify the dimension as \"Unknown — requires investigation\" and mandate a sandbox evaluation before production change.\n\n### Step 3: Determine Revalidation Scope\n\nBased on the impact assessment, define what validation activities are needed:\n\n```markdown\n# Revalidation Determination\n\n| Revalidation Level | Criteria | Activities Required |\n|--------------------|----------|-------------------|\n| **Full revalidation** | Core functionality changed, new GAMP category, or major version upgrade | URS review, RA update, IQ, OQ, PQ, TM update, VSR |\n| **Partial revalidation** | Specific functions affected, configuration changes | Targeted OQ for affected functions, TM update |\n| **Documentation only** | No functional impact, administrative changes | Update validation documents, change log entry |\n| **None** | No impact on validated state (e.g., cosmetic change) | Change log entry only |\n\n### Determination for CR-[SYS]-[YYYY]-[NNN]\n**Revalidation level:** [Full \u002F Partial \u002F Documentation only \u002F None]\n**Rationale:** [Specific reasoning based on impact assessment]\n\n### Required Activities\n| Activity | Owner | Deadline |\n|----------|-------|----------|\n| [e.g., Execute OQ test cases TC-OQ-015 through TC-OQ-022] | [Name] | [Date] |\n| [e.g., Update traceability matrix for URS-007] | [Name] | [Date] |\n| [e.g., Update SOP-LIMS-003 section 4.2] | [Name] | [Date] |\n```\n\n**Got:** Revalidation scope is proportional to the change impact — no more, no less.\n**If fail:** If revalidation scope is contested, err on the side of more testing. Under-validation is a regulatory risk; over-validation is only a resource cost.\n\n### Step 4: Obtain Approval\n\nRoute the change through the appropriate approval workflow:\n\n```markdown\n# Change Approval\n\n### Approval for: CR-[SYS]-[YYYY]-[NNN]\n\n| Role | Name | Decision | Signature | Date |\n|------|------|----------|-----------|------|\n| System Owner | | Approve \u002F Reject \u002F Defer | | |\n| QA Representative | | Approve \u002F Reject \u002F Defer | | |\n| IT Representative | | Approve \u002F Reject \u002F Defer | | |\n| Validation Lead | | Approve \u002F Reject \u002F Defer | | |\n\n### Conditions (if any)\n[Any conditions attached to the approval]\n\n### Planned Implementation Window\n- **Start:** [Date\u002FTime]\n- **End:** [Date\u002FTime]\n- **Rollback deadline:** [Point of no return]\n```\n\n**Got:** All required approvers have signed before implementation begins (except emergency changes).\n**If fail:** For emergency changes, obtain verbal approval from system owner and QA, implement the change, and complete formal documentation within 5 business days.\n\n### Step 5: Implement and Verify\n\nExecute the change and perform post-change verification:\n\n```markdown\n# Implementation Record\n\n### Pre-Implementation\n- [ ] Backup of current system state completed\n- [ ] Rollback procedure documented and tested\n- [ ] Affected users notified\n- [ ] Test environment validated (if applicable)\n\n### Implementation\n- **Implemented by:** [Name]\n- **Date\u002FTime:** [YYYY-MM-DD HH:MM]\n- **Steps performed:** [Detailed implementation steps]\n- **Deviations from plan:** [None \u002F Description]\n\n### Post-Change Verification\n| Verification | Result | Evidence |\n|--------------|--------|----------|\n| System accessible and functional | Pass\u002FFail | [Screenshot\u002Flog reference] |\n| Changed functionality works as specified | Pass\u002FFail | [Test case reference] |\n| Unchanged functionality unaffected (regression) | Pass\u002FFail | [Test case reference] |\n| Audit trail continuity maintained | Pass\u002FFail | [Audit trail screenshot] |\n| User access controls intact | Pass\u002FFail | [Access review reference] |\n\n### Closure\n- [ ] All verification activities completed successfully\n- [ ] Validation documents updated per revalidation determination\n- [ ] SOPs updated and effective\n- [ ] Training completed for affected users\n- [ ] Change record closed in change control system\n```\n\n**Got:** Implementation matches the approved plan, and all verification activities pass.\n**If fail:** If verification fails, execute the rollback procedure immediately and document the failure as a deviation. Do not proceed without QA concurrence.\n\n## Validation\n\n- [ ] Change request has unique ID, description, and classification\n- [ ] Impact assessment covers all dimensions (software, data, infrastructure, SOPs, training)\n- [ ] Revalidation scope is defined with rationale\n- [ ] All required approvals obtained before implementation (or within 5 days for emergency)\n- [ ] Pre-implementation backup and rollback procedure documented\n- [ ] Post-change verification demonstrates the change works and nothing else broke\n- [ ] Validation documents updated to reflect the change\n- [ ] Change record formally closed\n\n## Pitfalls\n\n- **Skipping impact assessment for \"small\" changes**: Even minor changes can have unexpected impacts. A configuration toggle that seems harmless may disable an audit trail or change a calculation.\n- **Emergency change abuse**: If more than 10% of changes are classified as \"emergency,\" the change process is being circumvented. Review and tighten the emergency criteria.\n- **Incomplete rollback planning**: Assuming rollback is \"just restore the backup\" ignores data created between backup and rollback. Define data disposition for every rollback scenario.\n- **Approval after implementation**: Retrospective approval (except for documented emergencies) is a compliance violation. The CCB must approve before work begins.\n- **Missing regression testing**: Verifying only the changed functionality is insufficient. Regression testing must confirm that existing validated functions remain unaffected.\n\n## Related Skills\n\n- `design-compliance-architecture` — defines the governance framework including change control board\n- `write-validation-documentation` — create the revalidation documentation triggered by changes\n- `perform-csv-assessment` — full CSV reassessment for major changes requiring full revalidation\n- `write-standard-operating-procedure` — update SOPs affected by the change\n- `investigate-capa-root-cause` — when changes are triggered by CAPAs\n","# Manage Change Control\n\nEvaluate, approve, implement, and verify changes to validated computerized systems while maintaining their validated state.\n\n## When to Use\n\n- A validated system requires a software upgrade, patch, or configuration change\n- Infrastructure changes (server migration, OS upgrade, network change) affect validated systems\n- A CAPA or audit finding requires system modification\n- Business process changes require system reconfiguration\n- Emergency changes need expedited approval and retrospective documentation\n\n## Inputs\n\n- **Required**: Change description (what is changing and why)\n- **Required**: System(s) affected and their current validated state\n- **Required**: Change requestor and business justification\n- **Optional**: Vendor release notes or technical documentation\n- **Optional**: Related CAPA or audit finding references\n- **Optional**: Existing validation documentation for affected system(s)\n\n## Procedure\n\n### Step 1: Create and Classify the Change Request\n\n```markdown\n# Change Request\n## Document ID: CR-[SYS]-[YYYY]-[NNN]\n\n### 1. Change Description\n**Requestor:** [Name, Department]\n**Date:** [YYYY-MM-DD]\n**System:** [System name and version]\n**Current State:** [Current configuration\u002Fversion]\n**Proposed State:** [Target configuration\u002Fversion]\n\n### 2. Justification\n[Business, regulatory, or technical reason for the change]\n\n### 3. Classification\n| Type | Definition | Approval Path | Timeline |\n|------|-----------|--------------|----------|\n| **Emergency** | Urgent fix for safety, data integrity, or regulatory compliance | System owner + QA (retrospective CCB) | Implement immediately, document within 5 days |\n| **Standard** | Planned change with potential impact on validated state | CCB approval before implementation | Per CCB schedule |\n| **Minor** | Low-risk change with no impact on validated state | System owner approval | Documented before implementation |\n\n**This change is classified as:** [Emergency \u002F Standard \u002F Minor]\n**Rationale:** [Why this classification]\n```\n\n**Got:** Change request has a unique ID, clear description, and justified classification.\n**If fail:** If classification is disputed, default to Standard and let the CCB adjudicate.\n\n### Step 2: Perform Impact Assessment\n\nEvaluate the change against all dimensions of the validated state:\n\n```markdown\n# Impact Assessment\n## Change Request: CR-[SYS]-[YYYY]-[NNN]\n\n### Impact Matrix\n| Dimension | Affected? | Details | Risk |\n|-----------|-----------|---------|------|\n| Software configuration | Yes\u002FNo | [Specific parameters changing] | [H\u002FM\u002FL] |\n| Source code | Yes\u002FNo | [Modules, functions, or scripts affected] | [H\u002FM\u002FL] |\n| Database schema | Yes\u002FNo | [Tables, fields, constraints changing] | [H\u002FM\u002FL] |\n| Infrastructure | Yes\u002FNo | [Servers, network, storage affected] | [H\u002FM\u002FL] |\n| Interfaces | Yes\u002FNo | [Upstream\u002Fdownstream system connections] | [H\u002FM\u002FL] |\n| User access\u002Froles | Yes\u002FNo | [Role changes, new access requirements] | [H\u002FM\u002FL] |\n| SOPs\u002Fwork instructions | Yes\u002FNo | [Procedures requiring update] | [H\u002FM\u002FL] |\n| Training | Yes\u002FNo | [Users requiring retraining] | [H\u002FM\u002FL] |\n| Data migration | Yes\u002FNo | [Data transformation or migration needed] | [H\u002FM\u002FL] |\n| Audit trail | Yes\u002FNo | [Impact on audit trail continuity] | [H\u002FM\u002FL] |\n\n### Regulatory Impact\n- [ ] Change affects 21 CFR Part 11 controls\n- [ ] Change affects EU Annex 11 controls\n- [ ] Change affects data integrity (ALCOA+)\n- [ ] Change requires regulatory notification\n```\n\n**Got:** Every dimension is assessed with a clear yes\u002Fno and rationale.\n**If fail:** If impact cannot be determined without testing, classify the dimension as \"Unknown — requires investigation\" and mandate a sandbox evaluation before production change.\n\n### Step 3: Determine Revalidation Scope\n\nBased on the impact assessment, define what validation activities are needed:\n\n```markdown\n# Revalidation Determination\n\n| Revalidation Level | Criteria | Activities Required |\n|--------------------|----------|-------------------|\n| **Full revalidation** | Core functionality changed, new GAMP category, or major version upgrade | URS review, RA update, IQ, OQ, PQ, TM update, VSR |\n| **Partial revalidation** | Specific functions affected, configuration changes | Targeted OQ for affected functions, TM update |\n| **Documentation only** | No functional impact, administrative changes | Update validation documents, change log entry |\n| **None** | No impact on validated state (e.g., cosmetic change) | Change log entry only |\n\n### Determination for CR-[SYS]-[YYYY]-[NNN]\n**Revalidation level:** [Full \u002F Partial \u002F Documentation only \u002F None]\n**Rationale:** [Specific reasoning based on impact assessment]\n\n### Required Activities\n| Activity | Owner | Deadline |\n|----------|-------|----------|\n| [e.g., Execute OQ test cases TC-OQ-015 through TC-OQ-022] | [Name] | [Date] |\n| [e.g., Update traceability matrix for URS-007] | [Name] | [Date] |\n| [e.g., Update SOP-LIMS-003 section 4.2] | [Name] | [Date] |\n```\n\n**Got:** Revalidation scope is proportional to the change impact — no more, no less.\n**If fail:** If revalidation scope is contested, err on the side of more testing. Under-validation is a regulatory risk; over-validation is only a resource cost.\n\n### Step 4: Obtain Approval\n\nRoute the change through the appropriate approval workflow:\n\n```markdown\n# Change Approval\n\n### Approval for: CR-[SYS]-[YYYY]-[NNN]\n\n| Role | Name | Decision | Signature | Date |\n|------|------|----------|-----------|------|\n| System Owner | | Approve \u002F Reject \u002F Defer | | |\n| QA Representative | | Approve \u002F Reject \u002F Defer | | |\n| IT Representative | | Approve \u002F Reject \u002F Defer | | |\n| Validation Lead | | Approve \u002F Reject \u002F Defer | | |\n\n### Conditions (if any)\n[Any conditions attached to the approval]\n\n### Planned Implementation Window\n- **Start:** [Date\u002FTime]\n- **End:** [Date\u002FTime]\n- **Rollback deadline:** [Point of no return]\n```\n\n**Got:** All required approvers have signed before implementation begins (except emergency changes).\n**If fail:** For emergency changes, obtain verbal approval from system owner and QA, implement the change, and complete formal documentation within 5 business days.\n\n### Step 5: Implement and Verify\n\nExecute the change and perform post-change verification:\n\n```markdown\n# Implementation Record\n\n### Pre-Implementation\n- [ ] Backup of current system state completed\n- [ ] Rollback procedure documented and tested\n- [ ] Affected users notified\n- [ ] Test environment validated (if applicable)\n\n### Implementation\n- **Implemented by:** [Name]\n- **Date\u002FTime:** [YYYY-MM-DD HH:MM]\n- **Steps performed:** [Detailed implementation steps]\n- **Deviations from plan:** [None \u002F Description]\n\n### Post-Change Verification\n| Verification | Result | Evidence |\n|--------------|--------|----------|\n| System accessible and functional | Pass\u002FFail | [Screenshot\u002Flog reference] |\n| Changed functionality works as specified | Pass\u002FFail | [Test case reference] |\n| Unchanged functionality unaffected (regression) | Pass\u002FFail | [Test case reference] |\n| Audit trail continuity maintained | Pass\u002FFail | [Audit trail screenshot] |\n| User access controls intact | Pass\u002FFail | [Access review reference] |\n\n### Closure\n- [ ] All verification activities completed successfully\n- [ ] Validation documents updated per revalidation determination\n- [ ] SOPs updated and effective\n- [ ] Training completed for affected users\n- [ ] Change record closed in change control system\n```\n\n**Got:** Implementation matches the approved plan, and all verification activities pass.\n**If fail:** If verification fails, execute the rollback procedure immediately and document the failure as a deviation. Do not proceed without QA concurrence.\n\n## Validation\n\n- [ ] Change request has unique ID, description, and classification\n- [ ] Impact assessment covers all dimensions (software, data, infrastructure, SOPs, training)\n- [ ] Revalidation scope is defined with rationale\n- [ ] All required approvals obtained before implementation (or within 5 days for emergency)\n- [ ] Pre-implementation backup and rollback procedure documented\n- [ ] Post-change verification demonstrates the change works and nothing else broke\n- [ ] Validation documents updated to reflect the change\n- [ ] Change record formally closed\n\n## Pitfalls\n\n- **Skipping impact assessment for \"small\" changes**: Even minor changes can have unexpected impacts. A configuration toggle that seems harmless may disable an audit trail or change a calculation.\n- **Emergency change abuse**: If more than 10% of changes are classified as \"emergency,\" the change process is being circumvented. Review and tighten the emergency criteria.\n- **Incomplete rollback planning**: Assuming rollback is \"just restore the backup\" ignores data created between backup and rollback. Define data disposition for every rollback scenario.\n- **Approval after implementation**: Retrospective approval (except for documented emergencies) is a compliance violation. The CCB must approve before work begins.\n- **Missing regression testing**: Verifying only the changed functionality is insufficient. Regression testing must confirm that existing validated functions remain unaffected.\n\n## Related Skills\n\n- `design-compliance-architecture` — defines the governance framework including change control board\n- `write-validation-documentation` — create the revalidation documentation triggered by changes\n- `perform-csv-assessment` — full CSV reassessment for major changes requiring full revalidation\n- `write-standard-operating-procedure` — update SOPs affected by the change\n- `investigate-capa-root-cause` — when changes are triggered by CAPAs\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, change-control, revalidation, impact-assessment, compliance","Philipp Thoss","compliance","1.0","multi","intermediate","Julius Brussee homage — caveman","Manage change control for validated computerized systems. Covers change request triage (emergency, standard, minor), impact assessment on validated state, revalidation scope determination, approval workflows, implementation tracking, and post-change verification. Use when a validated system requires a software upgrade, patch, or configuration change; when infrastructure changes affect validated systems; when a CAPA requires system modification; or when emergency changes need expedited approval and retrospective documentation.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-04-24","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fmanage-change-control",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 manage-change-control",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill manage-change-control",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill manage-change-control","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fmanage-change-control\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",[],[]]