[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D69AMAJK2THES96AXF7JWR":3,"skill-same:01M7D69AMAJK2THES96AXF7JWR":87},{"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":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M7D69AMAJK2THES96AXF7JWR","analyzing-cyber-kill-chain",null,"Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.","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\u002Fanalyzing-cyber-kill-chain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-cyber-kill-chain\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyzing-cyber-kill-chain\ndescription: 'Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain\n  framework to identify which phases an adversary has completed, where defenses succeeded\n  or failed, and what controls would have interrupted the attack at earlier phases.\n  Use when conducting post-incident analysis, building prevention-focused security\n  controls, or mapping detection gaps to kill chain phases. Activates for requests\n  involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed\n  Martin kill chain framework.\n\n  '\ndomain: cybersecurity\nsubdomain: threat-intelligence\ntags:\n- kill-chain\n- Lockheed-Martin\n- MITRE-ATT&CK\n- intrusion-analysis\n- defense-in-depth\n- NIST-CSF\nversion: 1.0.0\nauthor: team-cybersecurity\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-05\n- DE.CM-01\n- DE.AE-02\nmitre_attack:\n- T1566.001\n- T1190\n- T1547.001\n- T1071.001\n- T1486\n---\n# Analyzing Cyber Kill Chain\n\n## When to Use\n\nUse this skill when:\n- Conducting post-incident analysis to determine how far an adversary progressed through an attack sequence\n- Designing layered defensive controls with the goal of interrupting attacks at the earliest possible phase\n- Producing threat intelligence reports that communicate attack progression to non-technical stakeholders\n\n**Do not use** this skill as a standalone framework — combine with MITRE ATT&CK for technique-level granularity beyond what the 7-phase kill chain provides.\n\n## Prerequisites\n\n- Complete incident timeline with forensic artifacts mapped to specific adversary actions\n- MITRE ATT&CK Enterprise matrix for technique-level mapping within each kill chain phase\n- Access to threat intelligence on the suspected adversary group's typical kill chain progression\n- Post-incident report or IR timeline from responding team\n\n## Workflow\n\n### Step 1: Map Observed Actions to Kill Chain Phases\n\nThe Lockheed Martin Cyber Kill Chain consists of seven phases. Map all observed adversary actions:\n\n**Phase 1 - Reconnaissance**: Adversary gathers target information before attack.\n- Indicators: DNS queries from adversary IP, LinkedIn scraping, job posting analysis, Shodan scans of organization infrastructure\n\n**Phase 2 - Weaponization**: Adversary creates attack tool (malware + exploit).\n- Indicators: Malware compilation timestamps, exploit document metadata, builder artifacts in malware samples\n\n**Phase 3 - Delivery**: Adversary transmits weapon to target.\n- Indicators: Phishing emails, malicious attachments, drive-by downloads, USB drops, supply chain compromise\n\n**Phase 4 - Exploitation**: Adversary exploits vulnerability to execute code.\n- Indicators: CVE exploitation events in application\u002FOS logs, memory corruption artifacts, shellcode execution\n\n**Phase 5 - Installation**: Adversary establishes persistence on target.\n- Indicators: New scheduled tasks, registry run keys, service installation, web shells, bootkits\n\n**Phase 6 - Command & Control (C2)**: Adversary communicates with compromised system.\n- Indicators: Beaconing traffic (regular intervals), DNS tunneling, HTTPS to uncommon domains, C2 framework signatures (Cobalt Strike, Sliver)\n\n**Phase 7 - Actions on Objectives**: Adversary achieves goals.\n- Indicators: Data staging\u002Fexfiltration, lateral movement, ransomware execution, destructive activity\n\n### Step 2: Identify Phase Completion and Detection Points\n\nCreate a phase matrix for the incident:\n```\nPhase 1: Recon        → Completed (undetected)\nPhase 2: Weaponize    → Completed (undetected — pre-attack)\nPhase 3: Delivery     → Completed; phishing email bypassed SEG\nPhase 4: Exploit      → Completed; CVE-2023-23397 exploited\nPhase 5: Install      → DETECTED: EDR flagged scheduled task creation (attack stalled here)\nPhase 6: C2           → Not achieved (installation blocked)\nPhase 7: Objectives   → Not achieved\n```\n\nFor each phase completed without detection, document the defensive control gap.\n\n### Step 3: Map to MITRE ATT&CK for Technique Detail\n\nEach kill chain phase maps to multiple ATT&CK tactics:\n- Delivery → Initial Access (TA0001)\n- Exploitation → Execution (TA0002)\n- Installation → Persistence (TA0003), Privilege Escalation (TA0004)\n- C2 → Command and Control (TA0011)\n- Actions on Objectives → Exfiltration (TA0010), Impact (TA0040)\n\nWithin each phase, enumerate specific ATT&CK techniques observed and map to existing detections.\n\n### Step 4: Identify Courses of Action per Phase\n\nFor each phase, document applicable defensive courses of action (COAs):\n- **Detect COA**: What detection would alert on adversary activity in this phase?\n- **Deny COA**: What control would prevent the adversary from completing this phase?\n- **Disrupt COA**: What control would interrupt the adversary mid-phase?\n- **Degrade COA**: What control would reduce the adversary's effectiveness in this phase?\n- **Deceive COA**: What deception (honeypots, canary tokens) would expose activity in this phase?\n- **Destroy COA**: What active defense capability would neutralize adversary infrastructure?\n\n### Step 5: Produce Kill Chain Analysis Report\n\nStructure findings as:\n1. Attack narrative (timeline of phases)\n2. Phase-by-phase analysis with evidence\n3. Detection point analysis (what worked, what failed)\n4. Defensive recommendation per phase prioritized by cost\u002Feffectiveness\n5. Control improvement roadmap\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Kill Chain** | Sequential model of adversary intrusion phases; breaking any link theoretically stops the attack |\n| **Courses of Action (COA)** | Defensive responses mapped to each kill chain phase: detect, deny, disrupt, degrade, deceive, destroy |\n| **Beaconing** | Regular, periodic C2 check-in pattern from compromised host to adversary server; detectable by frequency analysis |\n| **Phase Completion** | Adversary successfully finishes a kill chain phase and progresses to the next; defense-in-depth aims to prevent this |\n| **Intelligence Gain\u002FLoss** | Analysis of whether detecting at Phase 5 (vs. Phase 3) reduced intelligence about adversary capabilities or intent |\n\n## Tools & Systems\n\n- **MITRE ATT&CK Navigator**: Overlay kill chain phases with ATT&CK technique coverage for integrated analysis\n- **Elastic Security EQL**: Event Query Language for querying multi-phase attack sequences in Elastic SIEM\n- **Splunk ES**: Timeline visualization and correlation searches for kill chain phase sequencing\n- **MISP**: Kill chain tagging via galaxy clusters for structured incident event documentation\n\n## Common Pitfalls\n\n- **Linear assumption**: Adversaries don't always progress linearly — they may skip phases (weaponization already complete from previous campaign) or loop back (re-establish C2 after detection).\n- **Ignoring Phases 1 and 2**: Reconnaissance and weaponization occur before the defender has visibility. Intelligence about these phases requires external sources (OSINT, threat intelligence).\n- **Missing insider threats**: The kill chain was designed for external adversaries. Insider threats may skip directly to Phase 7 without traversing earlier phases.\n- **Confusing with ATT&CK tactics**: The 7-phase kill chain and 14 ATT&CK tactics are complementary but not directly equivalent. Maintain distinction to prevent analytic confusion.\n","# Analyzing Cyber Kill Chain\n\n## When to Use\n\nUse this skill when:\n- Conducting post-incident analysis to determine how far an adversary progressed through an attack sequence\n- Designing layered defensive controls with the goal of interrupting attacks at the earliest possible phase\n- Producing threat intelligence reports that communicate attack progression to non-technical stakeholders\n\n**Do not use** this skill as a standalone framework — combine with MITRE ATT&CK for technique-level granularity beyond what the 7-phase kill chain provides.\n\n## Prerequisites\n\n- Complete incident timeline with forensic artifacts mapped to specific adversary actions\n- MITRE ATT&CK Enterprise matrix for technique-level mapping within each kill chain phase\n- Access to threat intelligence on the suspected adversary group's typical kill chain progression\n- Post-incident report or IR timeline from responding team\n\n## Workflow\n\n### Step 1: Map Observed Actions to Kill Chain Phases\n\nThe Lockheed Martin Cyber Kill Chain consists of seven phases. Map all observed adversary actions:\n\n**Phase 1 - Reconnaissance**: Adversary gathers target information before attack.\n- Indicators: DNS queries from adversary IP, LinkedIn scraping, job posting analysis, Shodan scans of organization infrastructure\n\n**Phase 2 - Weaponization**: Adversary creates attack tool (malware + exploit).\n- Indicators: Malware compilation timestamps, exploit document metadata, builder artifacts in malware samples\n\n**Phase 3 - Delivery**: Adversary transmits weapon to target.\n- Indicators: Phishing emails, malicious attachments, drive-by downloads, USB drops, supply chain compromise\n\n**Phase 4 - Exploitation**: Adversary exploits vulnerability to execute code.\n- Indicators: CVE exploitation events in application\u002FOS logs, memory corruption artifacts, shellcode execution\n\n**Phase 5 - Installation**: Adversary establishes persistence on target.\n- Indicators: New scheduled tasks, registry run keys, service installation, web shells, bootkits\n\n**Phase 6 - Command & Control (C2)**: Adversary communicates with compromised system.\n- Indicators: Beaconing traffic (regular intervals), DNS tunneling, HTTPS to uncommon domains, C2 framework signatures (Cobalt Strike, Sliver)\n\n**Phase 7 - Actions on Objectives**: Adversary achieves goals.\n- Indicators: Data staging\u002Fexfiltration, lateral movement, ransomware execution, destructive activity\n\n### Step 2: Identify Phase Completion and Detection Points\n\nCreate a phase matrix for the incident:\n```\nPhase 1: Recon        → Completed (undetected)\nPhase 2: Weaponize    → Completed (undetected — pre-attack)\nPhase 3: Delivery     → Completed; phishing email bypassed SEG\nPhase 4: Exploit      → Completed; CVE-2023-23397 exploited\nPhase 5: Install      → DETECTED: EDR flagged scheduled task creation (attack stalled here)\nPhase 6: C2           → Not achieved (installation blocked)\nPhase 7: Objectives   → Not achieved\n```\n\nFor each phase completed without detection, document the defensive control gap.\n\n### Step 3: Map to MITRE ATT&CK for Technique Detail\n\nEach kill chain phase maps to multiple ATT&CK tactics:\n- Delivery → Initial Access (TA0001)\n- Exploitation → Execution (TA0002)\n- Installation → Persistence (TA0003), Privilege Escalation (TA0004)\n- C2 → Command and Control (TA0011)\n- Actions on Objectives → Exfiltration (TA0010), Impact (TA0040)\n\nWithin each phase, enumerate specific ATT&CK techniques observed and map to existing detections.\n\n### Step 4: Identify Courses of Action per Phase\n\nFor each phase, document applicable defensive courses of action (COAs):\n- **Detect COA**: What detection would alert on adversary activity in this phase?\n- **Deny COA**: What control would prevent the adversary from completing this phase?\n- **Disrupt COA**: What control would interrupt the adversary mid-phase?\n- **Degrade COA**: What control would reduce the adversary's effectiveness in this phase?\n- **Deceive COA**: What deception (honeypots, canary tokens) would expose activity in this phase?\n- **Destroy COA**: What active defense capability would neutralize adversary infrastructure?\n\n### Step 5: Produce Kill Chain Analysis Report\n\nStructure findings as:\n1. Attack narrative (timeline of phases)\n2. Phase-by-phase analysis with evidence\n3. Detection point analysis (what worked, what failed)\n4. Defensive recommendation per phase prioritized by cost\u002Feffectiveness\n5. Control improvement roadmap\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Kill Chain** | Sequential model of adversary intrusion phases; breaking any link theoretically stops the attack |\n| **Courses of Action (COA)** | Defensive responses mapped to each kill chain phase: detect, deny, disrupt, degrade, deceive, destroy |\n| **Beaconing** | Regular, periodic C2 check-in pattern from compromised host to adversary server; detectable by frequency analysis |\n| **Phase Completion** | Adversary successfully finishes a kill chain phase and progresses to the next; defense-in-depth aims to prevent this |\n| **Intelligence Gain\u002FLoss** | Analysis of whether detecting at Phase 5 (vs. Phase 3) reduced intelligence about adversary capabilities or intent |\n\n## Tools & Systems\n\n- **MITRE ATT&CK Navigator**: Overlay kill chain phases with ATT&CK technique coverage for integrated analysis\n- **Elastic Security EQL**: Event Query Language for querying multi-phase attack sequences in Elastic SIEM\n- **Splunk ES**: Timeline visualization and correlation searches for kill chain phase sequencing\n- **MISP**: Kill chain tagging via galaxy clusters for structured incident event documentation\n\n## Common Pitfalls\n\n- **Linear assumption**: Adversaries don't always progress linearly — they may skip phases (weaponization already complete from previous campaign) or loop back (re-establish C2 after detection).\n- **Ignoring Phases 1 and 2**: Reconnaissance and weaponization occur before the defender has visibility. Intelligence about these phases requires external sources (OSINT, threat intelligence).\n- **Missing insider threats**: The kill chain was designed for external adversaries. Insider threats may skip directly to Phase 7 without traversing earlier phases.\n- **Confusing with ATT&CK tactics**: The 7-phase kill chain and 14 ATT&CK tactics are complementary but not directly equivalent. Maintain distinction to prevent analytic confusion.\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":41,"mitre_attack":42},[26,27,28,29,30,31],"kill-chain","Lockheed-Martin","MITRE-ATT&CK","intrusion-analysis","defense-in-depth","NIST-CSF","team-cybersecurity","cybersecurity","1.0.0",[36,37,38,39],"ID.RA-01","ID.RA-05","DE.CM-01","DE.AE-02","threat-intelligence","Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.\n",[43,44,45,46,47],"T1566.001","T1190","T1547.001","T1071.001","T1486","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-cyber-kill-chain",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill analyzing-cyber-kill-chain",{"tool":63,"command":64},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill analyzing-cyber-kill-chain",{"tool":66,"command":67},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill analyzing-cyber-kill-chain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-cyber-kill-chain\u002FSKILL.md",true,[71,75,81],{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fapi-reference.md","REFERENCE","参考文档",2749,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-cyber-kill-chain\u002Freferences\u002Fapi-reference.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fagent.py","SCRIPT","脚本",10440,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-cyber-kill-chain\u002Fscripts\u002Fagent.py",[88,96,104,113,120,127],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":108,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":108,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":108,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":108,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"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",[],[]]