CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-compliance-checker

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

47

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-aws-compliance-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%Weight 40%Scale 1-5

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

The skill is rich with concrete, executable compliance checks but suffers from a monolithic, over-long body that inlines scripts instead of referencing separate files, and lacks a clear sequenced workflow with validation checkpoints. Splitting code into bundle files and adding a pre-flight validation step would markedly improve it.

Suggestions

Move the large bash/python check scripts into a scripts/ or references/ directory and keep SKILL.md as a concise overview with one-level-deep links.

Add a validation/feedback loop: a pre-flight check for AWS credentials and permissions, and a post-run step that verifies the report was written and is non-empty.

Complete the stubbed functions (run_cis_checks/run_pci_checks/run_hipaa_checks) and the commented-out PCI requirements (2 and 4) so the reporting path is fully executable.

DimensionReasoningScore

Conciseness

The ~520-line body inlines large bash/python scripts that belong in separate bundle files, and adds padded sections (Best Practices, Example Prompts, Kiro CLI Integration), making it noticeably verbose.

2 / 5

Actionability

Provides concrete, mostly executable aws-cli/bash/python code with real checks, though the reporting module has stub functions (run_cis_checks returns []) and some PCI requirements are commented out.

4 / 5

Workflow Clarity

Content is organized by framework and category but presents a collection of independent scripts rather than a sequenced workflow, with no validation checkpoints or credential/permission pre-checks.

2 / 5

Progressive Disclosure

Despite section headers, the monolithic SKILL.md inlines ~400 lines of script that clearly belong in references/scripts/ files; no bundle files exist to offload the detail.

2 / 5

Total

10

/

20

Passed

Description

61%Weight 40%Scale 1-5

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 is specific to its compliance-benchmark niche with good trigger keywords, but it omits explicit 'when to use' guidance and uses only a single generic action verb. Adding a 'Use when...' clause and a second concrete action would lift it substantially.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when preparing for audits, validating CIS/PCI/HIPAA/SOC 2 compliance, or maintaining continuous compliance monitoring.'

Replace the single generic verb 'checking' with multiple concrete actions (e.g., 'audits, scores, and reports AWS compliance against...').

Mention 'AWS' in the description to match the skill name and sharpen distinctiveness from general security-audit skills.

DimensionReasoningScore

Specificity

Names the compliance domain and four specific benchmarks (CIS, PCI-DSS, HIPAA, SOC 2), but offers only a single generic action ('compliance checking') rather than multiple concrete actions.

3 / 5

Completeness

Clearly states what the skill does, but lacks any 'Use when...' or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms users say (compliance, CIS, PCI-DSS, HIPAA, SOC 2, benchmarks), but omits common synonyms like 'audit' or 'security review'.

4 / 5

Distinctiveness Conflict Risk

The four named frameworks carve a clear niche with minimal conflict risk, though absence of 'AWS' in the description itself leaves minor overlap with general security-audit skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
boisenoise/skills-collections
Reviewed

Table of Contents

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.