[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B727ETCGV2JCFJ69KWHG4B":3,"skill-same:01M7B727ETCGV2JCFJ69KWHG4B":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":13,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M7B727ETCGV2JCFJ69KWHG4B","implementing-aws-security-hub",null,"Deploy AWS Security Hub as a centralized CSPM platform, backed by AWS Config, aggregating findings from GuardDuty, Inspector, Macie, and third-party tools; enable CIS Foundations, PCI-DSS, and NIST standards; automate remediation via EventBridge\u002FSystems Manager; and produce Audit Manager evidence. Use for a centralized findings dashboard or compliance audit evidence; not for threat detection or container scanning.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-aws-security-hub\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-aws-security-hub\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-aws-security-hub\ndescription: 'Deploy AWS Security Hub as a centralized CSPM platform, backed by AWS\n  Config, aggregating findings from GuardDuty, Inspector, Macie, and third-party tools;\n  enable CIS Foundations, PCI-DSS, and NIST standards; automate remediation via EventBridge\u002FSystems\n  Manager; and produce Audit Manager evidence. Use for a centralized findings dashboard\n  or compliance audit evidence; not for threat detection or container scanning.\n\n  '\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- aws-security-hub\n- cspm\n- compliance-automation\n- security-standards\n- finding-aggregation\nversion: 1.0.0\nauthor: mahipal\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---\n\n# Implementing AWS Security Hub\n\n## When to Use\n\n- When establishing a centralized security findings dashboard across multiple AWS accounts\n- When enabling automated compliance checks against CIS, PCI-DSS, NIST, or AWS Foundational Security Best Practices\n- When integrating findings from GuardDuty, Inspector, Macie, and third-party security tools\n- When building automated remediation workflows for recurring security misconfigurations\n- When preparing compliance evidence for auditors requiring continuous posture monitoring\n\n**Do not use** for real-time threat detection (see detecting-cloud-threats-with-guardduty), for Azure compliance monitoring (see securing-azure-with-microsoft-defender), or for deep vulnerability scanning of container images (see securing-container-registry).\n\n## Prerequisites\n\n- AWS Organization with a designated security administrator account\n- AWS Config enabled in all target accounts and regions\n- GuardDuty, Inspector, and Macie activated for finding integration\n- IAM permissions for securityhub:* and config:* in the administrator account\n\n## Workflow\n\n### Step 1: Enable Security Hub with Standards\n\nActivate Security Hub in the delegated administrator account and enable security standards. AWS Security Hub CSPM supports CIS AWS Foundations Benchmark v5.0, AWS Foundational Security Best Practices, PCI DSS v3.2.1, and NIST SP 800-53.\n\n```bash\n# Enable Security Hub with standards\naws securityhub enable-security-hub \\\n  --enable-default-standards \\\n  --tags '{\"Environment\":\"production\",\"ManagedBy\":\"security-team\"}'\n\n# Enable CIS AWS Foundations Benchmark v5.0\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[\n    {\"StandardsArn\": \"arn:aws:securityhub:::ruleset\u002Fcis-aws-foundations-benchmark\u002Fv\u002F5.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fpci-dss\u002Fv\u002F3.2.1\"}\n  ]'\n\n# Verify enabled standards\naws securityhub get-enabled-standards \\\n  --query 'StandardsSubscriptions[*].[StandardsArn,StandardsStatus]' --output table\n```\n\n### Step 2: Configure Multi-Account Aggregation\n\nDesignate a Security Hub administrator and automatically enroll all organization member accounts. Configure cross-region aggregation to consolidate findings into a single region.\n\n```bash\n# Designate delegated admin\naws securityhub enable-organization-admin-account \\\n  --admin-account-id 111122223333\n\n# Auto-enable for all org members\naws securityhub update-organization-configuration \\\n  --auto-enable \\\n  --organization-configuration '{\"ConfigurationType\": \"CENTRAL\"}'\n\n# Enable cross-region aggregation\naws securityhub create-finding-aggregator \\\n  --region-linking-mode ALL_REGIONS\n```\n\n### Step 3: Integrate Security Services and Third-Party Tools\n\nConfigure product integrations to receive findings from AWS services and partner security tools. Map third-party findings to AWS Security Finding Format (ASFF).\n\n```bash\n# List available product integrations\naws securityhub describe-products \\\n  --query 'Products[*].[ProductName,CompanyName,ProductSubscriptionResourcePolicy]' --output table\n\n# Enable specific integrations\naws securityhub enable-import-findings-for-product \\\n  --product-arn \"arn:aws:securityhub:us-east-1::product\u002Faws\u002Fguardduty\"\n\naws securityhub enable-import-findings-for-product \\\n  --product-arn \"arn:aws:securityhub:us-east-1::product\u002Faws\u002Finspector\"\n\n# Import custom findings using ASFF format\naws securityhub batch-import-findings --findings '[{\n  \"SchemaVersion\": \"2018-10-08\",\n  \"Id\": \"custom-finding-001\",\n  \"ProductArn\": \"arn:aws:securityhub:us-east-1:123456789012:product\u002F123456789012\u002Fdefault\",\n  \"GeneratorId\": \"custom-scanner\",\n  \"AwsAccountId\": \"123456789012\",\n  \"Types\": [\"Software and Configuration Checks\u002FVulnerabilities\u002FCVE\"],\n  \"Title\": \"Unpatched OpenSSL in production ALB backend\",\n  \"Description\": \"CVE-2024-12345 detected on backend instances\",\n  \"Severity\": {\"Label\": \"HIGH\"},\n  \"Resources\": [{\"Type\": \"AwsEc2Instance\", \"Id\": \"arn:aws:ec2:us-east-1:123456789012:instance\u002Fi-0abc123\"}]\n}]'\n```\n\n### Step 4: Build Automated Remediation\n\nCreate Security Hub custom actions linked to EventBridge rules and Lambda functions for one-click or fully automated remediation of common findings.\n\n```bash\n# Create a custom action for remediation\naws securityhub create-action-target \\\n  --name \"IsolateInstance\" \\\n  --description \"Isolate EC2 instance by replacing security groups\" \\\n  --id \"IsolateInstance\"\n\n# EventBridge rule for automated remediation of specific controls\naws events put-rule \\\n  --name SecurityHubAutoRemediate \\\n  --event-pattern '{\n    \"source\": [\"aws.securityhub\"],\n    \"detail-type\": [\"Security Hub Findings - Imported\"],\n    \"detail\": {\n      \"findings\": {\n        \"Compliance\": {\"Status\": [\"FAILED\"]},\n        \"Severity\": {\"Label\": [\"CRITICAL\", \"HIGH\"]},\n        \"GeneratorId\": [\"aws-foundational-security-best-practices\u002Fv\u002F1.0.0\u002FS3.1\"]\n      }\n    }\n  }'\n```\n\n### Step 5: Monitor Compliance Scores and Generate Reports\n\nTrack security scores across standards, monitor compliance drift over time, and generate reports for audit evidence.\n\n```bash\n# Get security score for a standard\naws securityhub get-security-control-definition \\\n  --security-control-id \"S3.1\"\n\n# List all failed controls with counts\naws securityhub get-findings \\\n  --filters '{\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}],\n    \"RecordState\": [{\"Value\": \"ACTIVE\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --sort-criteria '{\"Field\": \"SeverityLabel\", \"SortOrder\": \"desc\"}' \\\n  --max-items 50\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Security Standard | Pre-packaged set of controls mapped to compliance frameworks such as CIS, PCI-DSS, NIST 800-53, and AWS best practices |\n| Security Control | Individual automated check that evaluates a specific AWS resource configuration against a security requirement |\n| ASFF | AWS Security Finding Format, a standardized JSON schema for normalizing findings from all integrated security products |\n| Compliance Score | Percentage of controls in a passing state within a given security standard, calculated per account and aggregated at the organization level |\n| Finding Aggregator | Cross-region mechanism that consolidates findings from all enabled regions into a single administrator region |\n| Custom Action | User-defined action that can be triggered from the Security Hub console to invoke EventBridge rules for manual or automated response |\n\n## Tools & Systems\n\n- **AWS Security Hub CSPM**: Core platform for automated security posture checks and finding aggregation\n- **AWS Config**: Underlying configuration recorder that Security Hub relies on for resource evaluation\n- **Amazon EventBridge**: Event routing service for connecting Security Hub findings to automated remediation workflows\n- **AWS Systems Manager**: Automation documents that Security Hub can invoke for remediation of common misconfigurations\n- **AWS Audit Manager**: Generates audit-ready reports using Security Hub findings as evidence\n\n## Common Scenarios\n\n### Scenario: Failed CIS Controls Across 50 Accounts\n\n**Context**: An enterprise enables CIS AWS Foundations Benchmark v5.0 and discovers 340 failed controls across 50 accounts, primarily in IAM password policy, CloudTrail configuration, and VPC flow log enablement.\n\n**Approach**:\n1. Export all FAILED findings grouped by control ID to identify the most prevalent issues\n2. Prioritize Critical and High severity controls that affect the most accounts\n3. Create Systems Manager Automation documents for the top 10 recurring failures\n4. Deploy automated remediation via EventBridge for controls like S3.1 (block public access) and CloudTrail.1 (enable multi-region trail)\n5. Schedule weekly compliance score reviews and track improvement over a 90-day remediation window\n\n**Pitfalls**: Enabling automated remediation for all controls at once can break production workloads that legitimately require public S3 access or specific network configurations. Always test remediation in a staging account first.\n\n## Output Format\n\n```\nAWS Security Hub Compliance Report\n====================================\nOrganization: acme-corp\nAdministrator Account: 111122223333\nReport Date: 2025-02-23\nStandards Enabled: CIS v5.0, AWS FSBP v1.0, PCI DSS v3.2.1\n\nCOMPLIANCE SCORES:\n  CIS AWS Foundations Benchmark v5.0: 78%\n  AWS Foundational Security Best Practices: 85%\n  PCI DSS v3.2.1: 72%\n\nTOP FAILED CONTROLS (by account count):\n  [S3.1]   Block public access settings enabled      - 23\u002F50 accounts FAILED\n  [CT.1]   CloudTrail multi-region enabled            - 12\u002F50 accounts FAILED\n  [IAM.4]  Root account has no access keys            -  3\u002F50 accounts FAILED\n  [EC2.19] Security groups restrict unrestricted ports- 31\u002F50 accounts FAILED\n  [RDS.3]  RDS encryption at rest enabled             - 18\u002F50 accounts FAILED\n\nFINDING SUMMARY:\n  Total Active Findings: 1,247\n  Critical: 34 | High: 189 | Medium: 567 | Low: 457\n  Auto-Remediated This Month: 89\n  Suppressed: 23\n```\n","# Implementing AWS Security Hub\n\n## When to Use\n\n- When establishing a centralized security findings dashboard across multiple AWS accounts\n- When enabling automated compliance checks against CIS, PCI-DSS, NIST, or AWS Foundational Security Best Practices\n- When integrating findings from GuardDuty, Inspector, Macie, and third-party security tools\n- When building automated remediation workflows for recurring security misconfigurations\n- When preparing compliance evidence for auditors requiring continuous posture monitoring\n\n**Do not use** for real-time threat detection (see detecting-cloud-threats-with-guardduty), for Azure compliance monitoring (see securing-azure-with-microsoft-defender), or for deep vulnerability scanning of container images (see securing-container-registry).\n\n## Prerequisites\n\n- AWS Organization with a designated security administrator account\n- AWS Config enabled in all target accounts and regions\n- GuardDuty, Inspector, and Macie activated for finding integration\n- IAM permissions for securityhub:* and config:* in the administrator account\n\n## Workflow\n\n### Step 1: Enable Security Hub with Standards\n\nActivate Security Hub in the delegated administrator account and enable security standards. AWS Security Hub CSPM supports CIS AWS Foundations Benchmark v5.0, AWS Foundational Security Best Practices, PCI DSS v3.2.1, and NIST SP 800-53.\n\n```bash\n# Enable Security Hub with standards\naws securityhub enable-security-hub \\\n  --enable-default-standards \\\n  --tags '{\"Environment\":\"production\",\"ManagedBy\":\"security-team\"}'\n\n# Enable CIS AWS Foundations Benchmark v5.0\naws securityhub batch-enable-standards \\\n  --standards-subscription-requests '[\n    {\"StandardsArn\": \"arn:aws:securityhub:::ruleset\u002Fcis-aws-foundations-benchmark\u002Fv\u002F5.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Faws-foundational-security-best-practices\u002Fv\u002F1.0.0\"},\n    {\"StandardsArn\": \"arn:aws:securityhub:us-east-1::standards\u002Fpci-dss\u002Fv\u002F3.2.1\"}\n  ]'\n\n# Verify enabled standards\naws securityhub get-enabled-standards \\\n  --query 'StandardsSubscriptions[*].[StandardsArn,StandardsStatus]' --output table\n```\n\n### Step 2: Configure Multi-Account Aggregation\n\nDesignate a Security Hub administrator and automatically enroll all organization member accounts. Configure cross-region aggregation to consolidate findings into a single region.\n\n```bash\n# Designate delegated admin\naws securityhub enable-organization-admin-account \\\n  --admin-account-id 111122223333\n\n# Auto-enable for all org members\naws securityhub update-organization-configuration \\\n  --auto-enable \\\n  --organization-configuration '{\"ConfigurationType\": \"CENTRAL\"}'\n\n# Enable cross-region aggregation\naws securityhub create-finding-aggregator \\\n  --region-linking-mode ALL_REGIONS\n```\n\n### Step 3: Integrate Security Services and Third-Party Tools\n\nConfigure product integrations to receive findings from AWS services and partner security tools. Map third-party findings to AWS Security Finding Format (ASFF).\n\n```bash\n# List available product integrations\naws securityhub describe-products \\\n  --query 'Products[*].[ProductName,CompanyName,ProductSubscriptionResourcePolicy]' --output table\n\n# Enable specific integrations\naws securityhub enable-import-findings-for-product \\\n  --product-arn \"arn:aws:securityhub:us-east-1::product\u002Faws\u002Fguardduty\"\n\naws securityhub enable-import-findings-for-product \\\n  --product-arn \"arn:aws:securityhub:us-east-1::product\u002Faws\u002Finspector\"\n\n# Import custom findings using ASFF format\naws securityhub batch-import-findings --findings '[{\n  \"SchemaVersion\": \"2018-10-08\",\n  \"Id\": \"custom-finding-001\",\n  \"ProductArn\": \"arn:aws:securityhub:us-east-1:123456789012:product\u002F123456789012\u002Fdefault\",\n  \"GeneratorId\": \"custom-scanner\",\n  \"AwsAccountId\": \"123456789012\",\n  \"Types\": [\"Software and Configuration Checks\u002FVulnerabilities\u002FCVE\"],\n  \"Title\": \"Unpatched OpenSSL in production ALB backend\",\n  \"Description\": \"CVE-2024-12345 detected on backend instances\",\n  \"Severity\": {\"Label\": \"HIGH\"},\n  \"Resources\": [{\"Type\": \"AwsEc2Instance\", \"Id\": \"arn:aws:ec2:us-east-1:123456789012:instance\u002Fi-0abc123\"}]\n}]'\n```\n\n### Step 4: Build Automated Remediation\n\nCreate Security Hub custom actions linked to EventBridge rules and Lambda functions for one-click or fully automated remediation of common findings.\n\n```bash\n# Create a custom action for remediation\naws securityhub create-action-target \\\n  --name \"IsolateInstance\" \\\n  --description \"Isolate EC2 instance by replacing security groups\" \\\n  --id \"IsolateInstance\"\n\n# EventBridge rule for automated remediation of specific controls\naws events put-rule \\\n  --name SecurityHubAutoRemediate \\\n  --event-pattern '{\n    \"source\": [\"aws.securityhub\"],\n    \"detail-type\": [\"Security Hub Findings - Imported\"],\n    \"detail\": {\n      \"findings\": {\n        \"Compliance\": {\"Status\": [\"FAILED\"]},\n        \"Severity\": {\"Label\": [\"CRITICAL\", \"HIGH\"]},\n        \"GeneratorId\": [\"aws-foundational-security-best-practices\u002Fv\u002F1.0.0\u002FS3.1\"]\n      }\n    }\n  }'\n```\n\n### Step 5: Monitor Compliance Scores and Generate Reports\n\nTrack security scores across standards, monitor compliance drift over time, and generate reports for audit evidence.\n\n```bash\n# Get security score for a standard\naws securityhub get-security-control-definition \\\n  --security-control-id \"S3.1\"\n\n# List all failed controls with counts\naws securityhub get-findings \\\n  --filters '{\n    \"ComplianceStatus\": [{\"Value\": \"FAILED\", \"Comparison\": \"EQUALS\"}],\n    \"RecordState\": [{\"Value\": \"ACTIVE\", \"Comparison\": \"EQUALS\"}]\n  }' \\\n  --sort-criteria '{\"Field\": \"SeverityLabel\", \"SortOrder\": \"desc\"}' \\\n  --max-items 50\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Security Standard | Pre-packaged set of controls mapped to compliance frameworks such as CIS, PCI-DSS, NIST 800-53, and AWS best practices |\n| Security Control | Individual automated check that evaluates a specific AWS resource configuration against a security requirement |\n| ASFF | AWS Security Finding Format, a standardized JSON schema for normalizing findings from all integrated security products |\n| Compliance Score | Percentage of controls in a passing state within a given security standard, calculated per account and aggregated at the organization level |\n| Finding Aggregator | Cross-region mechanism that consolidates findings from all enabled regions into a single administrator region |\n| Custom Action | User-defined action that can be triggered from the Security Hub console to invoke EventBridge rules for manual or automated response |\n\n## Tools & Systems\n\n- **AWS Security Hub CSPM**: Core platform for automated security posture checks and finding aggregation\n- **AWS Config**: Underlying configuration recorder that Security Hub relies on for resource evaluation\n- **Amazon EventBridge**: Event routing service for connecting Security Hub findings to automated remediation workflows\n- **AWS Systems Manager**: Automation documents that Security Hub can invoke for remediation of common misconfigurations\n- **AWS Audit Manager**: Generates audit-ready reports using Security Hub findings as evidence\n\n## Common Scenarios\n\n### Scenario: Failed CIS Controls Across 50 Accounts\n\n**Context**: An enterprise enables CIS AWS Foundations Benchmark v5.0 and discovers 340 failed controls across 50 accounts, primarily in IAM password policy, CloudTrail configuration, and VPC flow log enablement.\n\n**Approach**:\n1. Export all FAILED findings grouped by control ID to identify the most prevalent issues\n2. Prioritize Critical and High severity controls that affect the most accounts\n3. Create Systems Manager Automation documents for the top 10 recurring failures\n4. Deploy automated remediation via EventBridge for controls like S3.1 (block public access) and CloudTrail.1 (enable multi-region trail)\n5. Schedule weekly compliance score reviews and track improvement over a 90-day remediation window\n\n**Pitfalls**: Enabling automated remediation for all controls at once can break production workloads that legitimately require public S3 access or specific network configurations. Always test remediation in a staging account first.\n\n## Output Format\n\n```\nAWS Security Hub Compliance Report\n====================================\nOrganization: acme-corp\nAdministrator Account: 111122223333\nReport Date: 2025-02-23\nStandards Enabled: CIS v5.0, AWS FSBP v1.0, PCI DSS v3.2.1\n\nCOMPLIANCE SCORES:\n  CIS AWS Foundations Benchmark v5.0: 78%\n  AWS Foundational Security Best Practices: 85%\n  PCI DSS v3.2.1: 72%\n\nTOP FAILED CONTROLS (by account count):\n  [S3.1]   Block public access settings enabled      - 23\u002F50 accounts FAILED\n  [CT.1]   CloudTrail multi-region enabled            - 12\u002F50 accounts FAILED\n  [IAM.4]  Root account has no access keys            -  3\u002F50 accounts FAILED\n  [EC2.19] Security groups restrict unrestricted ports- 31\u002F50 accounts FAILED\n  [RDS.3]  RDS encryption at rest enabled             - 18\u002F50 accounts FAILED\n\nFINDING SUMMARY:\n  Total Active Findings: 1,247\n  Critical: 34 | High: 189 | Medium: 567 | Low: 457\n  Auto-Remediated This Month: 89\n  Suppressed: 23\n```\n",{"name":5,"tags":24,"author":30,"domain":31,"license":14,"version":32,"nist_csf":33,"subdomain":38,"description":39,"mitre_attack":40},[25,26,27,28,29],"aws-security-hub","cspm","compliance-automation","security-standards","finding-aggregation","mahipal","cybersecurity","1.0.0",[34,35,36,37],"PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01","cloud-security","Deploy AWS Security Hub as a centralized CSPM platform, backed by AWS Config, aggregating findings from GuardDuty, Inspector, Macie, and third-party tools; enable CIS Foundations, PCI-DSS, and NIST standards; automate remediation via EventBridge\u002FSystems Manager; and produce Audit Manager evidence. Use for a centralized findings dashboard or compliance audit evidence; not for threat detection or container scanning.\n",[41,42,43,44],"T1078.004","T1530","T1537","T1580","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-aws-security-hub","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-aws-security-hub",{"tool":57,"command":58},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-aws-security-hub",{"tool":60,"command":61},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-aws-security-hub","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-aws-security-hub\u002FSKILL.md",true,[65,69,75],{"path":66,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fapi-reference.md","REFERENCE","参考文档",2354,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-aws-security-hub\u002Freferences\u002Fapi-reference.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fagent.py","SCRIPT","脚本",6933,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-aws-security-hub\u002Fscripts\u002Fagent.py",[82,90,97,104,111,118],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]