[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DB34QH20YYJ7F38XMJ4VR8":3,"skill-same:01M7DB34QH20YYJ7F38XMJ4VR8":102},{"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":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M7DB34QH20YYJ7F38XMJ4VR8","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.","SaiVatsal\u002FSkills-I-Use","SaiVatsal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F242597752?v=4","01M7D5YM1T4VXW9203M0GFAHZ1","SaiVatsalPolimera","01M7D5YM2D61ST39XVR2V7B7ZJ",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fmapping-mitre-attack-techniques\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fmapping-mitre-attack-techniques\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mapping-mitre-attack-techniques\ndescription: 'Maps observed adversary behaviors, security alerts, and detection rules\n  to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and\n  guide control prioritization. Use when building an ATT&CK-based coverage heatmap,\n  tagging SIEM alerts with technique IDs, aligning security controls to adversary\n  playbooks, or reporting threat exposure to executives. Activates for requests involving\n  ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.\n\n  '\ndomain: cybersecurity\nsubdomain: threat-intelligence\ntags:\n- MITRE-ATT&CK\n- ATT&CK-Navigator\n- Sigma\n- D3FEND\n- TTP\n- detection-engineering\n- NIST-CSF\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\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- T1591\n- T1592\n- T1593\n- T1589\n- T1685.002\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,"nist_csf":36,"subdomain":41,"description":42,"nist_ai_rmf":43,"mitre_attack":47,"atlas_techniques":53,"d3fend_techniques":57},[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",[37,38,39,40],"ID.RA-01","ID.RA-05","DE.CM-01","DE.AE-02","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",[44,45,46],"MEASURE-2.7","MAP-5.1","MANAGE-2.4",[48,49,50,51,52],"T1591","T1592","T1593","T1589","T1685.002",[54,55,56],"AML.T0070","AML.T0066","AML.T0082",[58,59,60,61,62],"Executable Denylisting","Execution Isolation","File Metadata Consistency Validation","Content Format Conversion","File Content Analysis","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fmapping-mitre-attack-techniques",0,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use","https:\u002F\u002Fgithub.com\u002FSaiVatsal","https:\u002F\u002Fsaivatsal.github.io\u002FPortfolio\u002F","The Longer It Takes The Stronger It Becomes ","2026-09-21 22:45:58",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill mapping-mitre-attack-techniques",{"tool":78,"command":79},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill mapping-mitre-attack-techniques",{"tool":81,"command":82},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill mapping-mitre-attack-techniques","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fmapping-mitre-attack-techniques\u002FSKILL.md",true,[86,90,96],{"path":87,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fapi-reference.md","REFERENCE","参考文档",2708,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fmapping-mitre-attack-techniques\u002Freferences\u002Fapi-reference.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",7754,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fmapping-mitre-attack-techniques\u002Fscripts\u002Fagent.py",[103,111,119,128,135,142],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":20},"01M7DJZP6E6KMBQV4CZSDPZEZ8","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\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":15,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M7DJZFTS5TS06K2TV3MDTE67","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\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":123,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M7DJRK4SRQ908F2TJM6EZ7EV","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","MIT","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":123,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M7DJR902059VEQP23PVM2WA0","design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":123,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":20},"01M7DJR56QF5N6XYTCPCFHFMNP","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":123,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":20},"01M7DJQXB6M0SFF7NX8J5N01AH","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fbanner-design\u002FSKILL.md",[],[]]