[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751MVM5XK5F4KV7DY63EB6B":3,"skill-same:01M751MVM5XK5F4KV7DY63EB6B":89},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":35,"commitSha":36,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M751MVM5XK5F4KV7DY63EB6B","implementing-vulnerability-remediation-sla",null,"Vulnerability remediation SLAs define mandatory timeframes for patching or mitigating identified vulnerabilities based on severity, asset criticality, and exploit availability. Effective SLA programs","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: implementing-vulnerability-remediation-sla\ndescription: Vulnerability remediation SLAs define mandatory timeframes for patching or mitigating identified vulnerabilities based on severity, asset criticality, and exploit availability. Effective SLA programs \ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags: [vulnerability-management, cve, sla, remediation, patch-management, risk]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Implementing Vulnerability Remediation SLA\n\n## Overview\nVulnerability remediation SLAs define mandatory timeframes for patching or mitigating identified vulnerabilities based on severity, asset criticality, and exploit availability. Effective SLA programs drive accountability, ensure consistent remediation timelines, and provide measurable KPIs for vulnerability management maturity.\n\n\n## When to Use\n\n- When deploying or configuring implementing vulnerability remediation sla capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Vulnerability scanning program producing regular findings\n- Asset inventory with criticality classifications\n- Ticketing system (Jira, ServiceNow, etc.) for remediation tracking\n- Executive sponsorship for SLA enforcement\n- Cross-functional agreement from IT operations, development, and security\n\n## Core Concepts\n\n### SLA Framework Components\n1. **Severity Classification**: CVSS base score + threat context (EPSS, KEV)\n2. **Asset Tiering**: Business criticality and exposure level\n3. **Remediation Timeframes**: Maximum days to remediate by category\n4. **Exception Process**: Documented approval for SLA extensions\n5. **Escalation Procedures**: Actions when SLAs are breached\n6. **Metrics and Reporting**: KPIs for compliance tracking\n\n### Recommended SLA Matrix\n| Severity | Tier 1 (Critical) | Tier 2 (Important) | Tier 3 (Standard) |\n|----------|-------------------|--------------------|--------------------|\n| Critical (CVSS 9.0-10.0) | 24-48 hours | 72 hours | 7 days |\n| High (CVSS 7.0-8.9) | 7 days | 14 days | 30 days |\n| Medium (CVSS 4.0-6.9) | 30 days | 45 days | 60 days |\n| Low (CVSS 0.1-3.9) | 90 days | 90 days | 90 days |\n| CISA KEV Listed | 24 hours | 48 hours | 7 days |\n\n### SLA Accelerators (Reduce SLA by 50%)\n- Exploit code publicly available\n- Active exploitation observed in the wild (CISA KEV)\n- Internet-facing asset affected\n- EPSS score > 0.5 (50% exploitation probability)\n- Previous breach via similar vulnerability type\n\n## Workflow\n\n### Step 1: Define Asset Tiers\n```\nTier 1 (Critical Assets):\n- Customer-facing production systems\n- Payment processing infrastructure\n- Domain controllers and identity systems\n- Core network infrastructure (firewalls, routers)\n- Databases containing PII\u002FPHI\u002FPCI data\n\nTier 2 (Important Assets):\n- Internal production applications\n- Email and collaboration systems\n- Development\u002Fstaging environments with production data\n- Backup and recovery infrastructure\n- VPN and remote access gateways\n\nTier 3 (Standard Assets):\n- End-user workstations\n- Development\u002Ftest environments\n- Print servers and peripheral management\n- Non-critical internal tools\n```\n\n### Step 2: Establish SLA Policy Document\nKey sections to include:\n- Purpose and scope\n- Roles and responsibilities (RACI matrix)\n- Severity definitions and calculation method\n- Remediation timeframes by severity and asset tier\n- Exception request process and approval authority\n- Escalation procedures for SLA breaches\n- Metrics, reporting cadence, and governance\n- Policy review and update schedule\n\n### Step 3: Integrate with Ticketing System\n```python\n# ServiceNow \u002F Jira integration for automatic ticket creation\n# See process.py for full implementation\n\n# Key fields for remediation tickets:\n# - Vulnerability ID (CVE\u002FPlugin ID)\n# - Affected host(s)\n# - Severity (CVSS + contextual factors)\n# - Asset tier\n# - SLA deadline (calculated from discovery date)\n# - Assignment group\n# - Remediation instructions\n# - Verification criteria\n```\n\n### Step 4: Configure Escalation Chain\n```\nSLA Status          Action                          Notify\n───────────────────────────────────────────────────────────\n75% elapsed         Warning email                   Asset owner\n100% elapsed        SLA breach notification          Manager + CISO\n100% + 7 days       Executive escalation             VP\u002FCTO\n100% + 30 days      Risk acceptance required          CISO approval\n100% + 90 days      Compensating controls mandatory   Board report\n```\n\n### Step 5: Establish Exception Process\nValid exception reasons:\n- System cannot be patched without major downtime (scheduled maintenance window)\n- No vendor patch available (apply compensating controls)\n- Patch breaks critical functionality (require test results as evidence)\n- End-of-life system pending decommission (document risk acceptance)\n\nException requirements:\n- Written justification with business impact\n- Compensating controls documented and implemented\n- Approved by asset owner AND security leadership\n- Maximum exception duration: 90 days (renewable with re-approval)\n- Tracked in vulnerability management platform\n\n## Key Performance Indicators (KPIs)\n\n### Primary Metrics\n| KPI | Definition | Target |\n|-----|-----------|--------|\n| SLA Compliance Rate | % of vulns remediated within SLA | >90% |\n| Mean Time to Remediate (MTTR) | Average days from discovery to fix | Critical: \u003C3d, High: \u003C10d |\n| Vulnerability Backlog | Open vulnerabilities past SLA | \u003C5% of total |\n| Exception Rate | % of findings with active exceptions | \u003C10% |\n| Recurrence Rate | % of vulns that reappear after remediation | \u003C5% |\n\n### Trending Metrics\n- Month-over-month SLA compliance trend\n- MTTR trend by severity\n- Vulnerability density per asset (vulns\u002Fhost)\n- Patch coverage rate (% of assets scanned and compliant)\n- Time to first response (acknowledgment of finding)\n\n## Best Practices\n1. Start with achievable SLAs and tighten over time as maturity improves\n2. Use automated ticketing to eliminate manual SLA tracking\n3. Provide remediation teams with clear fix instructions, not just CVE numbers\n4. Track SLA compliance at the team\u002Fdepartment level for accountability\n5. Report SLA metrics to executive leadership monthly\n6. Include compensating controls as valid interim remediation\n7. Align SLAs with regulatory requirements (PCI DSS, HIPAA, SOX)\n8. Review and adjust SLAs annually based on threat landscape changes\n\n## Common Pitfalls\n- Setting unrealistic SLAs that teams cannot meet (creates SLA fatigue)\n- No executive enforcement of SLA breaches\n- Treating all assets equally without tiering\n- Not accounting for vulnerability context (EPSS, KEV) in SLA calculation\n- Missing exception management process (leads to untracked risk)\n- Measuring only compliance rate without analyzing root causes of breaches\n\n## Related Skills\n- prioritizing-vulnerabilities-with-cvss-scoring\n- implementing-patch-management-workflow\n- implementing-vulnerability-metrics-and-reporting\n- implementing-exception-management-process\n","# Implementing Vulnerability Remediation SLA\n\n## Overview\nVulnerability remediation SLAs define mandatory timeframes for patching or mitigating identified vulnerabilities based on severity, asset criticality, and exploit availability. Effective SLA programs drive accountability, ensure consistent remediation timelines, and provide measurable KPIs for vulnerability management maturity.\n\n\n## When to Use\n\n- When deploying or configuring implementing vulnerability remediation sla capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Vulnerability scanning program producing regular findings\n- Asset inventory with criticality classifications\n- Ticketing system (Jira, ServiceNow, etc.) for remediation tracking\n- Executive sponsorship for SLA enforcement\n- Cross-functional agreement from IT operations, development, and security\n\n## Core Concepts\n\n### SLA Framework Components\n1. **Severity Classification**: CVSS base score + threat context (EPSS, KEV)\n2. **Asset Tiering**: Business criticality and exposure level\n3. **Remediation Timeframes**: Maximum days to remediate by category\n4. **Exception Process**: Documented approval for SLA extensions\n5. **Escalation Procedures**: Actions when SLAs are breached\n6. **Metrics and Reporting**: KPIs for compliance tracking\n\n### Recommended SLA Matrix\n| Severity | Tier 1 (Critical) | Tier 2 (Important) | Tier 3 (Standard) |\n|----------|-------------------|--------------------|--------------------|\n| Critical (CVSS 9.0-10.0) | 24-48 hours | 72 hours | 7 days |\n| High (CVSS 7.0-8.9) | 7 days | 14 days | 30 days |\n| Medium (CVSS 4.0-6.9) | 30 days | 45 days | 60 days |\n| Low (CVSS 0.1-3.9) | 90 days | 90 days | 90 days |\n| CISA KEV Listed | 24 hours | 48 hours | 7 days |\n\n### SLA Accelerators (Reduce SLA by 50%)\n- Exploit code publicly available\n- Active exploitation observed in the wild (CISA KEV)\n- Internet-facing asset affected\n- EPSS score > 0.5 (50% exploitation probability)\n- Previous breach via similar vulnerability type\n\n## Workflow\n\n### Step 1: Define Asset Tiers\n```\nTier 1 (Critical Assets):\n- Customer-facing production systems\n- Payment processing infrastructure\n- Domain controllers and identity systems\n- Core network infrastructure (firewalls, routers)\n- Databases containing PII\u002FPHI\u002FPCI data\n\nTier 2 (Important Assets):\n- Internal production applications\n- Email and collaboration systems\n- Development\u002Fstaging environments with production data\n- Backup and recovery infrastructure\n- VPN and remote access gateways\n\nTier 3 (Standard Assets):\n- End-user workstations\n- Development\u002Ftest environments\n- Print servers and peripheral management\n- Non-critical internal tools\n```\n\n### Step 2: Establish SLA Policy Document\nKey sections to include:\n- Purpose and scope\n- Roles and responsibilities (RACI matrix)\n- Severity definitions and calculation method\n- Remediation timeframes by severity and asset tier\n- Exception request process and approval authority\n- Escalation procedures for SLA breaches\n- Metrics, reporting cadence, and governance\n- Policy review and update schedule\n\n### Step 3: Integrate with Ticketing System\n```python\n# ServiceNow \u002F Jira integration for automatic ticket creation\n# See process.py for full implementation\n\n# Key fields for remediation tickets:\n# - Vulnerability ID (CVE\u002FPlugin ID)\n# - Affected host(s)\n# - Severity (CVSS + contextual factors)\n# - Asset tier\n# - SLA deadline (calculated from discovery date)\n# - Assignment group\n# - Remediation instructions\n# - Verification criteria\n```\n\n### Step 4: Configure Escalation Chain\n```\nSLA Status          Action                          Notify\n───────────────────────────────────────────────────────────\n75% elapsed         Warning email                   Asset owner\n100% elapsed        SLA breach notification          Manager + CISO\n100% + 7 days       Executive escalation             VP\u002FCTO\n100% + 30 days      Risk acceptance required          CISO approval\n100% + 90 days      Compensating controls mandatory   Board report\n```\n\n### Step 5: Establish Exception Process\nValid exception reasons:\n- System cannot be patched without major downtime (scheduled maintenance window)\n- No vendor patch available (apply compensating controls)\n- Patch breaks critical functionality (require test results as evidence)\n- End-of-life system pending decommission (document risk acceptance)\n\nException requirements:\n- Written justification with business impact\n- Compensating controls documented and implemented\n- Approved by asset owner AND security leadership\n- Maximum exception duration: 90 days (renewable with re-approval)\n- Tracked in vulnerability management platform\n\n## Key Performance Indicators (KPIs)\n\n### Primary Metrics\n| KPI | Definition | Target |\n|-----|-----------|--------|\n| SLA Compliance Rate | % of vulns remediated within SLA | >90% |\n| Mean Time to Remediate (MTTR) | Average days from discovery to fix | Critical: \u003C3d, High: \u003C10d |\n| Vulnerability Backlog | Open vulnerabilities past SLA | \u003C5% of total |\n| Exception Rate | % of findings with active exceptions | \u003C10% |\n| Recurrence Rate | % of vulns that reappear after remediation | \u003C5% |\n\n### Trending Metrics\n- Month-over-month SLA compliance trend\n- MTTR trend by severity\n- Vulnerability density per asset (vulns\u002Fhost)\n- Patch coverage rate (% of assets scanned and compliant)\n- Time to first response (acknowledgment of finding)\n\n## Best Practices\n1. Start with achievable SLAs and tighten over time as maturity improves\n2. Use automated ticketing to eliminate manual SLA tracking\n3. Provide remediation teams with clear fix instructions, not just CVE numbers\n4. Track SLA compliance at the team\u002Fdepartment level for accountability\n5. Report SLA metrics to executive leadership monthly\n6. Include compensating controls as valid interim remediation\n7. Align SLAs with regulatory requirements (PCI DSS, HIPAA, SOX)\n8. Review and adjust SLAs annually based on threat landscape changes\n\n## Common Pitfalls\n- Setting unrealistic SLAs that teams cannot meet (creates SLA fatigue)\n- No executive enforcement of SLA breaches\n- Treating all assets equally without tiering\n- Not accounting for vulnerability context (EPSS, KEV) in SLA calculation\n- Missing exception management process (leads to untracked risk)\n- Measuring only compliance rate without analyzing root causes of breaches\n\n## Related Skills\n- prioritizing-vulnerabilities-with-cvss-scoring\n- implementing-patch-management-workflow\n- implementing-vulnerability-metrics-and-reporting\n- implementing-exception-management-process\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"subdomain":26,"description":7},[26,27,28,29,30,31],"vulnerability-management","cve","sla","remediation","patch-management","risk","mahipal","cybersecurity","1.0","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill implementing-vulnerability-remediation-sla",{"tool":47,"command":48},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill implementing-vulnerability-remediation-sla",{"tool":50,"command":51},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill implementing-vulnerability-remediation-sla","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002FSKILL.md",true,[55,61,65,71,75,79,85],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Ftemplate.md","ASSET","资产文件",1187,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002Fassets\u002Ftemplate.md",{"path":62,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fapi-reference.md","REFERENCE","参考文档",4825,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002Freferences\u002Fapi-reference.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fstandards.md",1158,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002Freferences\u002Fstandards.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fworkflows.md",1526,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002Freferences\u002Fworkflows.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fagent.py","SCRIPT","脚本",8796,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002Fscripts\u002Fagent.py",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fprocess.py",11013,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fimplementing-vulnerability-remediation-sla\u002Fscripts\u002Fprocess.py",[90,98,105,112,119,126],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":20},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":20},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]