[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D6M00KQC4DSGJ79PC5YRDP":3,"skill-same:01M7D6M00KQC4DSGJ79PC5YRDP":106},{"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":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M7D6M00KQC4DSGJ79PC5YRDP","analyzing-ransomware-payment-wallets",null,"Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs, identifying wallet clusters and tracking fund movement through mixers and exchanges to support law enforcement attribution. Use when tracing ransomware bitcoin payments, performing cryptocurrency wallet forensics, or gathering blockchain threat intelligence on extortion payments.","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-ransomware-payment-wallets\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-ransomware-payment-wallets\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyzing-ransomware-payment-wallets\ndescription: 'Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs, identifying wallet clusters and tracking fund movement through mixers and exchanges to support law enforcement attribution. Use when tracing ransomware bitcoin payments, performing cryptocurrency wallet forensics, or gathering blockchain threat intelligence on extortion payments.\n\n  '\ndomain: cybersecurity\nsubdomain: ransomware-defense\ntags:\n- ransomware\n- blockchain\n- cryptocurrency\n- forensics\n- threat-intelligence\n- bitcoin\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.DS-11\n- RS.MA-01\n- RC.RP-01\n- PR.IR-01\nmitre_attack:\n- T1657\n- T1486\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - monetization\n  - stealth\n  techniques:\n  - id: F1018\n    name: Convert to Cryptocurrency\n    tactic: monetization\n    source: f3\n  - id: F1017\n    name: Conversion to Physical Monetary Instruments\n    tactic: monetization\n    source: f3\n  - id: F1017.001\n    name: 'Conversion to Physical Monetary Instruments: Cash'\n    tactic: monetization\n    source: f3\n  - id: F1047\n    name: Transfer of funds\n    tactic: monetization\n    source: f3\n  - id: F1045\n    name: Structuring\n    tactic: stealth\n    source: f3\n---\n\n# Analyzing Ransomware Payment Wallets\n\n## When to Use\n\n- An organization has been hit by ransomware and the ransom note contains a Bitcoin or cryptocurrency wallet address that needs investigation\n- Law enforcement or incident responders need to trace where ransom payments flowed after the victim paid\n- Threat intelligence analysts are attributing ransomware campaigns by clustering payment infrastructure across incidents\n- Investigators need to determine if a ransomware group is reusing wallet infrastructure across multiple victims\n- Compliance or legal teams need evidence of fund flows for prosecution, sanctions enforcement, or insurance claims\n\n**Do not use** this skill for live payment interception or to interact directly with ransomware operators. All analysis should be passive and read-only against public blockchain data.\n\n## Prerequisites\n\n- Python 3.8+ with `requests`, `json`, and `hashlib` libraries\n- Access to blockchain explorer APIs (blockchain.com, WalletExplorer.com, Blockstream.info)\n- Familiarity with Bitcoin transaction model (UTXOs, inputs, outputs, change addresses)\n- Understanding of common obfuscation techniques (mixers, tumblers, peel chains, cross-chain swaps)\n- Optional: Chainalysis Reactor license for enterprise-grade cluster analysis\n- Optional: OXT.me for advanced transaction graph visualization\n\n## Workflow\n\n### Step 1: Extract Wallet Address from Ransom Note\n\nParse the ransom note to identify the payment address(es):\n\n```\nCommon address formats:\n  Bitcoin (P2PKH):   1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa  (starts with 1)\n  Bitcoin (P2SH):    3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy  (starts with 3)\n  Bitcoin (Bech32):  bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq (starts with bc1)\n  Monero:            4... (95 characters, much harder to trace)\n  Ethereum:          0x... (40 hex chars)\n```\n\n### Step 2: Query Blockchain Explorer for Transaction History\n\nRetrieve all transactions associated with the wallet:\n\n```python\nimport requests\n\ndef get_wallet_transactions(address):\n    \"\"\"Query blockchain.com API for address transactions.\"\"\"\n    url = f\"https:\u002F\u002Fblockchain.info\u002Frawaddr\u002F{address}\"\n    resp = requests.get(url, timeout=30)\n    resp.raise_for_status()\n    data = resp.json()\n    return {\n        \"address\": address,\n        \"n_tx\": data.get(\"n_tx\", 0),\n        \"total_received_satoshi\": data.get(\"total_received\", 0),\n        \"total_sent_satoshi\": data.get(\"total_sent\", 0),\n        \"final_balance_satoshi\": data.get(\"final_balance\", 0),\n        \"transactions\": data.get(\"txs\", []),\n    }\n```\n\n### Step 3: Map Fund Flow and Identify Clusters\n\nTrace outputs from the ransom wallet to downstream addresses:\n\n```\nFund Flow Analysis:\n━━━━━━━━━━━━━━━━━━\nVictim Payment ──► Ransom Wallet ──► Consolidation Wallet\n                                  ├─► Mixer\u002FTumbler Service\n                                  ├─► Exchange Deposit Address\n                                  └─► Peel Chain (sequential small outputs)\n\nKey indicators:\n  - Consolidation: Multiple ransom payments aggregated into one wallet\n  - Peel chains: Sequential transactions with diminishing outputs\n  - Mixer usage: Funds sent to known mixer addresses (Wasabi, Samourai, ChipMixer)\n  - Exchange cashout: Deposits to known exchange wallets (Binance, Kraken hot wallets)\n```\n\n### Step 4: Cross-Reference with Known Wallet Databases\n\nCheck addresses against known ransomware infrastructure:\n\n```python\n# Check WalletExplorer for entity identification\ndef check_wallet_explorer(address):\n    url = f\"https:\u002F\u002Fwww.walletexplorer.com\u002Fapi\u002F1\u002Faddress?address={address}&caller=research\"\n    resp = requests.get(url, timeout=30)\n    data = resp.json()\n    return {\n        \"wallet_id\": data.get(\"wallet_id\"),\n        \"label\": data.get(\"label\", \"Unknown\"),\n        \"is_exchange\": data.get(\"is_exchange\", False),\n    }\n```\n\n### Step 5: Generate Attribution Report\n\nCompile findings into a structured intelligence report:\n\n```\nRANSOMWARE WALLET ANALYSIS REPORT\n====================================\nRansom Address:      bc1q...xyz\nFamily Attribution:  LockBit 3.0 (based on ransom note format)\nTotal Received:      4.25 BTC ($178,500 at time of payment)\nTotal Sent:          4.25 BTC (wallet fully drained)\nNumber of Payments:  3 (likely 3 separate victims)\n\nFUND FLOW:\n  Payment 1: 1.5 BTC → Consolidation wallet → Binance deposit\n  Payment 2: 1.0 BTC → Wasabi Mixer → Unknown\n  Payment 3: 1.75 BTC → Peel chain (12 hops) → OKX deposit\n\nCLUSTER ANALYSIS:\n  Related wallets: 47 addresses identified in same cluster\n  Total cluster volume: 156.3 BTC ($6.5M USD)\n  First activity: 2024-01-15\n  Last activity: 2024-09-22\n```\n\n## Verification\n\n- Confirm wallet address format is valid before querying APIs\n- Cross-reference transaction timestamps with known incident timelines\n- Validate cluster associations by checking common-input-ownership heuristic\n- Compare findings against OFAC SDN list for sanctioned addresses\n- Verify exchange attribution against multiple sources (WalletExplorer, OXT, Chainalysis)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **UTXO** | Unspent Transaction Output; the fundamental unit of Bitcoin that tracks ownership through a chain of transactions |\n| **Cluster Analysis** | Grouping multiple Bitcoin addresses believed to be controlled by the same entity using common-input-ownership and change-address heuristics |\n| **Peel Chain** | A laundering pattern where funds are sent through many sequential transactions, each peeling off a small amount to a new address |\n| **CoinJoin\u002FMixer** | Privacy techniques that combine multiple users' transactions to obscure the link between sender and receiver |\n| **Common Input Ownership** | Heuristic that assumes all inputs to a single transaction are controlled by the same entity |\n\n## Tools & Systems\n\n- **Chainalysis Reactor**: Enterprise blockchain investigation platform with entity attribution and cross-chain tracing\n- **WalletExplorer**: Free tool that clusters Bitcoin addresses and labels known services (exchanges, mixers, markets)\n- **OXT.me**: Advanced Bitcoin transaction visualization with UTXO graph analysis\n- **Blockstream.info**: Open-source Bitcoin block explorer with full API access\n- **blockchain.com API**: Free API for querying Bitcoin address balances and transaction histories\n- **OFAC SDN List**: U.S. Treasury sanctioned address list for compliance checking\n","# Analyzing Ransomware Payment Wallets\n\n## When to Use\n\n- An organization has been hit by ransomware and the ransom note contains a Bitcoin or cryptocurrency wallet address that needs investigation\n- Law enforcement or incident responders need to trace where ransom payments flowed after the victim paid\n- Threat intelligence analysts are attributing ransomware campaigns by clustering payment infrastructure across incidents\n- Investigators need to determine if a ransomware group is reusing wallet infrastructure across multiple victims\n- Compliance or legal teams need evidence of fund flows for prosecution, sanctions enforcement, or insurance claims\n\n**Do not use** this skill for live payment interception or to interact directly with ransomware operators. All analysis should be passive and read-only against public blockchain data.\n\n## Prerequisites\n\n- Python 3.8+ with `requests`, `json`, and `hashlib` libraries\n- Access to blockchain explorer APIs (blockchain.com, WalletExplorer.com, Blockstream.info)\n- Familiarity with Bitcoin transaction model (UTXOs, inputs, outputs, change addresses)\n- Understanding of common obfuscation techniques (mixers, tumblers, peel chains, cross-chain swaps)\n- Optional: Chainalysis Reactor license for enterprise-grade cluster analysis\n- Optional: OXT.me for advanced transaction graph visualization\n\n## Workflow\n\n### Step 1: Extract Wallet Address from Ransom Note\n\nParse the ransom note to identify the payment address(es):\n\n```\nCommon address formats:\n  Bitcoin (P2PKH):   1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa  (starts with 1)\n  Bitcoin (P2SH):    3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy  (starts with 3)\n  Bitcoin (Bech32):  bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq (starts with bc1)\n  Monero:            4... (95 characters, much harder to trace)\n  Ethereum:          0x... (40 hex chars)\n```\n\n### Step 2: Query Blockchain Explorer for Transaction History\n\nRetrieve all transactions associated with the wallet:\n\n```python\nimport requests\n\ndef get_wallet_transactions(address):\n    \"\"\"Query blockchain.com API for address transactions.\"\"\"\n    url = f\"https:\u002F\u002Fblockchain.info\u002Frawaddr\u002F{address}\"\n    resp = requests.get(url, timeout=30)\n    resp.raise_for_status()\n    data = resp.json()\n    return {\n        \"address\": address,\n        \"n_tx\": data.get(\"n_tx\", 0),\n        \"total_received_satoshi\": data.get(\"total_received\", 0),\n        \"total_sent_satoshi\": data.get(\"total_sent\", 0),\n        \"final_balance_satoshi\": data.get(\"final_balance\", 0),\n        \"transactions\": data.get(\"txs\", []),\n    }\n```\n\n### Step 3: Map Fund Flow and Identify Clusters\n\nTrace outputs from the ransom wallet to downstream addresses:\n\n```\nFund Flow Analysis:\n━━━━━━━━━━━━━━━━━━\nVictim Payment ──► Ransom Wallet ──► Consolidation Wallet\n                                  ├─► Mixer\u002FTumbler Service\n                                  ├─► Exchange Deposit Address\n                                  └─► Peel Chain (sequential small outputs)\n\nKey indicators:\n  - Consolidation: Multiple ransom payments aggregated into one wallet\n  - Peel chains: Sequential transactions with diminishing outputs\n  - Mixer usage: Funds sent to known mixer addresses (Wasabi, Samourai, ChipMixer)\n  - Exchange cashout: Deposits to known exchange wallets (Binance, Kraken hot wallets)\n```\n\n### Step 4: Cross-Reference with Known Wallet Databases\n\nCheck addresses against known ransomware infrastructure:\n\n```python\n# Check WalletExplorer for entity identification\ndef check_wallet_explorer(address):\n    url = f\"https:\u002F\u002Fwww.walletexplorer.com\u002Fapi\u002F1\u002Faddress?address={address}&caller=research\"\n    resp = requests.get(url, timeout=30)\n    data = resp.json()\n    return {\n        \"wallet_id\": data.get(\"wallet_id\"),\n        \"label\": data.get(\"label\", \"Unknown\"),\n        \"is_exchange\": data.get(\"is_exchange\", False),\n    }\n```\n\n### Step 5: Generate Attribution Report\n\nCompile findings into a structured intelligence report:\n\n```\nRANSOMWARE WALLET ANALYSIS REPORT\n====================================\nRansom Address:      bc1q...xyz\nFamily Attribution:  LockBit 3.0 (based on ransom note format)\nTotal Received:      4.25 BTC ($178,500 at time of payment)\nTotal Sent:          4.25 BTC (wallet fully drained)\nNumber of Payments:  3 (likely 3 separate victims)\n\nFUND FLOW:\n  Payment 1: 1.5 BTC → Consolidation wallet → Binance deposit\n  Payment 2: 1.0 BTC → Wasabi Mixer → Unknown\n  Payment 3: 1.75 BTC → Peel chain (12 hops) → OKX deposit\n\nCLUSTER ANALYSIS:\n  Related wallets: 47 addresses identified in same cluster\n  Total cluster volume: 156.3 BTC ($6.5M USD)\n  First activity: 2024-01-15\n  Last activity: 2024-09-22\n```\n\n## Verification\n\n- Confirm wallet address format is valid before querying APIs\n- Cross-reference transaction timestamps with known incident timelines\n- Validate cluster associations by checking common-input-ownership heuristic\n- Compare findings against OFAC SDN list for sanctioned addresses\n- Verify exchange attribution against multiple sources (WalletExplorer, OXT, Chainalysis)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **UTXO** | Unspent Transaction Output; the fundamental unit of Bitcoin that tracks ownership through a chain of transactions |\n| **Cluster Analysis** | Grouping multiple Bitcoin addresses believed to be controlled by the same entity using common-input-ownership and change-address heuristics |\n| **Peel Chain** | A laundering pattern where funds are sent through many sequential transactions, each peeling off a small amount to a new address |\n| **CoinJoin\u002FMixer** | Privacy techniques that combine multiple users' transactions to obscure the link between sender and receiver |\n| **Common Input Ownership** | Heuristic that assumes all inputs to a single transaction are controlled by the same entity |\n\n## Tools & Systems\n\n- **Chainalysis Reactor**: Enterprise blockchain investigation platform with entity attribution and cross-chain tracing\n- **WalletExplorer**: Free tool that clusters Bitcoin addresses and labels known services (exchanges, mixers, markets)\n- **OXT.me**: Advanced Bitcoin transaction visualization with UTXO graph analysis\n- **Blockstream.info**: Open-source Bitcoin block explorer with full API access\n- **blockchain.com API**: Free API for querying Bitcoin address balances and transaction histories\n- **OFAC SDN List**: U.S. Treasury sanctioned address list for compliance checking\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"mitre_f3":35,"nist_csf":57,"subdomain":62,"description":63,"mitre_attack":64},[26,27,28,29,30,31],"ransomware","blockchain","cryptocurrency","forensics","threat-intelligence","bitcoin","mahipal","cybersecurity","1.0.0",{"tactics":36,"version":39,"techniques":40},[37,38],"monetization","stealth","1.1",[41,45,48,51,54],{"id":42,"name":43,"source":44,"tactic":37},"F1018","Convert to Cryptocurrency","f3",{"id":46,"name":47,"source":44,"tactic":37},"F1017","Conversion to Physical Monetary Instruments",{"id":49,"name":50,"source":44,"tactic":37},"F1017.001","Conversion to Physical Monetary Instruments: Cash",{"id":52,"name":53,"source":44,"tactic":37},"F1047","Transfer of funds",{"id":55,"name":56,"source":44,"tactic":38},"F1045","Structuring",[58,59,60,61],"PR.DS-11","RS.MA-01","RC.RP-01","PR.IR-01","ransomware-defense","Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs, identifying wallet clusters and tracking fund movement through mixers and exchanges to support law enforcement attribution. Use when tracing ransomware bitcoin payments, performing cryptocurrency wallet forensics, or gathering blockchain threat intelligence on extortion payments.\n",[65,66],"T1657","T1486","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-ransomware-payment-wallets",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":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill analyzing-ransomware-payment-wallets",{"tool":82,"command":83},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill analyzing-ransomware-payment-wallets",{"tool":85,"command":86},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill analyzing-ransomware-payment-wallets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-ransomware-payment-wallets\u002FSKILL.md",true,[90,94,100],{"path":91,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fapi-reference.md","REFERENCE","参考文档",3058,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-ransomware-payment-wallets\u002Freferences\u002Fapi-reference.md",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fagent.py","SCRIPT","脚本",7968,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fanalyzing-ransomware-payment-wallets\u002Fscripts\u002Fagent.py",[107,115,123,132,139,146],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"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":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"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":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"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":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"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",[],[]]