[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73ECBQAXRXP8XAFYXC21T3Y":3,"skill-same:01M73ECBQAXRXP8XAFYXC21T3Y":100},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M73ECBQAXRXP8XAFYXC21T3Y","performing-cloud-native-threat-hunting-with-aws-detective",null,"Hunt for threats in AWS environments using Detective behavior graphs, entity investigation timelines, GuardDuty finding correlation, and automated entity profiling across IAM users, EC2 instances, and IP addresses.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cloud-native-threat-hunting-with-aws-detective\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: performing-cloud-native-threat-hunting-with-aws-detective\ndescription: Hunt for threats in AWS environments using Detective behavior graphs,\n  entity investigation timelines, GuardDuty finding correlation, and automated entity\n  profiling across IAM users, EC2 instances, and IP addresses.\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- aws-detective\n- threat-hunting\n- cloud-security\n- guardduty\n- behavior-graph\n- aws\n- iam\n- ec2\n- incident-investigation\nversion: '1.0'\nauthor: juliosuas\nlicense: Apache-2.0\nnist_csf:\n- PR.IR-01\n- ID.AM-08\n- GV.SC-06\n- DE.CM-01\nmitre_attack:\n- T1078.004\n- T1530\n- T1537\n- T1580\n- T1071\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n\n# Performing Cloud-Native Threat Hunting with AWS Detective\n\n## Overview\n\nAWS Detective automatically collects and analyzes log data from AWS CloudTrail, VPC Flow Logs, GuardDuty findings, and EKS audit logs to build interactive behavior graphs. These graphs enable security analysts to investigate entities (IAM users, roles, IP addresses, EC2 instances) across time, identify anomalous API calls, detect lateral movement between accounts, and correlate GuardDuty findings into coherent attack narratives — all without manual log parsing.\n\n## Prerequisites\n\n- AWS account with Detective enabled (requires GuardDuty active for 48+ hours)\n- AWS CLI v2 configured with appropriate IAM permissions (`detective:*`, `guardduty:List*`)\n- Python 3.9+ with boto3\n- IAM policy: `AmazonDetectiveFullAccess` or custom policy with `detective:SearchGraph`, `detective:GetInvestigation`, `detective:ListIndicators`\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| **Behavior Graph** | Data structure linking CloudTrail, VPC Flow, GuardDuty, and EKS logs for an account\u002Fregion |\n| **Entity** | Investigable object: IAM user, IAM role, EC2 instance, IP address, S3 bucket, EKS cluster |\n| **Finding Group** | Correlated set of GuardDuty findings linked to the same attack campaign |\n| **Entity Profile** | Timeline of API calls, network connections, and resource access for a specific entity |\n| **Scope Time** | Investigation window (default 24h, max 1 year) for behavioral analysis |\n\n## Steps\n\n### Step 1: List Available Behavior Graphs\n\n```bash\naws detective list-graphs --output table\n```\n\n### Step 2: Investigate a Suspicious IAM User\n\n```bash\n# Get entity profile for an IAM user\naws detective get-investigation \\\n  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \\\n  --investigation-id 000000000000000000001\n```\n\n### Step 3: Search Entities Programmatically\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Search AWS Detective for suspicious entities.\"\"\"\nimport boto3\nimport json\nfrom datetime import datetime, timedelta\n\ndetective = boto3.client('detective')\n\ndef list_behavior_graphs():\n    \"\"\"List all Detective behavior graphs.\"\"\"\n    response = detective.list_graphs()\n    return response.get('GraphList', [])\n\ndef get_investigation_indicators(graph_arn, investigation_id, max_results=50):\n    \"\"\"Get indicators for a specific investigation.\"\"\"\n    response = detective.list_indicators(\n        GraphArn=graph_arn,\n        InvestigationId=investigation_id,\n        MaxResults=max_results\n    )\n    return response.get('Indicators', [])\n\ndef investigate_guardduty_findings(graph_arn):\n    \"\"\"List high-severity investigations correlated by Detective.\"\"\"\n    response = detective.list_investigations(\n        GraphArn=graph_arn,\n        FilterCriteria={\n            'Severity': {'Value': 'CRITICAL'},\n            'Status': {'Value': 'RUNNING'}\n        },\n        MaxResults=20\n    )\n\n    for investigation in response.get('InvestigationDetails', []):\n        print(f\"Investigation: {investigation['InvestigationId']}\")\n        print(f\"  Entity: {investigation['EntityArn']}\")\n        print(f\"  Status: {investigation['Status']}\")\n        print(f\"  Severity: {investigation['Severity']}\")\n        print(f\"  Created: {investigation['CreatedTime']}\")\n        print()\n\nif __name__ == \"__main__\":\n    graphs = list_behavior_graphs()\n    for graph in graphs:\n        print(f\"Graph: {graph['Arn']}\")\n        investigate_guardduty_findings(graph['Arn'])\n```\n\n### Step 4: Analyze Finding Groups for Attack Campaigns\n\n```bash\n# List investigations with high severity\naws detective list-investigations \\\n  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \\\n  --filter-criteria '{\"Severity\":{\"Value\":\"HIGH\"}}' \\\n  --max-results 10\n```\n\n### Step 5: Check Entity Indicators\n\n```bash\n# Get indicators for a specific investigation\naws detective list-indicators \\\n  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \\\n  --investigation-id 000000000000000000001 \\\n  --max-results 50\n```\n\n## Expected Output\n\nThe `list-investigations` command returns investigation metadata:\n\n```json\n{\n  \"InvestigationDetails\": [\n    {\n      \"InvestigationId\": \"000000000000000000001\",\n      \"Severity\": \"CRITICAL\",\n      \"Status\": \"RUNNING\",\n      \"State\": \"ACTIVE\",\n      \"EntityArn\": \"arn:aws:iam::123456789012:user\u002Fsuspicious-user\",\n      \"EntityType\": \"IAM_USER\",\n      \"CreatedTime\": \"2026-03-15T14:30:00Z\"\n    }\n  ]\n}\n```\n\nIndicators are retrieved separately via `list-indicators` and include types such as `TTP_OBSERVED`, `IMPOSSIBLE_TRAVEL`, `FLAGGED_IP_ADDRESS`, `NEW_GEOLOCATION`, `NEW_ASO`, `NEW_USER_AGENT`, `RELATED_FINDING`, and `RELATED_FINDING_GROUP`.\n\n## Verification\n\n1. Confirm behavior graph has data: `aws detective list-graphs` returns non-empty list\n2. Validate investigation results contain entity timelines with API call sequences\n3. Cross-reference Detective findings with raw CloudTrail logs for accuracy\n4. Verify finding group correlations match manual investigation conclusions\n5. Confirm automated alerts trigger for HIGH\u002FCRITICAL severity investigations\n","# Performing Cloud-Native Threat Hunting with AWS Detective\n\n## Overview\n\nAWS Detective automatically collects and analyzes log data from AWS CloudTrail, VPC Flow Logs, GuardDuty findings, and EKS audit logs to build interactive behavior graphs. These graphs enable security analysts to investigate entities (IAM users, roles, IP addresses, EC2 instances) across time, identify anomalous API calls, detect lateral movement between accounts, and correlate GuardDuty findings into coherent attack narratives — all without manual log parsing.\n\n## Prerequisites\n\n- AWS account with Detective enabled (requires GuardDuty active for 48+ hours)\n- AWS CLI v2 configured with appropriate IAM permissions (`detective:*`, `guardduty:List*`)\n- Python 3.9+ with boto3\n- IAM policy: `AmazonDetectiveFullAccess` or custom policy with `detective:SearchGraph`, `detective:GetInvestigation`, `detective:ListIndicators`\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| **Behavior Graph** | Data structure linking CloudTrail, VPC Flow, GuardDuty, and EKS logs for an account\u002Fregion |\n| **Entity** | Investigable object: IAM user, IAM role, EC2 instance, IP address, S3 bucket, EKS cluster |\n| **Finding Group** | Correlated set of GuardDuty findings linked to the same attack campaign |\n| **Entity Profile** | Timeline of API calls, network connections, and resource access for a specific entity |\n| **Scope Time** | Investigation window (default 24h, max 1 year) for behavioral analysis |\n\n## Steps\n\n### Step 1: List Available Behavior Graphs\n\n```bash\naws detective list-graphs --output table\n```\n\n### Step 2: Investigate a Suspicious IAM User\n\n```bash\n# Get entity profile for an IAM user\naws detective get-investigation \\\n  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \\\n  --investigation-id 000000000000000000001\n```\n\n### Step 3: Search Entities Programmatically\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Search AWS Detective for suspicious entities.\"\"\"\nimport boto3\nimport json\nfrom datetime import datetime, timedelta\n\ndetective = boto3.client('detective')\n\ndef list_behavior_graphs():\n    \"\"\"List all Detective behavior graphs.\"\"\"\n    response = detective.list_graphs()\n    return response.get('GraphList', [])\n\ndef get_investigation_indicators(graph_arn, investigation_id, max_results=50):\n    \"\"\"Get indicators for a specific investigation.\"\"\"\n    response = detective.list_indicators(\n        GraphArn=graph_arn,\n        InvestigationId=investigation_id,\n        MaxResults=max_results\n    )\n    return response.get('Indicators', [])\n\ndef investigate_guardduty_findings(graph_arn):\n    \"\"\"List high-severity investigations correlated by Detective.\"\"\"\n    response = detective.list_investigations(\n        GraphArn=graph_arn,\n        FilterCriteria={\n            'Severity': {'Value': 'CRITICAL'},\n            'Status': {'Value': 'RUNNING'}\n        },\n        MaxResults=20\n    )\n\n    for investigation in response.get('InvestigationDetails', []):\n        print(f\"Investigation: {investigation['InvestigationId']}\")\n        print(f\"  Entity: {investigation['EntityArn']}\")\n        print(f\"  Status: {investigation['Status']}\")\n        print(f\"  Severity: {investigation['Severity']}\")\n        print(f\"  Created: {investigation['CreatedTime']}\")\n        print()\n\nif __name__ == \"__main__\":\n    graphs = list_behavior_graphs()\n    for graph in graphs:\n        print(f\"Graph: {graph['Arn']}\")\n        investigate_guardduty_findings(graph['Arn'])\n```\n\n### Step 4: Analyze Finding Groups for Attack Campaigns\n\n```bash\n# List investigations with high severity\naws detective list-investigations \\\n  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \\\n  --filter-criteria '{\"Severity\":{\"Value\":\"HIGH\"}}' \\\n  --max-results 10\n```\n\n### Step 5: Check Entity Indicators\n\n```bash\n# Get indicators for a specific investigation\naws detective list-indicators \\\n  --graph-arn arn:aws:detective:us-east-1:123456789012:graph:a1b2c3d4 \\\n  --investigation-id 000000000000000000001 \\\n  --max-results 50\n```\n\n## Expected Output\n\nThe `list-investigations` command returns investigation metadata:\n\n```json\n{\n  \"InvestigationDetails\": [\n    {\n      \"InvestigationId\": \"000000000000000000001\",\n      \"Severity\": \"CRITICAL\",\n      \"Status\": \"RUNNING\",\n      \"State\": \"ACTIVE\",\n      \"EntityArn\": \"arn:aws:iam::123456789012:user\u002Fsuspicious-user\",\n      \"EntityType\": \"IAM_USER\",\n      \"CreatedTime\": \"2026-03-15T14:30:00Z\"\n    }\n  ]\n}\n```\n\nIndicators are retrieved separately via `list-indicators` and include types such as `TTP_OBSERVED`, `IMPOSSIBLE_TRAVEL`, `FLAGGED_IP_ADDRESS`, `NEW_GEOLOCATION`, `NEW_ASO`, `NEW_USER_AGENT`, `RELATED_FINDING`, and `RELATED_FINDING_GROUP`.\n\n## Verification\n\n1. Confirm behavior graph has data: `aws detective list-graphs` returns non-empty list\n2. Validate investigation results contain entity timelines with API call sequences\n3. Cross-reference Detective findings with raw CloudTrail logs for accuracy\n4. Verify finding group correlations match manual investigation conclusions\n5. Confirm automated alerts trigger for HIGH\u002FCRITICAL severity investigations\n",{"name":5,"tags":24,"author":34,"domain":35,"source":36,"license":15,"version":37,"nist_csf":38,"subdomain":27,"description":7,"mitre_attack":43,"source_commit":49},[25,26,27,28,29,30,31,32,33],"aws-detective","threat-hunting","cloud-security","guardduty","behavior-graph","aws","iam","ec2","incident-investigation","juliosuas","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[39,40,41,42],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01",[44,45,46,47,48],"T1078.004","T1530","T1537","T1580","T1071","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fperforming-cloud-native-threat-hunting-with-aws-detective",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill performing-cloud-native-threat-hunting-with-aws-detective",{"tool":66,"command":67},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill performing-cloud-native-threat-hunting-with-aws-detective",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill performing-cloud-native-threat-hunting-with-aws-detective","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cloud-native-threat-hunting-with-aws-detective\u002FSKILL.md",true,[74,80,86,90,94],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Ftemplate.md","ASSET","资产文件",1116,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cloud-native-threat-hunting-with-aws-detective\u002Fassets\u002Ftemplate.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fapi-reference.md","REFERENCE","参考文档",8716,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cloud-native-threat-hunting-with-aws-detective\u002Freferences\u002Fapi-reference.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fstandards.md",1084,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cloud-native-threat-hunting-with-aws-detective\u002Freferences\u002Fstandards.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fworkflows.md",1115,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cloud-native-threat-hunting-with-aws-detective\u002Freferences\u002Fworkflows.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fprocess.py","SCRIPT","脚本",7027,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-cloud-native-threat-hunting-with-aws-detective\u002Fscripts\u002Fprocess.py",[101,109,116,124,132,140],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\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":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]