[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7539HM95JX2DYYJ0KTHFPF3":3,"skill-same:01M7539HM95JX2DYYJ0KTHFPF3":74},{"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":38,"commitSha":39,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M7539HM95JX2DYYJ0KTHFPF3","mapping-mitre-attack-techniques",null,"Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.","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\u002Fmapping-mitre-attack-techniques\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fmapping-mitre-attack-techniques\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: mapping-mitre-attack-techniques\ndescription: >\n  Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK\n  techniques and sub-techniques to quantify detection coverage and guide control prioritization.\n  Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs,\n  aligning security controls to adversary playbooks, or reporting threat exposure to executives.\n  Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.\ndomain: cybersecurity\nsubdomain: threat-intelligence\ntags: [MITRE-ATT&CK, ATT&CK-Navigator, Sigma, D3FEND, TTP, detection-engineering, NIST-CSF]\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Mapping MITRE ATT&CK Techniques\n\n## When to Use\n\nUse this skill when:\n- Generating an ATT&CK coverage heatmap to show which techniques your detection stack addresses\n- Tagging existing SIEM use cases or Sigma rules with ATT&CK technique IDs for structured reporting\n- Aligning your security program roadmap to specific adversary groups known to target your sector\n\n**Do not use** this skill for real-time incident triage — ATT&CK mapping is an analytical activity best performed post-detection or during threat hunting planning.\n\n## Prerequisites\n\n- Access to MITRE ATT&CK knowledge base (https:\u002F\u002Fattack.mitre.org) or local ATT&CK STIX data bundle\n- ATT&CK Navigator web app or local installation (https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F)\n- Inventory of existing detection rules (Sigma, Splunk, Sentinel KQL) to assess current coverage\n- ATT&CK Python library: `pip install mitreattack-python`\n\n## Workflow\n\n### Step 1: Obtain Current ATT&CK Data\n\nDownload the latest ATT&CK STIX bundle for the relevant matrix (Enterprise, Mobile, ICS):\n```bash\ncurl -o enterprise-attack.json \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fmitre\u002Fcti\u002Fmaster\u002Fenterprise-attack\u002Fenterprise-attack.json\n```\n\nUse the mitreattack-python library to query techniques programmatically:\n```python\nfrom mitreattack.stix20 import MitreAttackData\n\nmitre = MitreAttackData(\"enterprise-attack.json\")\ntechniques = mitre.get_techniques(remove_revoked_deprecated=True)\nfor t in techniques[:5]:\n    print(t[\"external_references\"][0][\"external_id\"], t[\"name\"])\n```\n\n### Step 2: Map Existing Detections to Techniques\n\nFor each SIEM rule or Sigma file, assign ATT&CK technique IDs. Sigma rules support native ATT&CK tagging:\n```yaml\ntags:\n  - attack.execution\n  - attack.t1059.001  # PowerShell\n  - attack.t1059.003  # Windows Command Shell\n```\n\nCreate a coverage matrix: list each technique ID and mark as: Detected (alert fires), Logged (data present but no alert), Blind (no data source).\n\n### Step 3: Prioritize Coverage Gaps Using Threat Intelligence\n\nCross-reference coverage gaps with adversary groups targeting your sector. Use ATT&CK Groups data:\n```python\ngroups = mitre.get_groups()\napt29 = mitre.get_object_by_attack_id(\"G0016\", \"groups\")\napt29_techniques = mitre.get_techniques_used_by_group(apt29)\nfor t in apt29_techniques:\n    print(t[\"object\"][\"external_references\"][0][\"external_id\"])\n```\n\nPrioritize adding detection for techniques used by high-priority threat groups where your coverage is blind.\n\n### Step 4: Build Navigator Heatmap\n\nExport coverage scores as ATT&CK Navigator JSON layer:\n```python\nimport json\n\nlayer = {\n    \"name\": \"SOC Detection Coverage Q1 2025\",\n    \"versions\": {\"attack\": \"14\", \"navigator\": \"4.9\", \"layer\": \"4.5\"},\n    \"domain\": \"enterprise-attack\",\n    \"techniques\": [\n        {\"techniqueID\": \"T1059.001\", \"score\": 100, \"comment\": \"Splunk rule: PS_Encoded_Command\"},\n        {\"techniqueID\": \"T1071.001\", \"score\": 50, \"comment\": \"Logged only, no alert\"},\n        {\"techniqueID\": \"T1055\", \"score\": 0, \"comment\": \"No coverage — blind spot\"}\n    ],\n    \"gradient\": {\"colors\": [\"#ff6666\", \"#ffe766\", \"#8ec843\"], \"minValue\": 0, \"maxValue\": 100}\n}\nwith open(\"coverage_layer.json\", \"w\") as f:\n    json.dump(layer, f)\n```\n\nImport layer into ATT&CK Navigator (https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F) for visualization.\n\n### Step 5: Generate Executive Coverage Report\n\nSummarize coverage by tactic category (Initial Access, Execution, Persistence, etc.) with counts and percentages. Provide a risk-ranked list of top 10 blind-spot techniques based on adversary group usage frequency. Recommend data source additions (e.g., \"Enable PowerShell Script Block Logging to address 12 Execution sub-technique gaps\").\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **ATT&CK Technique** | Specific adversary method identified by T-number (e.g., T1059 = Command and Scripting Interpreter) |\n| **Sub-technique** | More granular variant of a technique (e.g., T1059.001 = PowerShell, T1059.003 = Windows Command Shell) |\n| **Tactic** | Adversary goal category in ATT&CK: Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Credential Access, Discovery, Lateral Movement, Collection, C&C, Exfiltration, Impact |\n| **Data Source** | ATT&CK v10+ component identifying telemetry required to detect a technique (e.g., Process Creation, Network Traffic) |\n| **Coverage Score** | Numeric (0–100) representing detection completeness for a technique: 0=blind, 50=logged only, 100=alerted |\n| **MITRE D3FEND** | Defensive countermeasure ontology complementing ATT&CK — maps defensive techniques to attack techniques they mitigate |\n\n## Tools & Systems\n\n- **ATT&CK Navigator**: Browser-based heatmap visualization tool for layering coverage scores and annotations on the ATT&CK matrix\n- **mitreattack-python**: Official MITRE Python library for programmatic access to ATT&CK STIX data (techniques, groups, software, mitigations)\n- **Atomic Red Team**: MITRE-aligned test library providing atomic test cases to validate detection for each technique\n- **Sigma**: Detection rule format with ATT&CK tagging support; translatable to Splunk, Sentinel, QRadar, Elastic\n- **ATT&CK Workbench**: Self-hosted ATT&CK knowledge base for organizations maintaining custom technique extensions\n\n## Common Pitfalls\n\n- **Over-claiming coverage**: Logging a data source (e.g., process creation events) does not mean the associated technique is detected — a rule must actually fire on malicious patterns.\n- **Mapping at tactic level only**: Tagging a rule as \"attack.execution\" without a specific technique ID prevents granular gap analysis.\n- **Ignoring sub-techniques**: Many adversaries use specific sub-techniques. Coverage of T1059 (parent) doesn't imply coverage of T1059.005 (Visual Basic).\n- **Static mapping without updates**: ATT&CK releases major versions annually. Coverage maps go stale as techniques are added, revised, or deprecated.\n- **Not mapping to adversary groups**: Generic coverage maps don't distinguish between techniques used by APTs targeting your sector vs. commodity malware.\n","# Mapping MITRE ATT&CK Techniques\n\n## When to Use\n\nUse this skill when:\n- Generating an ATT&CK coverage heatmap to show which techniques your detection stack addresses\n- Tagging existing SIEM use cases or Sigma rules with ATT&CK technique IDs for structured reporting\n- Aligning your security program roadmap to specific adversary groups known to target your sector\n\n**Do not use** this skill for real-time incident triage — ATT&CK mapping is an analytical activity best performed post-detection or during threat hunting planning.\n\n## Prerequisites\n\n- Access to MITRE ATT&CK knowledge base (https:\u002F\u002Fattack.mitre.org) or local ATT&CK STIX data bundle\n- ATT&CK Navigator web app or local installation (https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F)\n- Inventory of existing detection rules (Sigma, Splunk, Sentinel KQL) to assess current coverage\n- ATT&CK Python library: `pip install mitreattack-python`\n\n## Workflow\n\n### Step 1: Obtain Current ATT&CK Data\n\nDownload the latest ATT&CK STIX bundle for the relevant matrix (Enterprise, Mobile, ICS):\n```bash\ncurl -o enterprise-attack.json \\\n  https:\u002F\u002Fraw.githubusercontent.com\u002Fmitre\u002Fcti\u002Fmaster\u002Fenterprise-attack\u002Fenterprise-attack.json\n```\n\nUse the mitreattack-python library to query techniques programmatically:\n```python\nfrom mitreattack.stix20 import MitreAttackData\n\nmitre = MitreAttackData(\"enterprise-attack.json\")\ntechniques = mitre.get_techniques(remove_revoked_deprecated=True)\nfor t in techniques[:5]:\n    print(t[\"external_references\"][0][\"external_id\"], t[\"name\"])\n```\n\n### Step 2: Map Existing Detections to Techniques\n\nFor each SIEM rule or Sigma file, assign ATT&CK technique IDs. Sigma rules support native ATT&CK tagging:\n```yaml\ntags:\n  - attack.execution\n  - attack.t1059.001  # PowerShell\n  - attack.t1059.003  # Windows Command Shell\n```\n\nCreate a coverage matrix: list each technique ID and mark as: Detected (alert fires), Logged (data present but no alert), Blind (no data source).\n\n### Step 3: Prioritize Coverage Gaps Using Threat Intelligence\n\nCross-reference coverage gaps with adversary groups targeting your sector. Use ATT&CK Groups data:\n```python\ngroups = mitre.get_groups()\napt29 = mitre.get_object_by_attack_id(\"G0016\", \"groups\")\napt29_techniques = mitre.get_techniques_used_by_group(apt29)\nfor t in apt29_techniques:\n    print(t[\"object\"][\"external_references\"][0][\"external_id\"])\n```\n\nPrioritize adding detection for techniques used by high-priority threat groups where your coverage is blind.\n\n### Step 4: Build Navigator Heatmap\n\nExport coverage scores as ATT&CK Navigator JSON layer:\n```python\nimport json\n\nlayer = {\n    \"name\": \"SOC Detection Coverage Q1 2025\",\n    \"versions\": {\"attack\": \"14\", \"navigator\": \"4.9\", \"layer\": \"4.5\"},\n    \"domain\": \"enterprise-attack\",\n    \"techniques\": [\n        {\"techniqueID\": \"T1059.001\", \"score\": 100, \"comment\": \"Splunk rule: PS_Encoded_Command\"},\n        {\"techniqueID\": \"T1071.001\", \"score\": 50, \"comment\": \"Logged only, no alert\"},\n        {\"techniqueID\": \"T1055\", \"score\": 0, \"comment\": \"No coverage — blind spot\"}\n    ],\n    \"gradient\": {\"colors\": [\"#ff6666\", \"#ffe766\", \"#8ec843\"], \"minValue\": 0, \"maxValue\": 100}\n}\nwith open(\"coverage_layer.json\", \"w\") as f:\n    json.dump(layer, f)\n```\n\nImport layer into ATT&CK Navigator (https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F) for visualization.\n\n### Step 5: Generate Executive Coverage Report\n\nSummarize coverage by tactic category (Initial Access, Execution, Persistence, etc.) with counts and percentages. Provide a risk-ranked list of top 10 blind-spot techniques based on adversary group usage frequency. Recommend data source additions (e.g., \"Enable PowerShell Script Block Logging to address 12 Execution sub-technique gaps\").\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **ATT&CK Technique** | Specific adversary method identified by T-number (e.g., T1059 = Command and Scripting Interpreter) |\n| **Sub-technique** | More granular variant of a technique (e.g., T1059.001 = PowerShell, T1059.003 = Windows Command Shell) |\n| **Tactic** | Adversary goal category in ATT&CK: Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Credential Access, Discovery, Lateral Movement, Collection, C&C, Exfiltration, Impact |\n| **Data Source** | ATT&CK v10+ component identifying telemetry required to detect a technique (e.g., Process Creation, Network Traffic) |\n| **Coverage Score** | Numeric (0–100) representing detection completeness for a technique: 0=blind, 50=logged only, 100=alerted |\n| **MITRE D3FEND** | Defensive countermeasure ontology complementing ATT&CK — maps defensive techniques to attack techniques they mitigate |\n\n## Tools & Systems\n\n- **ATT&CK Navigator**: Browser-based heatmap visualization tool for layering coverage scores and annotations on the ATT&CK matrix\n- **mitreattack-python**: Official MITRE Python library for programmatic access to ATT&CK STIX data (techniques, groups, software, mitigations)\n- **Atomic Red Team**: MITRE-aligned test library providing atomic test cases to validate detection for each technique\n- **Sigma**: Detection rule format with ATT&CK tagging support; translatable to Splunk, Sentinel, QRadar, Elastic\n- **ATT&CK Workbench**: Self-hosted ATT&CK knowledge base for organizations maintaining custom technique extensions\n\n## Common Pitfalls\n\n- **Over-claiming coverage**: Logging a data source (e.g., process creation events) does not mean the associated technique is detected — a rule must actually fire on malicious patterns.\n- **Mapping at tactic level only**: Tagging a rule as \"attack.execution\" without a specific technique ID prevents granular gap analysis.\n- **Ignoring sub-techniques**: Many adversaries use specific sub-techniques. Coverage of T1059 (parent) doesn't imply coverage of T1059.005 (Visual Basic).\n- **Static mapping without updates**: ATT&CK releases major versions annually. Coverage maps go stale as techniques are added, revised, or deprecated.\n- **Not mapping to adversary groups**: Generic coverage maps don't distinguish between techniques used by APTs targeting your sector vs. commodity malware.\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"subdomain":36,"description":37},[26,27,28,29,30,31,32],"MITRE-ATT&CK","ATT&CK-Navigator","Sigma","D3FEND","TTP","detection-engineering","NIST-CSF","mahipal","cybersecurity","1.0.0","threat-intelligence","Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.\n","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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill mapping-mitre-attack-techniques",{"tool":50,"command":51},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill mapping-mitre-attack-techniques",{"tool":53,"command":54},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill mapping-mitre-attack-techniques","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fmapping-mitre-attack-techniques\u002FSKILL.md",true,[58,62,68],{"path":59,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fapi-reference.md","REFERENCE","参考文档",2708,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fmapping-mitre-attack-techniques\u002Freferences\u002Fapi-reference.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fagent.py","SCRIPT","脚本",7754,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fmapping-mitre-attack-techniques\u002Fscripts\u002Fagent.py",[75,83,90,97,104,111],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"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",[],[]]