[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A41MAZ90EC3WN4QGK37N2B":3,"skill-same:01M7A41MAZ90EC3WN4QGK37N2B":108},{"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":53,"commitSha":54,"skillDirectory":55,"forksCount":14,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M7A41MAZ90EC3WN4QGK37N2B","analyzing-threat-actor-ttps-with-mitre-attack",null,"Systematically map threat actor behavior and observed IOCs to the MITRE ATT&CK framework, build technique coverage heatmaps with the ATT&CK Navigator, identify detection gaps, and produce actionable threat intelligence reports across the Enterprise, Mobile, and ICS matrices. Use when analyzing threat actor TTPs, correlating IOCs to specific ATT&CK techniques, or assessing defensive detection coverage against adversary behavior.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyzing-threat-actor-ttps-with-mitre-attack\ndescription: Systematically map threat actor behavior and observed IOCs to the MITRE ATT&CK framework, build technique coverage heatmaps with the ATT&CK Navigator, identify detection gaps, and produce actionable threat intelligence reports across the Enterprise, Mobile, and ICS matrices. Use when analyzing threat actor TTPs, correlating IOCs to specific ATT&CK techniques, or assessing defensive detection coverage against adversary behavior.\ndomain: cybersecurity\nsubdomain: threat-intelligence\ntags:\n- threat-intelligence\n- cti\n- ioc\n- mitre-attack\n- stix\n- ttp-analysis\n- threat-actors\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- Executable Denylisting\n- Execution Isolation\n- File Metadata Consistency Validation\n- Content Format Conversion\n- File Content Analysis\nnist_csf:\n- ID.RA-01\n- ID.RA-05\n- DE.CM-01\n- DE.AE-02\nmitre_attack:\n- T1566.001\n- T1059.001\n- T1071.001\n- T1547.001\n- T1053.005\n---\n# Analyzing Threat Actor TTPs with MITRE ATT&CK\n\n## Overview\n\nMITRE ATT&CK is a globally-accessible knowledge base of adversary tactics, techniques, and procedures (TTPs) based on real-world observations. This skill covers systematically mapping threat actor behavior to the ATT&CK framework, building technique coverage heatmaps using the ATT&CK Navigator, identifying detection gaps, and producing actionable intelligence reports that link observed IOCs to specific adversary techniques across the Enterprise, Mobile, and ICS matrices.\n\n\n## When to Use\n\n- When investigating security incidents that require analyzing threat actor ttps with mitre attack\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n\n- Python 3.9+ with `mitreattack-python`, `attackcti`, `stix2` libraries\n- MITRE ATT&CK Navigator (web-based or local deployment)\n- Understanding of ATT&CK matrix structure: Tactics, Techniques, Sub-techniques\n- Access to threat intelligence reports or MISP\u002FOpenCTI for threat actor data\n- Familiarity with STIX 2.1 Attack Pattern objects\n\n## Key Concepts\n\n### ATT&CK Matrix Structure\n\nThe ATT&CK Enterprise matrix organizes adversary behavior into 14 Tactics (the \"why\") containing Techniques (the \"how\") and Sub-techniques (specific implementations). Each technique has associated data sources, detections, mitigations, and real-world procedure examples from observed threat groups.\n\n### Threat Group Profiles\n\nATT&CK catalogs over 140 threat groups (e.g., APT28, APT29, Lazarus Group, FIN7) with documented technique usage. Each group profile includes aliases, targeted sectors, associated campaigns, software used, and technique mappings with procedure-level detail.\n\n### ATT&CK Navigator\n\nThe ATT&CK Navigator is a web-based tool for creating custom ATT&CK matrix visualizations. Analysts create layers (JSON files) that annotate techniques with scores, colors, comments, and metadata to visualize threat actor coverage, detection capabilities, or risk assessments.\n\n## Workflow\n\n### Step 1: Query ATT&CK Data Programmatically\n\n```python\nfrom attackcti import attack_client\nimport json\n\n# Initialize ATT&CK client (queries MITRE TAXII server)\nlift = attack_client()\n\n# Get all Enterprise techniques\nenterprise_techniques = lift.get_enterprise_techniques()\nprint(f\"Total Enterprise techniques: {len(enterprise_techniques)}\")\n\n# Get all threat groups\ngroups = lift.get_groups()\nprint(f\"Total threat groups: {len(groups)}\")\n\n# Get specific group by name\napt29 = [g for g in groups if 'APT29' in g.get('name', '')]\nif apt29:\n    group = apt29[0]\n    print(f\"Group: {group['name']}\")\n    print(f\"Aliases: {group.get('aliases', [])}\")\n    print(f\"Description: {group.get('description', '')[:200]}\")\n```\n\n### Step 2: Map Threat Actor to ATT&CK Techniques\n\n```python\nfrom attackcti import attack_client\n\nlift = attack_client()\n\n# Get techniques used by APT29\napt29_techniques = lift.get_techniques_used_by_group(\"G0016\")  # APT29 group ID\n\ntechnique_map = {}\nfor entry in apt29_techniques:\n    tech_id = entry.get(\"external_references\", [{}])[0].get(\"external_id\", \"\")\n    tech_name = entry.get(\"name\", \"\")\n    description = entry.get(\"description\", \"\")\n    tactic_refs = [\n        phase.get(\"phase_name\", \"\")\n        for phase in entry.get(\"kill_chain_phases\", [])\n    ]\n\n    technique_map[tech_id] = {\n        \"name\": tech_name,\n        \"tactics\": tactic_refs,\n        \"description\": description[:300],\n    }\n\nprint(f\"\\nAPT29 uses {len(technique_map)} techniques:\")\nfor tid, info in sorted(technique_map.items()):\n    print(f\"  {tid}: {info['name']} [{', '.join(info['tactics'])}]\")\n```\n\n### Step 3: Generate ATT&CK Navigator Layer\n\n```python\nimport json\n\ndef create_navigator_layer(group_name, technique_map, description=\"\"):\n    \"\"\"Generate ATT&CK Navigator layer JSON for a threat group.\"\"\"\n    techniques_list = []\n    for tech_id, info in technique_map.items():\n        techniques_list.append({\n            \"techniqueID\": tech_id,\n            \"tactic\": info[\"tactics\"][0] if info[\"tactics\"] else \"\",\n            \"color\": \"#ff6666\",  # Red for observed techniques\n            \"comment\": info[\"description\"][:200],\n            \"enabled\": True,\n            \"score\": 100,\n            \"metadata\": [\n                {\"name\": \"group\", \"value\": group_name},\n            ],\n        })\n\n    layer = {\n        \"name\": f\"{group_name} TTP Coverage\",\n        \"versions\": {\n            \"attack\": \"16.1\",\n            \"navigator\": \"5.1.0\",\n            \"layer\": \"4.5\",\n        },\n        \"domain\": \"enterprise-attack\",\n        \"description\": description or f\"Techniques attributed to {group_name}\",\n        \"filters\": {\"platforms\": [\"Windows\", \"Linux\", \"macOS\", \"Cloud\"]},\n        \"sorting\": 0,\n        \"layout\": {\n            \"layout\": \"side\",\n            \"aggregateFunction\": \"average\",\n            \"showID\": True,\n            \"showName\": True,\n            \"showAggregateScores\": False,\n            \"countUnscored\": False,\n        },\n        \"hideDisabled\": False,\n        \"techniques\": techniques_list,\n        \"gradient\": {\n            \"colors\": [\"#ffffff\", \"#ff6666\"],\n            \"minValue\": 0,\n            \"maxValue\": 100,\n        },\n        \"legendItems\": [\n            {\"label\": \"Observed technique\", \"color\": \"#ff6666\"},\n            {\"label\": \"Not observed\", \"color\": \"#ffffff\"},\n        ],\n        \"showTacticRowBackground\": True,\n        \"tacticRowBackground\": \"#dddddd\",\n        \"selectTechniquesAcrossTactics\": True,\n        \"selectSubtechniquesWithParent\": False,\n        \"selectVisibleTechniques\": False,\n    }\n\n    return layer\n\n\n# Generate and save layer\nlayer = create_navigator_layer(\"APT29\", technique_map, \"APT29 (Cozy Bear) TTP analysis\")\nwith open(\"apt29_navigator_layer.json\", \"w\") as f:\n    json.dump(layer, f, indent=2)\nprint(\"[+] Navigator layer saved to apt29_navigator_layer.json\")\n```\n\n### Step 4: Identify Detection Gaps\n\n```python\nfrom attackcti import attack_client\n\nlift = attack_client()\n\n# Get all techniques with data sources\nall_techniques = lift.get_enterprise_techniques()\n\n# Build data source coverage map\ndata_source_coverage = {}\nfor tech in all_techniques:\n    tech_id = tech.get(\"external_references\", [{}])[0].get(\"external_id\", \"\")\n    data_sources = tech.get(\"x_mitre_data_sources\", [])\n\n    for ds in data_sources:\n        if ds not in data_source_coverage:\n            data_source_coverage[ds] = []\n        data_source_coverage[ds].append(tech_id)\n\n# Compare threat actor techniques against available detections\ndetected_techniques = {\"T1059\", \"T1071\", \"T1566\"}  # Example: techniques you can detect\nactor_techniques = set(technique_map.keys())\n\ncovered = actor_techniques.intersection(detected_techniques)\ngaps = actor_techniques - detected_techniques\n\nprint(f\"\\n=== Detection Gap Analysis for APT29 ===\")\nprint(f\"Actor techniques: {len(actor_techniques)}\")\nprint(f\"Detected: {len(covered)} ({len(covered)\u002Flen(actor_techniques)*100:.0f}%)\")\nprint(f\"Gaps: {len(gaps)} ({len(gaps)\u002Flen(actor_techniques)*100:.0f}%)\")\nprint(f\"\\nUndetected techniques:\")\nfor tech_id in sorted(gaps):\n    if tech_id in technique_map:\n        print(f\"  {tech_id}: {technique_map[tech_id]['name']}\")\n```\n\n### Step 5: Cross-Group Technique Comparison\n\n```python\nfrom attackcti import attack_client\n\nlift = attack_client()\n\n# Compare techniques across multiple groups\ngroups_to_compare = {\n    \"G0016\": \"APT29\",\n    \"G0007\": \"APT28\",\n    \"G0032\": \"Lazarus Group\",\n}\n\ngroup_techniques = {}\nfor gid, gname in groups_to_compare.items():\n    techs = lift.get_techniques_used_by_group(gid)\n    tech_ids = set()\n    for t in techs:\n        tid = t.get(\"external_references\", [{}])[0].get(\"external_id\", \"\")\n        if tid:\n            tech_ids.add(tid)\n    group_techniques[gname] = tech_ids\n\n# Find common and unique techniques\nall_groups = list(group_techniques.keys())\ncommon_to_all = set.intersection(*group_techniques.values())\nprint(f\"\\nTechniques common to all {len(all_groups)} groups: {len(common_to_all)}\")\nfor tid in sorted(common_to_all):\n    print(f\"  {tid}\")\n\nfor gname, techs in group_techniques.items():\n    unique = techs - set.union(*[t for n, t in group_techniques.items() if n != gname])\n    print(f\"\\nUnique to {gname}: {len(unique)} techniques\")\n```\n\n## Validation Criteria\n\n- ATT&CK data successfully queried via TAXII server or local copy\n- Threat actor mapped to specific techniques with procedure examples\n- ATT&CK Navigator layer JSON is valid and renders correctly\n- Detection gap analysis identifies unmonitored techniques\n- Cross-group comparison reveals shared and unique TTPs\n- Output is actionable for detection engineering prioritization\n\n## References\n\n- [MITRE ATT&CK](https:\u002F\u002Fattack.mitre.org\u002F)\n- [ATT&CK Navigator](https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F)\n- [attackcti Python Library](https:\u002F\u002Fgithub.com\u002FOTRF\u002FATTACK-Python-Client)\n- [ATT&CK STIX Data](https:\u002F\u002Fgithub.com\u002Fmitre\u002Fcti)\n- [ATT&CK Groups](https:\u002F\u002Fattack.mitre.org\u002Fgroups\u002F)\n","# Analyzing Threat Actor TTPs with MITRE ATT&CK\n\n## Overview\n\nMITRE ATT&CK is a globally-accessible knowledge base of adversary tactics, techniques, and procedures (TTPs) based on real-world observations. This skill covers systematically mapping threat actor behavior to the ATT&CK framework, building technique coverage heatmaps using the ATT&CK Navigator, identifying detection gaps, and producing actionable intelligence reports that link observed IOCs to specific adversary techniques across the Enterprise, Mobile, and ICS matrices.\n\n\n## When to Use\n\n- When investigating security incidents that require analyzing threat actor ttps with mitre attack\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n\n- Python 3.9+ with `mitreattack-python`, `attackcti`, `stix2` libraries\n- MITRE ATT&CK Navigator (web-based or local deployment)\n- Understanding of ATT&CK matrix structure: Tactics, Techniques, Sub-techniques\n- Access to threat intelligence reports or MISP\u002FOpenCTI for threat actor data\n- Familiarity with STIX 2.1 Attack Pattern objects\n\n## Key Concepts\n\n### ATT&CK Matrix Structure\n\nThe ATT&CK Enterprise matrix organizes adversary behavior into 14 Tactics (the \"why\") containing Techniques (the \"how\") and Sub-techniques (specific implementations). Each technique has associated data sources, detections, mitigations, and real-world procedure examples from observed threat groups.\n\n### Threat Group Profiles\n\nATT&CK catalogs over 140 threat groups (e.g., APT28, APT29, Lazarus Group, FIN7) with documented technique usage. Each group profile includes aliases, targeted sectors, associated campaigns, software used, and technique mappings with procedure-level detail.\n\n### ATT&CK Navigator\n\nThe ATT&CK Navigator is a web-based tool for creating custom ATT&CK matrix visualizations. Analysts create layers (JSON files) that annotate techniques with scores, colors, comments, and metadata to visualize threat actor coverage, detection capabilities, or risk assessments.\n\n## Workflow\n\n### Step 1: Query ATT&CK Data Programmatically\n\n```python\nfrom attackcti import attack_client\nimport json\n\n# Initialize ATT&CK client (queries MITRE TAXII server)\nlift = attack_client()\n\n# Get all Enterprise techniques\nenterprise_techniques = lift.get_enterprise_techniques()\nprint(f\"Total Enterprise techniques: {len(enterprise_techniques)}\")\n\n# Get all threat groups\ngroups = lift.get_groups()\nprint(f\"Total threat groups: {len(groups)}\")\n\n# Get specific group by name\napt29 = [g for g in groups if 'APT29' in g.get('name', '')]\nif apt29:\n    group = apt29[0]\n    print(f\"Group: {group['name']}\")\n    print(f\"Aliases: {group.get('aliases', [])}\")\n    print(f\"Description: {group.get('description', '')[:200]}\")\n```\n\n### Step 2: Map Threat Actor to ATT&CK Techniques\n\n```python\nfrom attackcti import attack_client\n\nlift = attack_client()\n\n# Get techniques used by APT29\napt29_techniques = lift.get_techniques_used_by_group(\"G0016\")  # APT29 group ID\n\ntechnique_map = {}\nfor entry in apt29_techniques:\n    tech_id = entry.get(\"external_references\", [{}])[0].get(\"external_id\", \"\")\n    tech_name = entry.get(\"name\", \"\")\n    description = entry.get(\"description\", \"\")\n    tactic_refs = [\n        phase.get(\"phase_name\", \"\")\n        for phase in entry.get(\"kill_chain_phases\", [])\n    ]\n\n    technique_map[tech_id] = {\n        \"name\": tech_name,\n        \"tactics\": tactic_refs,\n        \"description\": description[:300],\n    }\n\nprint(f\"\\nAPT29 uses {len(technique_map)} techniques:\")\nfor tid, info in sorted(technique_map.items()):\n    print(f\"  {tid}: {info['name']} [{', '.join(info['tactics'])}]\")\n```\n\n### Step 3: Generate ATT&CK Navigator Layer\n\n```python\nimport json\n\ndef create_navigator_layer(group_name, technique_map, description=\"\"):\n    \"\"\"Generate ATT&CK Navigator layer JSON for a threat group.\"\"\"\n    techniques_list = []\n    for tech_id, info in technique_map.items():\n        techniques_list.append({\n            \"techniqueID\": tech_id,\n            \"tactic\": info[\"tactics\"][0] if info[\"tactics\"] else \"\",\n            \"color\": \"#ff6666\",  # Red for observed techniques\n            \"comment\": info[\"description\"][:200],\n            \"enabled\": True,\n            \"score\": 100,\n            \"metadata\": [\n                {\"name\": \"group\", \"value\": group_name},\n            ],\n        })\n\n    layer = {\n        \"name\": f\"{group_name} TTP Coverage\",\n        \"versions\": {\n            \"attack\": \"16.1\",\n            \"navigator\": \"5.1.0\",\n            \"layer\": \"4.5\",\n        },\n        \"domain\": \"enterprise-attack\",\n        \"description\": description or f\"Techniques attributed to {group_name}\",\n        \"filters\": {\"platforms\": [\"Windows\", \"Linux\", \"macOS\", \"Cloud\"]},\n        \"sorting\": 0,\n        \"layout\": {\n            \"layout\": \"side\",\n            \"aggregateFunction\": \"average\",\n            \"showID\": True,\n            \"showName\": True,\n            \"showAggregateScores\": False,\n            \"countUnscored\": False,\n        },\n        \"hideDisabled\": False,\n        \"techniques\": techniques_list,\n        \"gradient\": {\n            \"colors\": [\"#ffffff\", \"#ff6666\"],\n            \"minValue\": 0,\n            \"maxValue\": 100,\n        },\n        \"legendItems\": [\n            {\"label\": \"Observed technique\", \"color\": \"#ff6666\"},\n            {\"label\": \"Not observed\", \"color\": \"#ffffff\"},\n        ],\n        \"showTacticRowBackground\": True,\n        \"tacticRowBackground\": \"#dddddd\",\n        \"selectTechniquesAcrossTactics\": True,\n        \"selectSubtechniquesWithParent\": False,\n        \"selectVisibleTechniques\": False,\n    }\n\n    return layer\n\n\n# Generate and save layer\nlayer = create_navigator_layer(\"APT29\", technique_map, \"APT29 (Cozy Bear) TTP analysis\")\nwith open(\"apt29_navigator_layer.json\", \"w\") as f:\n    json.dump(layer, f, indent=2)\nprint(\"[+] Navigator layer saved to apt29_navigator_layer.json\")\n```\n\n### Step 4: Identify Detection Gaps\n\n```python\nfrom attackcti import attack_client\n\nlift = attack_client()\n\n# Get all techniques with data sources\nall_techniques = lift.get_enterprise_techniques()\n\n# Build data source coverage map\ndata_source_coverage = {}\nfor tech in all_techniques:\n    tech_id = tech.get(\"external_references\", [{}])[0].get(\"external_id\", \"\")\n    data_sources = tech.get(\"x_mitre_data_sources\", [])\n\n    for ds in data_sources:\n        if ds not in data_source_coverage:\n            data_source_coverage[ds] = []\n        data_source_coverage[ds].append(tech_id)\n\n# Compare threat actor techniques against available detections\ndetected_techniques = {\"T1059\", \"T1071\", \"T1566\"}  # Example: techniques you can detect\nactor_techniques = set(technique_map.keys())\n\ncovered = actor_techniques.intersection(detected_techniques)\ngaps = actor_techniques - detected_techniques\n\nprint(f\"\\n=== Detection Gap Analysis for APT29 ===\")\nprint(f\"Actor techniques: {len(actor_techniques)}\")\nprint(f\"Detected: {len(covered)} ({len(covered)\u002Flen(actor_techniques)*100:.0f}%)\")\nprint(f\"Gaps: {len(gaps)} ({len(gaps)\u002Flen(actor_techniques)*100:.0f}%)\")\nprint(f\"\\nUndetected techniques:\")\nfor tech_id in sorted(gaps):\n    if tech_id in technique_map:\n        print(f\"  {tech_id}: {technique_map[tech_id]['name']}\")\n```\n\n### Step 5: Cross-Group Technique Comparison\n\n```python\nfrom attackcti import attack_client\n\nlift = attack_client()\n\n# Compare techniques across multiple groups\ngroups_to_compare = {\n    \"G0016\": \"APT29\",\n    \"G0007\": \"APT28\",\n    \"G0032\": \"Lazarus Group\",\n}\n\ngroup_techniques = {}\nfor gid, gname in groups_to_compare.items():\n    techs = lift.get_techniques_used_by_group(gid)\n    tech_ids = set()\n    for t in techs:\n        tid = t.get(\"external_references\", [{}])[0].get(\"external_id\", \"\")\n        if tid:\n            tech_ids.add(tid)\n    group_techniques[gname] = tech_ids\n\n# Find common and unique techniques\nall_groups = list(group_techniques.keys())\ncommon_to_all = set.intersection(*group_techniques.values())\nprint(f\"\\nTechniques common to all {len(all_groups)} groups: {len(common_to_all)}\")\nfor tid in sorted(common_to_all):\n    print(f\"  {tid}\")\n\nfor gname, techs in group_techniques.items():\n    unique = techs - set.union(*[t for n, t in group_techniques.items() if n != gname])\n    print(f\"\\nUnique to {gname}: {len(unique)} techniques\")\n```\n\n## Validation Criteria\n\n- ATT&CK data successfully queried via TAXII server or local copy\n- Threat actor mapped to specific techniques with procedure examples\n- ATT&CK Navigator layer JSON is valid and renders correctly\n- Detection gap analysis identifies unmonitored techniques\n- Cross-group comparison reveals shared and unique TTPs\n- Output is actionable for detection engineering prioritization\n\n## References\n\n- [MITRE ATT&CK](https:\u002F\u002Fattack.mitre.org\u002F)\n- [ATT&CK Navigator](https:\u002F\u002Fmitre-attack.github.io\u002Fattack-navigator\u002F)\n- [attackcti Python Library](https:\u002F\u002Fgithub.com\u002FOTRF\u002FATTACK-Python-Client)\n- [ATT&CK STIX Data](https:\u002F\u002Fgithub.com\u002Fmitre\u002Fcti)\n- [ATT&CK Groups](https:\u002F\u002Fattack.mitre.org\u002Fgroups\u002F)\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":26,"description":7,"mitre_attack":41,"d3fend_techniques":47},[26,27,28,29,30,31,32],"threat-intelligence","cti","ioc","mitre-attack","stix","ttp-analysis","threat-actors","mahipal","cybersecurity","1.0",[37,38,39,40],"ID.RA-01","ID.RA-05","DE.CM-01","DE.AE-02",[42,43,44,45,46],"T1566.001","T1059.001","T1071.001","T1547.001","T1053.005",[48,49,50,51,52],"Executable Denylisting","Execution Isolation","File Metadata Consistency Validation","Content Format Conversion","File Content Analysis","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add NeelakshSaxena\u002FVayu --skill analyzing-threat-actor-ttps-with-mitre-attack",{"tool":66,"command":67},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill analyzing-threat-actor-ttps-with-mitre-attack",{"tool":69,"command":70},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill analyzing-threat-actor-ttps-with-mitre-attack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002FSKILL.md",true,[74,80,84,90,94,98,104],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Ftemplate.md","ASSET","资产文件",2234,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002Fassets\u002Ftemplate.md",{"path":81,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fapi-reference.md","REFERENCE","参考文档",2102,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002Freferences\u002Fapi-reference.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fstandards.md",3299,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002Freferences\u002Fstandards.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fworkflows.md",4817,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002Freferences\u002Fworkflows.md",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fagent.py","SCRIPT","脚本",5176,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002Fscripts\u002Fagent.py",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fprocess.py",12390,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalyzing-threat-actor-ttps-with-mitre-attack\u002Fscripts\u002Fprocess.py",[109,116,123,130,137,144],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]