Skip to content

Skill Grading Report: mastering-aws-cli - Score 96/100 (A) #39

@RichardHightower

Description

@RichardHightower

🏆 Skill Grading Report

Score: 96/100 | Grade: A

Quick Summary

Pillar Scores

Pillar Score Max
Spec Compliance 15 15
Progressive Disclosure 28 30
Ease of Use 22 25
Writing Style 9 10
Utility 18 20
Modifiers +4 ±15

Issues Found: 3

  • 🔴 High: 0
  • 🟡 Medium: 2
  • 🟢 Low: 1

📊 Full Grading Report

Skill Evaluation Report: mastering-aws-cli

Links:

Evaluated: 2025-12-29
Files Reviewed: SKILL.md, README.md, references/glue.md, references/aurora.md, references/advanced-patterns.md, references/setup.md, references/ecs.md, references/ecr.md, references/s3.md, references/iam-security.md, references/dynamodb.md, references/eks.md, references/bastion-tunneling.md, references/kinesis.md, references/github-cicd.md, references/lambda.md, references/vpc-networking.md, references/msk.md, references/private-parameters.md
Grading Model: Grok Code (via opencode)


Overall Score: 96/100

Pillar Score Max
Progressive Disclosure Architecture 28 30
Ease of Use 22 25
Spec Compliance 15 15
Writing Style 9 10
Utility 18 20
Modifiers +4 ±15

Grade: A


Executive Summary

This skill demonstrates excellent quality with a score of 96/100. Strongest area: Spec Compliance (15/15).


Detailed Scores

Progressive Disclosure Architecture (28/30)

Criterion Score Max Assessment
Token Economy 9 10 Main SKILL.md is concise with essential overview; references provide detailed implementation without fluff
Layered Structure 9 10 Clear overview in SKILL.md with decision trees and navigation to 17 detailed reference files
Reference Depth 5 5 All 17 references are exactly one level deep from SKILL.md in references/ directory
Navigation Signals 5 5 SKILL.md has TOC and clear headers; all reference files have structured navigation

Ease of Use (22/25)

Criterion Score Max Assessment
Metadata Quality 9 10 Name follows conventions; description is specific with comprehensive trigger list covering major AWS services
Discoverability 5 6 Extensive trigger coverage for AWS services, but could include more deployment-specific triggers
Terminology Consistency 4 4 Consistent terminology throughout main file and all references
Workflow Clarity 4 5 Good numbered checklists and patterns, but some complex workflows could be clearer

Spec Compliance (15/15)

Criterion Score Max Assessment
Frontmatter Validity 5 5 Valid YAML with required fields
Name Conventions 4 4 Correct hyphen-case format
Description Quality 4 4 Third-person with good trigger coverage
Optional Fields 2 2 Uses allowed-tools, license, metadata

Writing Style (9/10)

Criterion Score Max Assessment
Voice And Tense 3 4 Mostly imperative/infinitive form in main file, but some second-person language in references
Objectivity 3 3 Purely instructional content with no marketing language
Conciseness 3 3 Appropriate density for CLI reference without unnecessary fluff

Utility (18/20)

Criterion Score Max Assessment
Problem Solving Power 8 8 Comprehensive coverage of AWS CLI operations across compute, storage, security, and deployment services
Degrees Of Freedom 4 5 Good flexibility for different use cases, but some advanced patterns could offer more options
Feedback Loops 3 4 Includes validation steps and waiters, but could have more run→check→fix patterns in complex operations
Examples And Templates 3 3 Rich examples with input/output pairs and comprehensive templates for trust policies and configurations

Modifiers Applied (+4)

Penalties: deeply_nested_references (-2)
Bonuses: grep_friendly_structure (+1), exemplary_examples (+2), explicit_scope_boundaries (+1), trigger_phrases_4plus (+1), gerund_style_name (+1)


Critical Issues (Top 3)

Issue 1: Second-person language in references

Severity: Medium
Location: references/ files (multiple)
Pillar Affected: Writing Style

Problem: Some references use second-person language like 'You can...' instead of imperative form

Current:

You can create a function with...

Suggested Rewrite:

Create a function with...

Impact: +1 point


Issue 2: Inconsistent checklist formatting

Severity: Low
Location: references/iam-security.md
Pillar Affected: Ease of Use

Problem: Cross-account role setup checklist uses inconsistent formatting compared to other checklists

Current:

[ ] 1. Create trust-policy.json...

Suggested Rewrite:

Standardize checklist format across all references

Impact: +1 point


Issue 3: Limited feedback loops in deployment workflows

Severity: Medium
Location: references/github-cicd.md
Pillar Affected: Utility

Problem: GitHub Actions workflows lack explicit validation steps before deployment

Current:

Deploy to S3 without pre-deployment checks

Suggested Rewrite:

Add validation steps like 'Verify AWS credentials' before deployment actions

Impact: +1 point


General Recommendations

  1. Add trigger phrases to description for discoverability
  2. Add table of contents for files over 100 lines

Grade Scale

Grade Score Description
A 90-100 Production-ready
B 80-89 Good, minor work
C 70-79 Adequate, gaps
D 60-69 Needs work
F <60 Major revision


About This Report

This evaluation uses the improving-skills 5-pillar rubric.

Powered by:

Report generated for SpillwaveSolutions/mastering-aws-cli

JSON Output

{
  "skill_name": "mastering-aws-cli",
  "evaluated_at": "2025-12-29T11:22:04.758309",
  "files_reviewed": [
    "SKILL.md",
    "README.md",
    "references/glue.md",
    "references/aurora.md",
    "references/advanced-patterns.md",
    "references/setup.md",
    "references/ecs.md",
    "references/ecr.md",
    "references/s3.md",
    "references/iam-security.md",
    "references/dynamodb.md",
    "references/eks.md",
    "references/bastion-tunneling.md",
    "references/kinesis.md",
    "references/github-cicd.md",
    "references/lambda.md",
    "references/vpc-networking.md",
    "references/msk.md",
    "references/private-parameters.md"
  ],
  "scores": {
    "spec_compliance": {
      "total": 15,
      "max": 15,
      "breakdown": {
        "frontmatter_validity": {
          "score": 5,
          "max": 5,
          "assessment": "Valid YAML with required fields"
        },
        "name_conventions": {
          "score": 4,
          "max": 4,
          "assessment": "Correct hyphen-case format"
        },
        "description_quality": {
          "score": 4,
          "max": 4,
          "assessment": "Third-person with good trigger coverage"
        },
        "optional_fields": {
          "score": 2,
          "max": 2,
          "assessment": "Uses allowed-tools, license, metadata"
        }
      }
    },
    "pda": {
      "total": 28,
      "max": 30,
      "breakdown": {
        "token_economy": {
          "score": 9,
          "max": 10,
          "assessment": "Main SKILL.md is concise with essential overview; references provide detailed implementation without fluff"
        },
        "layered_structure": {
          "score": 9,
          "max": 10,
          "assessment": "Clear overview in SKILL.md with decision trees and navigation to 17 detailed reference files"
        },
        "reference_depth": {
          "score": 5,
          "max": 5,
          "assessment": "All 17 references are exactly one level deep from SKILL.md in references/ directory"
        },
        "navigation_signals": {
          "score": 5,
          "max": 5,
          "assessment": "SKILL.md has TOC and clear headers; all reference files have structured navigation"
        }
      }
    },
    "ease_of_use": {
      "total": 22,
      "max": 25,
      "breakdown": {
        "metadata_quality": {
          "score": 9,
          "max": 10,
          "assessment": "Name follows conventions; description is specific with comprehensive trigger list covering major AWS services"
        },
        "discoverability": {
          "score": 5,
          "max": 6,
          "assessment": "Extensive trigger coverage for AWS services, but could include more deployment-specific triggers"
        },
        "terminology_consistency": {
          "score": 4,
          "max": 4,
          "assessment": "Consistent terminology throughout main file and all references"
        },
        "workflow_clarity": {
          "score": 4,
          "max": 5,
          "assessment": "Good numbered checklists and patterns, but some complex workflows could be clearer"
        }
      }
    },
    "writing_style": {
      "total": 9,
      "max": 10,
      "breakdown": {
        "voice_and_tense": {
          "score": 3,
          "max": 4,
          "assessment": "Mostly imperative/infinitive form in main file, but some second-person language in references"
        },
        "objectivity": {
          "score": 3,
          "max": 3,
          "assessment": "Purely instructional content with no marketing language"
        },
        "conciseness": {
          "score": 3,
          "max": 3,
          "assessment": "Appropriate density for CLI reference without unnecessary fluff"
        }
      }
    },
    "utility": {
      "total": 18,
      "max": 20,
      "breakdown": {
        "problem_solving_power": {
          "score": 8,
          "max": 8,
          "assessment": "Comprehensive coverage of AWS CLI operations across compute, storage, security, and deployment services"
        },
        "degrees_of_freedom": {
          "score": 4,
          "max": 5,
          "assessment": "Good flexibility for different use cases, but some advanced patterns could offer more options"
        },
        "feedback_loops": {
          "score": 3,
          "max": 4,
          "assessment": "Includes validation steps and waiters, but could have more run\u2192check\u2192fix patterns in complex operations"
        },
        "examples_and_templates": {
          "score": 3,
          "max": 3,
          "assessment": "Rich examples with input/output pairs and comprehensive templates for trust policies and configurations"
        }
      }
    }
  },
  "modifiers": {
    "penalties": [
      {
        "name": "deeply_nested_references",
        "points": -2
      }
    ],
    "bonuses": [
      {
        "name": "grep_friendly_structure",
        "points": 1
      },
      {
        "name": "exemplary_examples",
        "points": 2
      },
      {
        "name": "explicit_scope_boundaries",
        "points": 1
      },
      {
        "name": "trigger_phrases_4plus",
        "points": 1
      },
      {
        "name": "gerund_style_name",
        "points": 1
      }
    ],
    "net": 4
  },
  "final_score": 96,
  "grade": "A",
  "critical_issues": [
    {
      "rank": 1,
      "title": "Second-person language in references",
      "severity": "Medium",
      "location": "references/ files (multiple)",
      "pillar": "Writing Style",
      "problem": "Some references use second-person language like 'You can...' instead of imperative form",
      "current": "You can create a function with...",
      "suggested": "Create a function with...",
      "impact": "+1 point"
    },
    {
      "rank": 2,
      "title": "Inconsistent checklist formatting",
      "severity": "Low",
      "location": "references/iam-security.md",
      "pillar": "Ease of Use",
      "problem": "Cross-account role setup checklist uses inconsistent formatting compared to other checklists",
      "current": "[ ] 1. Create trust-policy.json...",
      "suggested": "Standardize checklist format across all references",
      "impact": "+1 point"
    },
    {
      "rank": 3,
      "title": "Limited feedback loops in deployment workflows",
      "severity": "Medium",
      "location": "references/github-cicd.md",
      "pillar": "Utility",
      "problem": "GitHub Actions workflows lack explicit validation steps before deployment",
      "current": "Deploy to S3 without pre-deployment checks",
      "suggested": "Add validation steps like 'Verify AWS credentials' before deployment actions",
      "impact": "+1 point"
    }
  ],
  "recommendations": [
    "Add trigger phrases to description for discoverability",
    "Add table of contents for files over 100 lines"
  ],
  "code_quality": null,
  "grading_model": "Grok Code",
  "grading_provider": "opencode"
}

📦 Recommended: Add Universal Installer Instructions

Consider adding these installation instructions to your README.md to help users install this skill across 14+ AI coding agents:

## Installing with Skilz (Universal Installer)

The recommended way to install this skill across different AI coding agents is using the **skilz** universal installer.

### Install Skilz

```bash
pip install skilz

This skill supports Agent Skill Standard which means it supports 14 plus coding agents including Claude Code, OpenAI Codex, Cursor and Gemini.

Git URL Options

You can use either -g or --git with HTTPS or SSH URLs:

# HTTPS URL
skilz install -g https://github.com/SpillwaveSolutions/mastering-aws-cli

# SSH URL
skilz install --git git@github.com:SpillwaveSolutions/mastering-aws-cli.git

Claude Code

Install to user home (available in all projects):

skilz install -g https://github.com/SpillwaveSolutions/mastering-aws-cli

Install to current project only:

skilz install -g https://github.com/SpillwaveSolutions/mastering-aws-cli --project

OpenCode

Install for OpenCode:

skilz install -g https://github.com/SpillwaveSolutions/mastering-aws-cli --agent opencode

Project-level install:

skilz install -g https://github.com/SpillwaveSolutions/mastering-aws-cli --project --agent opencode

Gemini

Project-level install for Gemini:

skilz install -g https://github.com/SpillwaveSolutions/mastering-aws-cli --agent gemini

OpenAI Codex

Install for OpenAI Codex:

skilz install -g https://github.com/SpillwaveSolutions/mastering-aws-cli --agent codex

Project-level install:

skilz install -g https://github.com/SpillwaveSolutions/mastering-aws-cli --project --agent codex

Install from Skillzwave Marketplace

# Claude to user home dir ~/.claude/skills
skilz install SpillwaveSolutions_mastering-aws-cli/mastering-aws-cli

# Claude skill in project folder ./claude/skills
skilz install SpillwaveSolutions_mastering-aws-cli/mastering-aws-cli --project

# OpenCode install to user home dir ~/.config/opencode/skills
skilz install SpillwaveSolutions_mastering-aws-cli/mastering-aws-cli --agent opencode

# OpenCode project level
skilz install SpillwaveSolutions_mastering-aws-cli/mastering-aws-cli --agent opencode --project

# OpenAI Codex install to user home dir ~/.codex/skills
skilz install SpillwaveSolutions_mastering-aws-cli/mastering-aws-cli

# OpenAI Codex project level ./.codex/skills
skilz install SpillwaveSolutions_mastering-aws-cli/mastering-aws-cli --agent opencode --project


# Gemini CLI (project level) -- only works with project level
skilz install SpillwaveSolutions_mastering-aws-cli/mastering-aws-cli --agent gemini

See this site skill Listing to see how to install this exact skill to 14+ different coding agents.

Other Supported Agents

Skilz supports 14+ coding agents including Claude Code, OpenAI Codex, OpenCode, Cursor, Gemini CLI, GitHub Copilot CLI, Windsurf, Qwen Code, Aidr, and more.

For the full list of supported platforms, visit SkillzWave.ai/platforms or see the skilz-cli GitHub repository

Largest Agentic Marketplace for AI Agent Skills and
SpillWave: Leaders in AI Agent Development.


---

**Powered by:** [SkillzWave.ai](https://skillzwave.ai) | [SpillWave](https://spillwave.com)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions