-
Notifications
You must be signed in to change notification settings - Fork 0
Description
🏆 Agent Skill Grading Report
Score: 97/100 | Grade: A
Quick Summary of Agent Skill Grades
Pillar Scores for Agent Skill
| Pillar | Score | Max |
|---|---|---|
| Spec Compliance | 15 | 15 |
| Progressive Disclosure | 27 | 30 |
| Ease of Use | 22 | 25 |
| Writing Style | 7 | 10 |
| Utility | 18 | 20 |
| Modifiers | +8 | ±15 |
Issues Found: 4
- 🔴 High: 0
- 🟡 Medium: 2
- 🟢 Low: 2
📊 Full Grading Report for Agent Skill
Skill Evaluation Report: developing-with-docker
Links:
- 📁 GitHub: SpillwaveSolutions/developing-with-docker-agentic-skill
- 🛒 Marketplace: View on SkillzWave
- 📤 Submit Skill: Submit to SkillzWave - Skills are ranked, graded, and scanned for security
- 📊 Tracking: All Graded Skills
Evaluated: 2026-01-12
Files Reviewed: skills/developing-with-docker/SKILL.md, references/guide-foundations.md, references/guide-rancher-migration.md, references/guide-installation-connectivity.md, references/guide-advanced-debugging.md, references/guide-cli-debugging.md, references/guide-networking-compose-ops.md
Grading Model: Claude (default) (via claude)
Overall Score: 97/100
| Pillar | Score | Max |
|---|---|---|
| Progressive Disclosure Architecture | 27 | 30 |
| Ease of Use | 22 | 25 |
| Spec Compliance | 15 | 15 |
| Writing Style | 7 | 10 |
| Utility | 18 | 20 |
| Modifiers | +8 | ±15 |
Grade: A
Executive Summary
This skill demonstrates excellent quality with a score of 97/100. Strongest area: Spec Compliance (15/15).
Detailed Scores
Progressive Disclosure Architecture (27/30)
| Criterion | Score | Max | Assessment |
|---|---|---|---|
| Token Economy | 9 | 10 | SKILL.md is lean (~100 lines); references contain detailed prose that could be more concise in places. |
| Layered Structure | 9 | 10 | Excellent hub-and-spoke design: SKILL.md provides workflow overview, 6 references contain deep technical content. |
| Reference Depth | 5 | 5 | All 6 references are exactly one level deep from SKILL.md; no nested sub-references. |
| Navigation Signals | 4 | 5 | All reference files have TOC; SKILL.md lacks TOC but is short enough to scan; 'Summary:' prefixes aid navigation. |
Ease of Use (22/25)
| Criterion | Score | Max | Assessment |
|---|---|---|---|
| Metadata Quality | 9 | 10 | Name follows kebab-case; description includes specific triggers like 'debug Docker', 'fix Docker networking'. |
| Discoverability | 6 | 6 | Strong trigger terms: 'debug Docker', 'troubleshoot containers', 'Docker Compose issues', 'volume permissions'. |
| Terminology Consistency | 3 | 4 | Consistent terms for 'bind mount' vs 'volume'; occasional mix of 'Desktop' and 'Docker Desktop'. |
| Workflow Clarity | 4 | 5 | Clear 5-step debugging workflow with numbered steps; validation checklist provided; findings template included. |
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 license, metadata |
Writing Style (7/10)
| Criterion | Score | Max | Assessment |
|---|---|---|---|
| Voice And Tense | 3 | 4 | Mostly imperative ('Use', 'Check', 'Verify'); some sections drift into explanatory prose with second-person. |
| Objectivity | 2 | 3 | Largely instructional; occasional subjective phrases like 'game-changer' and 'polished ergonomics'. |
| Conciseness | 2 | 3 | SKILL.md is concise; references contain valuable but verbose prose that exceeds Claude-optimal density. |
Utility (18/20)
| Criterion | Score | Max | Assessment |
|---|---|---|---|
| Problem Solving Power | 8 | 8 | Addresses major Docker debugging gaps: cross-platform gotchas, UID/GID, networking, distroless debugging. |
| Degrees Of Freedom | 5 | 5 | Appropriate constraints: branching by symptom allows flexibility; platform-specific guidance is prescriptive where needed. |
| Feedback Loops | 3 | 4 | Validation checklist and findings template enable run-check patterns; references include verification commands. |
| Examples And Templates | 2 | 3 | Good example requests and findings template in SKILL.md; references have code examples but lack structured input/output pairs. |
Modifiers Applied (+8)
Penalties: None
Bonuses: copy_paste_checklists (+2), grep_friendly_structure (+1), explicit_scope_boundaries (+1), trigger_phrases_4plus (+1), quality_pre_commit_checklist (+2), gerund_style_name (+1)
Critical Issues (Top 4)
Issue 1: Marketing language in references
Severity: Medium
Location: references/guide-foundations.md:Section 2.1, 7.1
Pillar Affected: Writing Style
Problem: Subjective phrases reduce instructional clarity
Current:
'polished ergonomics', 'VirtioFS has been a game-changer'
Suggested Rewrite:
'mature tooling and integrated features', 'VirtioFS significantly improves file operation speeds'
Impact: +1 points
Issue 2: Reference files lack summaries for longer sections
Severity: Low
Location: references/guide-networking-compose-ops.md:Sections 6-14
Pillar Affected: PDA
Problem: Some sections are 30+ lines without Summary prefix, reducing scannability
Current:
Sections 6.1, 6.2, 6.3 lack summary lines
Suggested Rewrite:
Add 'Summary:' line after each subsection header for quick scanning
Impact: +1 points
Issue 3: Verbose explanatory prose in references
Severity: Medium
Location: references/guide-foundations.md:Multiple sections
Pillar Affected: Writing Style
Problem: Prose-heavy explanations could be condensed without losing meaning
Current:
Multi-paragraph explanations for concepts that could be bullet points
Suggested Rewrite:
Convert narrative paragraphs to structured bullet points where possible
Impact: +1 points
Issue 4: SKILL.md missing 'When Not to Use' examples
Severity: Low
Location: SKILL.md:Lines 89-92
Pillar Affected: Ease of Use
Problem: Exclusion criteria are vague without concrete examples
Current:
'general Kubernetes orchestration guidance'
Suggested Rewrite:
Add example: 'Do not use for: kubectl debugging, Helm chart issues, pod scheduling'
Impact: +1 points
General Recommendations
- Add trigger phrases to description for discoverability
- 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 Claude Skills Best Practices.
Powered by:
- SkillzWave - Claude Skills Marketplace
- SpillWave - AI Solutions
Report generated for SpillwaveSolutions/developing-with-docker-agentic-skill
JSON Output
{
"skill_name": "developing-with-docker",
"evaluated_at": "2026-01-12T20:22:40.196172",
"files_reviewed": [
"skills/developing-with-docker/SKILL.md",
"references/guide-foundations.md",
"references/guide-rancher-migration.md",
"references/guide-installation-connectivity.md",
"references/guide-advanced-debugging.md",
"references/guide-cli-debugging.md",
"references/guide-networking-compose-ops.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 license, metadata"
}
}
},
"pda": {
"total": 27,
"max": 30,
"breakdown": {
"token_economy": {
"score": 9,
"max": 10,
"assessment": "SKILL.md is lean (~100 lines); references contain detailed prose that could be more concise in places."
},
"layered_structure": {
"score": 9,
"max": 10,
"assessment": "Excellent hub-and-spoke design: SKILL.md provides workflow overview, 6 references contain deep technical content."
},
"reference_depth": {
"score": 5,
"max": 5,
"assessment": "All 6 references are exactly one level deep from SKILL.md; no nested sub-references."
},
"navigation_signals": {
"score": 4,
"max": 5,
"assessment": "All reference files have TOC; SKILL.md lacks TOC but is short enough to scan; 'Summary:' prefixes aid navigation."
}
}
},
"ease_of_use": {
"total": 22,
"max": 25,
"breakdown": {
"metadata_quality": {
"score": 9,
"max": 10,
"assessment": "Name follows kebab-case; description includes specific triggers like 'debug Docker', 'fix Docker networking'."
},
"discoverability": {
"score": 6,
"max": 6,
"assessment": "Strong trigger terms: 'debug Docker', 'troubleshoot containers', 'Docker Compose issues', 'volume permissions'."
},
"terminology_consistency": {
"score": 3,
"max": 4,
"assessment": "Consistent terms for 'bind mount' vs 'volume'; occasional mix of 'Desktop' and 'Docker Desktop'."
},
"workflow_clarity": {
"score": 4,
"max": 5,
"assessment": "Clear 5-step debugging workflow with numbered steps; validation checklist provided; findings template included."
}
}
},
"writing_style": {
"total": 7,
"max": 10,
"breakdown": {
"voice_and_tense": {
"score": 3,
"max": 4,
"assessment": "Mostly imperative ('Use', 'Check', 'Verify'); some sections drift into explanatory prose with second-person."
},
"objectivity": {
"score": 2,
"max": 3,
"assessment": "Largely instructional; occasional subjective phrases like 'game-changer' and 'polished ergonomics'."
},
"conciseness": {
"score": 2,
"max": 3,
"assessment": "SKILL.md is concise; references contain valuable but verbose prose that exceeds Claude-optimal density."
}
}
},
"utility": {
"total": 18,
"max": 20,
"breakdown": {
"problem_solving_power": {
"score": 8,
"max": 8,
"assessment": "Addresses major Docker debugging gaps: cross-platform gotchas, UID/GID, networking, distroless debugging."
},
"degrees_of_freedom": {
"score": 5,
"max": 5,
"assessment": "Appropriate constraints: branching by symptom allows flexibility; platform-specific guidance is prescriptive where needed."
},
"feedback_loops": {
"score": 3,
"max": 4,
"assessment": "Validation checklist and findings template enable run-check patterns; references include verification commands."
},
"examples_and_templates": {
"score": 2,
"max": 3,
"assessment": "Good example requests and findings template in SKILL.md; references have code examples but lack structured input/output pairs."
}
}
}
},
"modifiers": {
"penalties": [],
"bonuses": [
{
"name": "copy_paste_checklists",
"points": 2
},
{
"name": "grep_friendly_structure",
"points": 1
},
{
"name": "explicit_scope_boundaries",
"points": 1
},
{
"name": "trigger_phrases_4plus",
"points": 1
},
{
"name": "quality_pre_commit_checklist",
"points": 2
},
{
"name": "gerund_style_name",
"points": 1
}
],
"net": 8
},
"final_score": 97,
"grade": "A",
"critical_issues": [
{
"rank": 1,
"title": "Marketing language in references",
"severity": "Medium",
"location": "references/guide-foundations.md:Section 2.1, 7.1",
"pillar": "Writing Style",
"problem": "Subjective phrases reduce instructional clarity",
"current": "'polished ergonomics', 'VirtioFS has been a game-changer'",
"suggested": "'mature tooling and integrated features', 'VirtioFS significantly improves file operation speeds'",
"impact": "+1 points"
},
{
"rank": 2,
"title": "Reference files lack summaries for longer sections",
"severity": "Low",
"location": "references/guide-networking-compose-ops.md:Sections 6-14",
"pillar": "PDA",
"problem": "Some sections are 30+ lines without Summary prefix, reducing scannability",
"current": "Sections 6.1, 6.2, 6.3 lack summary lines",
"suggested": "Add 'Summary:' line after each subsection header for quick scanning",
"impact": "+1 points"
},
{
"rank": 3,
"title": "Verbose explanatory prose in references",
"severity": "Medium",
"location": "references/guide-foundations.md:Multiple sections",
"pillar": "Writing Style",
"problem": "Prose-heavy explanations could be condensed without losing meaning",
"current": "Multi-paragraph explanations for concepts that could be bullet points",
"suggested": "Convert narrative paragraphs to structured bullet points where possible",
"impact": "+1 points"
},
{
"rank": 4,
"title": "SKILL.md missing 'When Not to Use' examples",
"severity": "Low",
"location": "SKILL.md:Lines 89-92",
"pillar": "Ease of Use",
"problem": "Exclusion criteria are vague without concrete examples",
"current": "'general Kubernetes orchestration guidance'",
"suggested": "Add example: 'Do not use for: kubectl debugging, Helm chart issues, pod scheduling'",
"impact": "+1 points"
}
],
"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"
}Links:
- 📁 GitHub: spillwavesolutions/developing-with-docker-agentic-skill
- 🛒 Marketplace: View on SkillzWave
- 📤 Submit Skill: Submit to SkillzWave - Skills are ranked, graded, and scanned for security
- 📊 Tracking: All Graded Skills
📦 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 skilzThis skill supports Agent Skill Standard which means it supports 14 plus coding agents including Claude Code, OpenAI Codex, Cursor and Gemini.
Git URL Options
# Install for Claude Code (your home directory)
skilz install -g https://github.com/spillwavesolutions/developing-with-docker-agentic-skill
# Or from the SkillzWave marketplace
skilz install spillwavesolutions__developing-with-docker-agentic-skill__developing-with-docker
Claude Code
Install to user home (available in all projects):
skilz install -g https://github.com/spillwavesolutions/developing-with-docker-agentic-skillInstall to current project only:
skilz install -g https://github.com/spillwavesolutions/developing-with-docker-agentic-skill --projectOpenCode
Install for OpenCode:
# OpenCode
skilz install https://github.com/spillwavesolutions/developing-with-docker-agentic-skill --agent opencode
Install for Codex and Gemini too
# Gemini CLI
skilz install https://github.com/spillwavesolutions/developing-with-docker-agentic-skill --agent gemini
# OpenAI Codex
skilz install https://github.com/spillwavesolutions/developing-with-docker-agentic-skill --agent codex
Project-level install:
skilz install https://github.com/spillwavesolutions/developing-with-docker-agentic-skill --project --agent codexInstall from Skillzwave Marketplace
skilz install spillwavesolutions__developing-with-docker-agentic-skill__developing-with-docker --projectSee this site skill Listing to see how to install this exact skill to 14+ different coding agents.
Other Supported Agents
Skilz supports 20+ coding agents including Claude Code, OpenAI Codex, OpenCode, Cursor, Gemini CLI, GitHub Copilot CLI, Windsurf, Qwen Code, Aidr, and more.
See the skill on SkillzWave for agent-specific install commands, or check the skilz-cli docs.
SkillzWave is a skill marketplace for AI agents. SpillWave (where I work) builds AI agent tools.
---
## About This Report
This evaluation uses the [Claude Skills Best Practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices).
**Powered by:**
- [SkillzWave](https://skillzwave.ai) - Claude Skills Marketplace
- [SpillWave](https://spillwave.com) - AI Solutions
*Report generated for [spillwavesolutions/developing-with-docker-agentic-skill](https://github.com/spillwavesolutions/developing-with-docker-agentic-skill/blob/main/SKILL.md)*