aws-compliance-checker

Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks

Quality

27%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills/skills/security/aws-compliance-checker/SKILL.md

Quality

Content

14%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a massive monolithic dump of compliance-checking scripts with no clear workflow, no progressive disclosure, and significant verbosity. While some bash scripts contain real, executable AWS CLI commands, the Python scripts have incomplete implementations (stub functions, placeholder comments), and there's no guidance on sequencing, error handling, or remediation. The skill would benefit enormously from being restructured into a concise overview with separate bundle files for each framework's checks.

Suggestions

Extract each framework's scripts (CIS, PCI-DSS, HIPAA) into separate bundle files and reference them from a concise SKILL.md overview with clear navigation links.

Add a clear end-to-end workflow: prerequisites (IAM permissions, credential report generation), execution sequence, validation of results, and remediation steps when issues are found.

Remove the 'Supported Frameworks' section listing well-known framework categories and the generic 'Best Practices' section — Claude already knows these.

Complete the stub implementations (run_cis_checks, run_pci_checks, run_hipaa_checks returning empty lists) or remove the compliance-report.py if it's not functional.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Lists every compliance framework's categories (which Claude already knows), includes massive bash scripts inline, has placeholder functions (run_cis_checks returning empty lists), and explains concepts like what PCI-DSS and HIPAA cover. The 'Supported Frameworks' section is pure padding listing well-known framework categories.	1 / 3
Actionability	The CIS bash scripts are mostly executable and contain real AWS CLI commands, but the PCI-DSS Python checker has incomplete requirements (comments like '# Check for default passwords, etc.'), and the compliance-report.py has stub functions returning empty lists. SOC 2 checks are mentioned but never implemented.	2 / 3
Workflow Clarity	There is no clear workflow for how to actually run a compliance check end-to-end. Scripts are presented as standalone files with no sequencing, no validation checkpoints, no error handling guidance, and no instructions on what to do when issues are found. For a skill involving security auditing, the lack of verification steps and remediation workflows is a significant gap.	1 / 3
Progressive Disclosure	All content is dumped into a single monolithic file with hundreds of lines of inline scripts. The CIS checks alone span multiple large bash scripts that should be in separate bundle files. No bundle files are provided despite the content clearly warranting them. External links are provided but only as generic resources, not as structured references to supporting skill files.	1 / 3
	Total	5 / 12 Passed

Description

40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear domain niche with specific compliance frameworks, making it distinctive. However, it lacks a 'Use when...' clause, provides only a high-level action ('compliance checking') without detailing concrete outputs or capabilities, and misses common user-facing trigger terms like 'security audit' or 'compliance report'.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about compliance audits, security benchmarks, regulatory checks, or mentions CIS, PCI-DSS, HIPAA, or SOC 2.'

Expand the concrete actions described, e.g., 'Scans infrastructure configurations, generates compliance reports, identifies policy violations, and suggests remediation steps.'

Include additional natural trigger terms users might say, such as 'security audit', 'compliance scan', 'regulatory requirements', 'compliance report', or 'security posture'.

Dimension	Reasoning	Score
Specificity	Names the domain (compliance checking) and lists specific frameworks (CIS, PCI-DSS, HIPAA, SOC 2), but doesn't describe concrete actions beyond 'checking' — e.g., what does it produce? Reports, remediation steps, gap analysis?	2 / 3
Completeness	Describes what it does (compliance checking against benchmarks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when' clause caps completeness at 2, and the 'what' is also only partially described, warranting a 1.	1 / 3
Trigger Term Quality	Includes good framework-specific keywords (CIS, PCI-DSS, HIPAA, SOC 2) that users would naturally mention, but misses common variations like 'security audit', 'compliance scan', 'regulatory requirements', 'security benchmarks', or 'compliance report'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'compliance checking' with specific benchmark standards (CIS, PCI-DSS, HIPAA, SOC 2) creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (522 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: popey/claude-code-skills
Path: plugins/antigravity-awesome-skills/skills/security/aws-compliance-checker/SKILL.md
Commit: a5a6601

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.