aws-security-audit

Comprehensive AWS security posture assessment using AWS CLI and security best practices

1.12x

Quality

50%

Does it follow best practices?

Impact

82%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-aws-security-audit/SKILL.md

Quality

Content

51%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 body is highly actionable with executable AWS CLI commands and scripts, but it is a flat catalog rather than a sequenced, validated workflow, and it inlines large scripts that should be split into reference files. Repeated logic across three sections adds avoidable token cost.

Suggestions

Add an explicit run sequence with validation checkpoints (e.g. verify credentials/permissions first, then run checks per category, then summarize) to lift workflow clarity above the batch-operation cap.

Move the full bash audit script and Python score calculator into separate scripts/ files, keeping only a concise overview and key examples inline.

De-duplicate the IAM/security-group/EBS checks that currently appear in three places; reference one canonical set of commands.

Dimension	Reasoning	Score
Conciseness	Mostly lean command listings with inline comments and little concept-padding, but IAM/SG/EBS checks are repeated three times (commands, the bash audit script, and the Python score calculator), which is more than minor over-explanation.	3 / 5
Actionability	Provides concrete, copy-paste-ready aws-cli commands and full bash/Python scripts covering common cases, with a minor gap: the Python score calculator leaves the MFA parse step unimplemented (dead `if users_without_mfa > 0` branch).	4 / 5
Workflow Clarity	Content is a categorized catalog of checks rather than a sequenced workflow, with no validation checkpoints; the rubric caps batch-operation skills without validation at 3, and the Limitations safety note only partially mitigates this.	3 / 5
Progressive Disclosure	No references/scripts/assets bundle exists; the skill is monolithic with full bash and Python scripts plus large compliance tables inlined that clearly belong in separate files, despite reasonable section headers.	2 / 5
	Total	12 / 20 Passed

Description

48%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 identifies a clear AWS-security niche but is generic in its action language and omits any "Use when" trigger guidance, capping completeness. It is distinguishable but under-specified for triggering.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. auditing AWS security, preparing for compliance, or finding misconfigurations.

Enumerate concrete actions (e.g. identify permissive IAM policies, find public S3 buckets, check encryption) instead of the single generic word 'assessment'.

Include natural user phrasing/synonyms such as 'audit', 'compliance', 'misconfigurations' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Comprehensive AWS security posture assessment" names the domain and tool (AWS CLI) but offers only one generic action ("assessment") with no enumerated concrete checks, matching the anchor for minimal/generic actions.	2 / 5
Completeness	Has a clear "what" (security posture assessment) but no "Use when..." trigger clause, which the rubric caps at 3; the "when" is entirely missing.	3 / 5
Trigger Term Quality	Contains relevant keywords ("AWS security posture assessment", "AWS CLI") but misses natural verb-form phrases users actually say like "audit my AWS account", "check for security issues", or "find misconfigurations".	3 / 5
Distinctiveness Conflict Risk	Scoped specifically to AWS security posture, a distinct niche with only minor overlap risk against general AWS or compliance skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Path: skills/antigravity-aws-security-audit/SKILL.md
Commit: 19c310e

Reviewed: about 18 hours 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.