[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7S2DGGF5P2N6R65PQBNQB":3,"skill-same:01M7A7S2DGGF5P2N6R65PQBNQB":113},{"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":58,"commitSha":59,"skillDirectory":60,"forksCount":14,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M7A7S2DGGF5P2N6R65PQBNQB","implementing-aws-macie-for-data-classification",null,"Enable and configure Amazon Macie via AWS CLI\u002FTerraform to discover, classify, and protect sensitive data (PII, financial data, credentials) in S3 using ML and pattern matching, including discovery jobs, custom data identifiers, allow lists, and EventBridge-based remediation. Use when setting up S3 data classification, cloud DLP, or auditing S3 for unprotected sensitive data.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-aws-macie-for-data-classification\ndescription: Enable and configure Amazon Macie via AWS CLI\u002FTerraform to discover, classify, and protect sensitive data (PII, financial data, credentials) in S3 using ML and pattern matching, including discovery jobs, custom data identifiers, allow lists, and EventBridge-based remediation. Use when setting up S3 data classification, cloud DLP, or auditing S3 for unprotected sensitive data.\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- aws\n- macie\n- data-classification\n- s3\n- pii\n- sensitive-data\n- dlp\n- compliance\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\natlas_techniques:\n- AML.T0043\n- AML.T0018\nnist_ai_rmf:\n- GOVERN-1.1\n- GOVERN-4.2\n- MAP-2.3\n- MEASURE-2.7\n- MEASURE-2.5\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- T1003\n---\n\n# Implementing AWS Macie for Data Classification\n\n## Overview\n\nAmazon Macie is a fully managed data security and privacy service that uses machine learning and pattern matching to discover and protect sensitive data in Amazon S3. Macie automatically evaluates your S3 bucket inventory on a daily basis and identifies objects containing PII, financial information, credentials, and other sensitive data types. It provides two discovery approaches: automated sensitive data discovery for broad visibility and targeted discovery jobs for deep analysis.\n\n\n## When to Use\n\n- When deploying or configuring implementing aws macie for data classification capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- AWS account with S3 buckets containing data to classify\n- IAM permissions for Macie service configuration\n- AWS Organizations setup (for multi-account deployment)\n- S3 buckets in supported regions\n\n## Enable Macie\n\n### Via AWS CLI\n\n```bash\n# Enable Macie in the current account\u002Fregion\naws macie2 enable-macie\n\n# Verify Macie is enabled\naws macie2 get-macie-session\n\n# Enable automated sensitive data discovery\naws macie2 update-automated-discovery-configuration \\\n  --status ENABLED\n```\n\n### Via Terraform\n\n```hcl\nresource \"aws_macie2_account\" \"main\" {}\n\nresource \"aws_macie2_classification_export_configuration\" \"main\" {\n  depends_on = [aws_macie2_account.main]\n\n  s3_destination {\n    bucket_name = aws_s3_bucket.macie_results.id\n    key_prefix  = \"macie-findings\u002F\"\n    kms_key_arn = aws_kms_key.macie.arn\n  }\n}\n```\n\n## Configure Discovery Jobs\n\n### Create a classification job for specific buckets\n\n```bash\naws macie2 create-classification-job \\\n  --job-type ONE_TIME \\\n  --name \"pii-scan-production-buckets\" \\\n  --s3-job-definition '{\n    \"bucketDefinitions\": [{\n      \"accountId\": \"123456789012\",\n      \"buckets\": [\n        \"production-data-bucket\",\n        \"customer-records-bucket\"\n      ]\n    }]\n  }' \\\n  --managed-data-identifier-selector ALL\n```\n\n### Create a scheduled recurring job\n\n```bash\naws macie2 create-classification-job \\\n  --job-type SCHEDULED \\\n  --name \"weekly-sensitive-data-scan\" \\\n  --schedule-frequency-details '{\n    \"weekly\": {\n      \"dayOfWeek\": \"MONDAY\"\n    }\n  }' \\\n  --s3-job-definition '{\n    \"bucketDefinitions\": [{\n      \"accountId\": \"123456789012\",\n      \"buckets\": [\"all-data-bucket\"]\n    }],\n    \"scoping\": {\n      \"includes\": {\n        \"and\": [{\n          \"simpleScopeTerm\": {\n            \"comparator\": \"STARTS_WITH\",\n            \"key\": \"OBJECT_KEY\",\n            \"values\": [\"uploads\u002F\", \"documents\u002F\"]\n          }\n        }]\n      }\n    }\n  }'\n```\n\n## Custom Data Identifiers\n\n### Create a custom identifier for internal IDs\n\n```bash\naws macie2 create-custom-data-identifier \\\n  --name \"internal-employee-id\" \\\n  --description \"Matches internal employee ID format EMP-XXXXXX\" \\\n  --regex \"EMP-[0-9]{6}\" \\\n  --severity-levels '[\n    {\"occurrencesThreshold\": 1, \"severity\": \"LOW\"},\n    {\"occurrencesThreshold\": 10, \"severity\": \"MEDIUM\"},\n    {\"occurrencesThreshold\": 50, \"severity\": \"HIGH\"}\n  ]'\n```\n\n### Create identifier for project codes\n\n```bash\naws macie2 create-custom-data-identifier \\\n  --name \"project-code-identifier\" \\\n  --description \"Matches project codes in format PRJ-XXXX-XX\" \\\n  --regex \"PRJ-[A-Z]{4}-[0-9]{2}\" \\\n  --keywords '[\"project\", \"code\", \"initiative\"]' \\\n  --maximum-match-distance 50\n```\n\n## Allow Lists\n\n### Create an allow list to suppress false positives\n\n```bash\naws macie2 create-allow-list \\\n  --name \"test-data-exclusions\" \\\n  --description \"Exclude known test data patterns\" \\\n  --criteria '{\n    \"regex\": \"TEST-[0-9]{4}-[0-9]{4}-[0-9]{4}-[0-9]{4}\"\n  }'\n```\n\n## Managed Data Identifiers\n\nMacie provides 300+ managed data identifiers covering:\n\n| Category | Examples |\n|----------|---------|\n| **PII** | SSN, passport numbers, driver's license, date of birth, names, addresses |\n| **Financial** | Credit card numbers, bank account numbers, SWIFT codes |\n| **Credentials** | AWS secret keys, API keys, SSH private keys, OAuth tokens |\n| **Health** | HIPAA identifiers, health insurance claim numbers |\n| **Legal** | Tax identification numbers, national ID numbers |\n\n## Findings Management\n\n### List findings\n\n```bash\n# Get sensitive data findings\naws macie2 list-findings \\\n  --finding-criteria '{\n    \"criterion\": {\n      \"severity.description\": {\n        \"eq\": [\"High\"]\n      },\n      \"category\": {\n        \"eq\": [\"CLASSIFICATION\"]\n      }\n    }\n  }' \\\n  --sort-criteria '{\"attributeName\": \"updatedAt\", \"orderBy\": \"DESC\"}' \\\n  --max-results 25\n```\n\n### Get finding details\n\n```bash\naws macie2 get-findings \\\n  --finding-ids '[\"finding-id-1\", \"finding-id-2\"]'\n```\n\n### Export findings to Security Hub\n\n```bash\n# Macie automatically publishes findings to Security Hub\n# Verify integration:\naws macie2 get-macie-session --query 'findingPublishingFrequency'\n```\n\n## EventBridge Integration for Automated Response\n\n```json\n{\n  \"source\": [\"aws.macie\"],\n  \"detail-type\": [\"Macie Finding\"],\n  \"detail\": {\n    \"severity\": {\n      \"description\": [\"High\", \"Critical\"]\n    }\n  }\n}\n```\n\n### Lambda function for automated remediation\n\n```python\nimport boto3\nimport json\n\ns3 = boto3.client('s3')\nsns = boto3.client('sns')\n\ndef lambda_handler(event, context):\n    finding = event['detail']\n    severity = finding['severity']['description']\n    bucket = finding['resourcesAffected']['s3Bucket']['name']\n    key = finding['resourcesAffected']['s3Object']['key']\n    sensitive_types = [d['type'] for d in finding.get('classificationDetails', {}).get('result', {}).get('sensitiveData', [])]\n\n    if severity in ['High', 'Critical']:\n        # Tag the object for review\n        s3.put_object_tagging(\n            Bucket=bucket,\n            Key=key,\n            Tagging={\n                'TagSet': [\n                    {'Key': 'macie-finding', 'Value': severity},\n                    {'Key': 'sensitive-data', 'Value': ','.join(sensitive_types)},\n                    {'Key': 'requires-review', 'Value': 'true'}\n                ]\n            }\n        )\n\n        # Notify security team\n        sns.publish(\n            TopicArn='arn:aws:sns:us-east-1:123456789012:security-alerts',\n            Subject=f'Macie {severity} Finding: {bucket}\u002F{key}',\n            Message=json.dumps({\n                'bucket': bucket,\n                'key': key,\n                'severity': severity,\n                'sensitive_data_types': sensitive_types,\n                'finding_id': finding['id']\n            }, indent=2)\n        )\n\n    return {'statusCode': 200}\n```\n\n## Multi-Account Deployment\n\n### Designate Macie administrator account\n\n```bash\n# From the management account\naws macie2 enable-organization-admin-account \\\n  --admin-account-id 111111111111\n```\n\n### Add member accounts\n\n```bash\n# From the administrator account\naws macie2 create-member \\\n  --account '{\"accountId\": \"222222222222\", \"email\": \"security@example.com\"}'\n```\n\n## Monitoring Macie Operations\n\n### Usage statistics\n\n```bash\naws macie2 get-usage-statistics \\\n  --filter-by '[{\"comparator\": \"GT\", \"key\": \"accountId\", \"values\": []}]' \\\n  --sort-by '{\"key\": \"accountId\", \"orderBy\": \"ASC\"}'\n```\n\n### Classification job status\n\n```bash\naws macie2 list-classification-jobs \\\n  --filter-criteria '{\"includes\": [{\"comparator\": \"EQ\", \"key\": \"jobStatus\", \"values\": [\"RUNNING\"]}]}'\n```\n\n## References\n\n- AWS Macie Documentation: https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002F\n- AWS Macie Pricing\n- Supported File Types for Macie Analysis\n- GDPR and CCPA Compliance with Macie\n","# Implementing AWS Macie for Data Classification\n\n## Overview\n\nAmazon Macie is a fully managed data security and privacy service that uses machine learning and pattern matching to discover and protect sensitive data in Amazon S3. Macie automatically evaluates your S3 bucket inventory on a daily basis and identifies objects containing PII, financial information, credentials, and other sensitive data types. It provides two discovery approaches: automated sensitive data discovery for broad visibility and targeted discovery jobs for deep analysis.\n\n\n## When to Use\n\n- When deploying or configuring implementing aws macie for data classification capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- AWS account with S3 buckets containing data to classify\n- IAM permissions for Macie service configuration\n- AWS Organizations setup (for multi-account deployment)\n- S3 buckets in supported regions\n\n## Enable Macie\n\n### Via AWS CLI\n\n```bash\n# Enable Macie in the current account\u002Fregion\naws macie2 enable-macie\n\n# Verify Macie is enabled\naws macie2 get-macie-session\n\n# Enable automated sensitive data discovery\naws macie2 update-automated-discovery-configuration \\\n  --status ENABLED\n```\n\n### Via Terraform\n\n```hcl\nresource \"aws_macie2_account\" \"main\" {}\n\nresource \"aws_macie2_classification_export_configuration\" \"main\" {\n  depends_on = [aws_macie2_account.main]\n\n  s3_destination {\n    bucket_name = aws_s3_bucket.macie_results.id\n    key_prefix  = \"macie-findings\u002F\"\n    kms_key_arn = aws_kms_key.macie.arn\n  }\n}\n```\n\n## Configure Discovery Jobs\n\n### Create a classification job for specific buckets\n\n```bash\naws macie2 create-classification-job \\\n  --job-type ONE_TIME \\\n  --name \"pii-scan-production-buckets\" \\\n  --s3-job-definition '{\n    \"bucketDefinitions\": [{\n      \"accountId\": \"123456789012\",\n      \"buckets\": [\n        \"production-data-bucket\",\n        \"customer-records-bucket\"\n      ]\n    }]\n  }' \\\n  --managed-data-identifier-selector ALL\n```\n\n### Create a scheduled recurring job\n\n```bash\naws macie2 create-classification-job \\\n  --job-type SCHEDULED \\\n  --name \"weekly-sensitive-data-scan\" \\\n  --schedule-frequency-details '{\n    \"weekly\": {\n      \"dayOfWeek\": \"MONDAY\"\n    }\n  }' \\\n  --s3-job-definition '{\n    \"bucketDefinitions\": [{\n      \"accountId\": \"123456789012\",\n      \"buckets\": [\"all-data-bucket\"]\n    }],\n    \"scoping\": {\n      \"includes\": {\n        \"and\": [{\n          \"simpleScopeTerm\": {\n            \"comparator\": \"STARTS_WITH\",\n            \"key\": \"OBJECT_KEY\",\n            \"values\": [\"uploads\u002F\", \"documents\u002F\"]\n          }\n        }]\n      }\n    }\n  }'\n```\n\n## Custom Data Identifiers\n\n### Create a custom identifier for internal IDs\n\n```bash\naws macie2 create-custom-data-identifier \\\n  --name \"internal-employee-id\" \\\n  --description \"Matches internal employee ID format EMP-XXXXXX\" \\\n  --regex \"EMP-[0-9]{6}\" \\\n  --severity-levels '[\n    {\"occurrencesThreshold\": 1, \"severity\": \"LOW\"},\n    {\"occurrencesThreshold\": 10, \"severity\": \"MEDIUM\"},\n    {\"occurrencesThreshold\": 50, \"severity\": \"HIGH\"}\n  ]'\n```\n\n### Create identifier for project codes\n\n```bash\naws macie2 create-custom-data-identifier \\\n  --name \"project-code-identifier\" \\\n  --description \"Matches project codes in format PRJ-XXXX-XX\" \\\n  --regex \"PRJ-[A-Z]{4}-[0-9]{2}\" \\\n  --keywords '[\"project\", \"code\", \"initiative\"]' \\\n  --maximum-match-distance 50\n```\n\n## Allow Lists\n\n### Create an allow list to suppress false positives\n\n```bash\naws macie2 create-allow-list \\\n  --name \"test-data-exclusions\" \\\n  --description \"Exclude known test data patterns\" \\\n  --criteria '{\n    \"regex\": \"TEST-[0-9]{4}-[0-9]{4}-[0-9]{4}-[0-9]{4}\"\n  }'\n```\n\n## Managed Data Identifiers\n\nMacie provides 300+ managed data identifiers covering:\n\n| Category | Examples |\n|----------|---------|\n| **PII** | SSN, passport numbers, driver's license, date of birth, names, addresses |\n| **Financial** | Credit card numbers, bank account numbers, SWIFT codes |\n| **Credentials** | AWS secret keys, API keys, SSH private keys, OAuth tokens |\n| **Health** | HIPAA identifiers, health insurance claim numbers |\n| **Legal** | Tax identification numbers, national ID numbers |\n\n## Findings Management\n\n### List findings\n\n```bash\n# Get sensitive data findings\naws macie2 list-findings \\\n  --finding-criteria '{\n    \"criterion\": {\n      \"severity.description\": {\n        \"eq\": [\"High\"]\n      },\n      \"category\": {\n        \"eq\": [\"CLASSIFICATION\"]\n      }\n    }\n  }' \\\n  --sort-criteria '{\"attributeName\": \"updatedAt\", \"orderBy\": \"DESC\"}' \\\n  --max-results 25\n```\n\n### Get finding details\n\n```bash\naws macie2 get-findings \\\n  --finding-ids '[\"finding-id-1\", \"finding-id-2\"]'\n```\n\n### Export findings to Security Hub\n\n```bash\n# Macie automatically publishes findings to Security Hub\n# Verify integration:\naws macie2 get-macie-session --query 'findingPublishingFrequency'\n```\n\n## EventBridge Integration for Automated Response\n\n```json\n{\n  \"source\": [\"aws.macie\"],\n  \"detail-type\": [\"Macie Finding\"],\n  \"detail\": {\n    \"severity\": {\n      \"description\": [\"High\", \"Critical\"]\n    }\n  }\n}\n```\n\n### Lambda function for automated remediation\n\n```python\nimport boto3\nimport json\n\ns3 = boto3.client('s3')\nsns = boto3.client('sns')\n\ndef lambda_handler(event, context):\n    finding = event['detail']\n    severity = finding['severity']['description']\n    bucket = finding['resourcesAffected']['s3Bucket']['name']\n    key = finding['resourcesAffected']['s3Object']['key']\n    sensitive_types = [d['type'] for d in finding.get('classificationDetails', {}).get('result', {}).get('sensitiveData', [])]\n\n    if severity in ['High', 'Critical']:\n        # Tag the object for review\n        s3.put_object_tagging(\n            Bucket=bucket,\n            Key=key,\n            Tagging={\n                'TagSet': [\n                    {'Key': 'macie-finding', 'Value': severity},\n                    {'Key': 'sensitive-data', 'Value': ','.join(sensitive_types)},\n                    {'Key': 'requires-review', 'Value': 'true'}\n                ]\n            }\n        )\n\n        # Notify security team\n        sns.publish(\n            TopicArn='arn:aws:sns:us-east-1:123456789012:security-alerts',\n            Subject=f'Macie {severity} Finding: {bucket}\u002F{key}',\n            Message=json.dumps({\n                'bucket': bucket,\n                'key': key,\n                'severity': severity,\n                'sensitive_data_types': sensitive_types,\n                'finding_id': finding['id']\n            }, indent=2)\n        )\n\n    return {'statusCode': 200}\n```\n\n## Multi-Account Deployment\n\n### Designate Macie administrator account\n\n```bash\n# From the management account\naws macie2 enable-organization-admin-account \\\n  --admin-account-id 111111111111\n```\n\n### Add member accounts\n\n```bash\n# From the administrator account\naws macie2 create-member \\\n  --account '{\"accountId\": \"222222222222\", \"email\": \"security@example.com\"}'\n```\n\n## Monitoring Macie Operations\n\n### Usage statistics\n\n```bash\naws macie2 get-usage-statistics \\\n  --filter-by '[{\"comparator\": \"GT\", \"key\": \"accountId\", \"values\": []}]' \\\n  --sort-by '{\"key\": \"accountId\", \"orderBy\": \"ASC\"}'\n```\n\n### Classification job status\n\n```bash\naws macie2 list-classification-jobs \\\n  --filter-criteria '{\"includes\": [{\"comparator\": \"EQ\", \"key\": \"jobStatus\", \"values\": [\"RUNNING\"]}]}'\n```\n\n## References\n\n- AWS Macie Documentation: https:\u002F\u002Fdocs.aws.amazon.com\u002Fmacie\u002F\n- AWS Macie Pricing\n- Supported File Types for Macie Analysis\n- GDPR and CCPA Compliance with Macie\n",{"name":5,"tags":25,"author":34,"domain":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":7,"nist_ai_rmf":43,"mitre_attack":49,"atlas_techniques":55},[26,27,28,29,30,31,32,33],"aws","macie","data-classification","s3","pii","sensitive-data","dlp","compliance","mahipal","cybersecurity","1.0",[38,39,40,41],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01","cloud-security",[44,45,46,47,48],"GOVERN-1.1","GOVERN-4.2","MAP-2.3","MEASURE-2.7","MEASURE-2.5",[50,51,52,53,54],"T1078.004","T1530","T1537","T1580","T1003",[56,57],"AML.T0043","AML.T0018","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add NeelakshSaxena\u002FVayu --skill implementing-aws-macie-for-data-classification",{"tool":71,"command":72},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill implementing-aws-macie-for-data-classification",{"tool":74,"command":75},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill implementing-aws-macie-for-data-classification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002FSKILL.md",true,[79,85,89,95,99,103,109],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"assets\u002Ftemplate.md","ASSET","资产文件",775,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002Fassets\u002Ftemplate.md",{"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","参考文档",2080,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002Freferences\u002Fapi-reference.md",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fstandards.md",625,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002Freferences\u002Fstandards.md",{"path":100,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fworkflows.md",823,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002Freferences\u002Fworkflows.md",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fagent.py","SCRIPT","脚本",6102,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002Fscripts\u002Fagent.py",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fprocess.py",5678,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-aws-macie-for-data-classification\u002Fscripts\u002Fprocess.py",[114,121,128,135,142,149],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]