[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E58C0P4273NM3AT789PCF0":3,"skill-same:01M7E58C0P4273NM3AT789PCF0":101},{"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":6,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M7E58C0P4273NM3AT789PCF0","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.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fmapping-mitre-attack-techniques\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\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","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fcybersecurity-skills\u002Fskills\u002Fmapping-mitre-attack-techniques",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill mapping-mitre-attack-techniques",{"tool":77,"command":78},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill mapping-mitre-attack-techniques",{"tool":80,"command":81},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill mapping-mitre-attack-techniques","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fmapping-mitre-attack-techniques\u002FSKILL.md",true,[85,89,95],{"path":86,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fapi-reference.md","REFERENCE","参考文档",2708,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fmapping-mitre-attack-techniques\u002Freferences\u002Fapi-reference.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fagent.py","SCRIPT","脚本",7754,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fmapping-mitre-attack-techniques\u002Fscripts\u002Fagent.py",[102,110,118,126,134,141],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":20},"01M7EFF1CSQNTDMHFK4ZGY6NYK","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\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":20},"01M7EFE8106X6C28FT8PA74427","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\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":20},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":20},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]