Skip to content

Skill Grading Report: mastering-aws-cli - Score 98/100 (A) #35

@RichardHightower

Description

@RichardHightower

🏆 Skill Grading Report

Score: 98/100 | Grade: A

Quick Summary

Pillar Scores

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

Issues Found: 3

  • 🔴 High: 0
  • 🟡 Medium: 0
  • 🟢 Low: 3

📊 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: Claude (default) (via claude)


Overall Score: 98/100

Pillar Score Max
Progressive Disclosure Architecture 28 30
Ease of Use 24 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 98/100. Strongest area: Spec Compliance (15/15).


Detailed Scores

Progressive Disclosure Architecture (28/30)

Criterion Score Max Assessment
Token Economy 9 10 Dense, practical content throughout; minimal fluff; every section delivers actionable CLI commands
Layered Structure 9 10 Excellent hierarchy: SKILL.md overview with 17 deep reference files for specific services
Reference Depth 5 5 All references exactly one level deep; no nested reference chains; clean navigation
Navigation Signals 5 5 TOC in all reference files over 100 lines; decision trees for quick navigation; clear section headers

Ease of Use (24/25)

Criterion Score Max Assessment
Metadata Quality 9 10 Comprehensive triggers (35+); specific description with service list and example phrases
Discoverability 6 6 Extensive trigger list covers major AWS services; activates appropriately on aws-related queries
Terminology Consistency 4 4 Consistent terminology throughout; SSO vs IAM Identity Center noted properly
Workflow Clarity 5 5 Checklists provided for complex tasks (cross-account roles, GitHub OIDC); numbered steps throughout

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 4 4 Imperative form consistently used in commands and descriptions; no second-person pronouns
Objectivity 3 3 Purely instructional; no marketing language; factual technical content throughout
Conciseness 2 3 Very dense; some verbose JSON examples could use more inline comments for clarity

Utility (18/20)

Criterion Score Max Assessment
Problem Solving Power 7 8 Addresses major AWS CLI workflows; comprehensive service coverage; practical patterns
Degrees Of Freedom 5 5 Appropriate constraints for reference guide; provides templates without over-constraining
Feedback Loops 3 4 Waiters, dry-run patterns, verification commands included; checklists for complex workflows
Examples And Templates 3 3 Extensive real-world examples with output; JSON templates for 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: Missing When Not to Use section in references

Severity: Low
Location: references/*.md
Pillar Affected: Utility

Problem: Reference files lack boundary definitions for when NOT to use specific service commands

Current:

Reference files jump straight into commands without scope limitations

Suggested Rewrite:

Add brief 'Scope' section at top of each reference noting what's NOT covered (e.g., SDK usage, CloudFormation)

Impact: +1 point


Issue 2: GitHub CICD reference not visible in sampled files

Severity: Low
Location: references/github-cicd.md
Pillar Affected: PDA

Problem: Could not verify github-cicd.md content; navigation table references it but content depth unknown

Current:

File exists but not sampled

Suggested Rewrite:

Ensure github-cicd.md follows same comprehensive pattern as other references

Impact: +0 points (likely already good)


Issue 3: JSON blocks could benefit from inline annotations

Severity: Low
Location: SKILL.md:common patterns, references/*.md
Pillar Affected: Writing Style

Problem: Large JSON policy blocks lack inline comments explaining key fields

Current:

Raw JSON with explanatory text before/after but not inline

Suggested Rewrite:

Add # comments within JSON (where supported) or JSONC format snippets for educational value

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-29T10:57:22.798929",
  "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": "Dense, practical content throughout; minimal fluff; every section delivers actionable CLI commands"
        },
        "layered_structure": {
          "score": 9,
          "max": 10,
          "assessment": "Excellent hierarchy: SKILL.md overview with 17 deep reference files for specific services"
        },
        "reference_depth": {
          "score": 5,
          "max": 5,
          "assessment": "All references exactly one level deep; no nested reference chains; clean navigation"
        },
        "navigation_signals": {
          "score": 5,
          "max": 5,
          "assessment": "TOC in all reference files over 100 lines; decision trees for quick navigation; clear section headers"
        }
      }
    },
    "ease_of_use": {
      "total": 24,
      "max": 25,
      "breakdown": {
        "metadata_quality": {
          "score": 9,
          "max": 10,
          "assessment": "Comprehensive triggers (35+); specific description with service list and example phrases"
        },
        "discoverability": {
          "score": 6,
          "max": 6,
          "assessment": "Extensive trigger list covers major AWS services; activates appropriately on aws-related queries"
        },
        "terminology_consistency": {
          "score": 4,
          "max": 4,
          "assessment": "Consistent terminology throughout; SSO vs IAM Identity Center noted properly"
        },
        "workflow_clarity": {
          "score": 5,
          "max": 5,
          "assessment": "Checklists provided for complex tasks (cross-account roles, GitHub OIDC); numbered steps throughout"
        }
      }
    },
    "writing_style": {
      "total": 9,
      "max": 10,
      "breakdown": {
        "voice_and_tense": {
          "score": 4,
          "max": 4,
          "assessment": "Imperative form consistently used in commands and descriptions; no second-person pronouns"
        },
        "objectivity": {
          "score": 3,
          "max": 3,
          "assessment": "Purely instructional; no marketing language; factual technical content throughout"
        },
        "conciseness": {
          "score": 2,
          "max": 3,
          "assessment": "Very dense; some verbose JSON examples could use more inline comments for clarity"
        }
      }
    },
    "utility": {
      "total": 18,
      "max": 20,
      "breakdown": {
        "problem_solving_power": {
          "score": 7,
          "max": 8,
          "assessment": "Addresses major AWS CLI workflows; comprehensive service coverage; practical patterns"
        },
        "degrees_of_freedom": {
          "score": 5,
          "max": 5,
          "assessment": "Appropriate constraints for reference guide; provides templates without over-constraining"
        },
        "feedback_loops": {
          "score": 3,
          "max": 4,
          "assessment": "Waiters, dry-run patterns, verification commands included; checklists for complex workflows"
        },
        "examples_and_templates": {
          "score": 3,
          "max": 3,
          "assessment": "Extensive real-world examples with output; JSON templates for 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": 98,
  "grade": "A",
  "critical_issues": [
    {
      "rank": 1,
      "title": "Missing When Not to Use section in references",
      "severity": "Low",
      "location": "references/*.md",
      "pillar": "Utility",
      "problem": "Reference files lack boundary definitions for when NOT to use specific service commands",
      "current": "Reference files jump straight into commands without scope limitations",
      "suggested": "Add brief 'Scope' section at top of each reference noting what's NOT covered (e.g., SDK usage, CloudFormation)",
      "impact": "+1 point"
    },
    {
      "rank": 2,
      "title": "GitHub CICD reference not visible in sampled files",
      "severity": "Low",
      "location": "references/github-cicd.md",
      "pillar": "PDA",
      "problem": "Could not verify github-cicd.md content; navigation table references it but content depth unknown",
      "current": "File exists but not sampled",
      "suggested": "Ensure github-cicd.md follows same comprehensive pattern as other references",
      "impact": "+0 points (likely already good)"
    },
    {
      "rank": 3,
      "title": "JSON blocks could benefit from inline annotations",
      "severity": "Low",
      "location": "SKILL.md:common patterns, references/*.md",
      "pillar": "Writing Style",
      "problem": "Large JSON policy blocks lack inline comments explaining key fields",
      "current": "Raw JSON with explanatory text before/after but not inline",
      "suggested": "Add # comments within JSON (where supported) or JSONC format snippets for educational value",
      "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": "Claude (default)",
  "grading_provider": "claude"
}

📦 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