Skill Grading Report: lint-fixer - Score 77/100 (C)

# 📝 Skill Grading Report

**Score:** 77/100 | **Grade:** C

## Quick Summary

### Pillar Scores

| Pillar | Score | Max |
|--------|-------|-----|
| Spec Compliance | 11 | 15 |
| Progressive Disclosure | 23 | 30 |
| Ease of Use | 20 | 25 |
| Writing Style | 8 | 10 |
| Utility | 14 | 20 |
| Modifiers | +1 | ±15 |

### Issues Found: 4
- 🔴 High: 0
- 🟡 Medium: 3
- 🟢 Low: 1

## 📊 Full Grading Report

# Skill Evaluation Report: lint-fixer

**Links:**
- 📁 **GitHub:** [yamadashy/repomix](https://github.com/yamadashy/repomix/blob/main/.claude/skills/lint-fixer/SKILL.md)
- 🛒 **Marketplace:** [View on SkillzWave](https://skillzwave.ai/skill/yamadashy__repomix__-claude__skills__lint-fixer__SKILL/)
- 📤 **Submit Skill:** [Submit to SkillzWave](https://skillzwave.ai/submit/) - Skills are ranked, graded, and scanned for security
- 📊 **Tracking:** [All Graded Skills](https://github.com/SpillwaveSolutions/skill_improver/issues)

**Evaluated:** 2025-12-29
**Files Reviewed:** .claude/skills/lint-fixer/SKILL.md
**Grading Model:** Claude (default) (via claude)

---

## Overall Score: 77/100

| Pillar | Score | Max |
|--------|-------|-----|
| Progressive Disclosure Architecture | 23 | 30 |
| Ease of Use | 20 | 25 |
| Spec Compliance | 11 | 15 |
| Writing Style | 8 | 10 |
| Utility | 14 | 20 |
| Modifiers | +1 | ±15 |

**Grade: C**

---

## Executive Summary

This skill shows solid fundamentals with a score of 77/100. Strongest area: **Ease of Use** (20/25).

---

## Detailed Scores

### Progressive Disclosure Architecture (23/30)

| Criterion | Score | Max | Assessment |
|-----------|-------|-----|------------|
| Token Economy | 8 | 10 | Concise content with minimal fluff; each section serves a purpose though some bullets could be tighter |
| Layered Structure | 7 | 10 | Self-contained skill with no reference files; appropriate for scope but missed opportunity to offload config details |
| Reference Depth | 4 | 5 | No references needed given simplicity; config files mentioned but not elaborated in separate docs |
| Navigation Signals | 4 | 5 | Clear section headers; file under 100 lines so no TOC needed; structure is navigable |

### Ease of Use (20/25)

| Criterion | Score | Max | Assessment |
|-----------|-------|-----|------------|
| Metadata Quality | 8 | 10 | Name follows conventions; description includes trigger terms but could be more specific about when to invoke |
| Discoverability | 5 | 6 | Good trigger terms (lint, fix, code changes, style guidelines); activates appropriately for linting tasks |
| Terminology Consistency | 4 | 4 | Consistent terminology throughout; tools named clearly and used consistently |
| Workflow Clarity | 3 | 5 | Numbered workflow steps present but lacks checklist format; no explicit validation gates |

### Spec Compliance (11/15)

| Criterion | Score | Max | Assessment |
|-----------|-------|-----|------------|
| Frontmatter Validity | 4 | 5 | Valid YAML but minor formatting issues |
| Name Conventions | 4 | 4 | Correct hyphen-case format |
| Description Quality | 3 | 4 | Only 1-2 trigger phrases |
| Optional Fields | 0 | 2 | No optional fields used (no penalty) |

### Writing Style (8/10)

| Criterion | Score | Max | Assessment |
|-----------|-------|-----|------------|
| Voice And Tense | 3 | 4 | Mostly imperative/infinitive form; occasional descriptive statements; no second-person |
| Objectivity | 3 | 3 | No marketing language; purely instructional and factual |
| Conciseness | 2 | 3 | Good density but some lines like 'Fix linting issues while preserving code functionality' are generic |

### Utility (14/20)

| Criterion | Score | Max | Assessment |
|-----------|-------|-----|------------|
| Problem Solving Power | 5 | 8 | Addresses common linting workflow but lacks troubleshooting guidance for complex scenarios |
| Degrees Of Freedom | 4 | 5 | Appropriate constraints for task; clear tool sequence but allows judgment on manual fixes |
| Feedback Loops | 3 | 4 | Run→verify→test pattern present; lacks explicit success/failure criteria |
| Examples And Templates | 2 | 3 | No input/output examples; config file locations noted but no sample output or error patterns |

### Modifiers Applied (+1)

**Penalties:** None
**Bonuses:** grep_friendly_structure (+1)

---

## Critical Issues (Top 4)

### Issue 1: Missing Error Pattern Examples

**Severity:** Medium
**Location:** SKILL.md:Workflow
**Pillar Affected:** Utility

**Problem:** No examples of common lint errors and their fixes

**Current:**
```
3. Fix issues - Biome/oxlint auto-fix most style issues
```

**Suggested Rewrite:**
```
Add section with 2-3 common error patterns and resolution approaches
```

**Impact:** +2 points

---

### Issue 2: Generic Opening Statement

**Severity:** Low
**Location:** SKILL.md:line 8
**Pillar Affected:** Writing Style

**Problem:** Opening line is generic and doesn't add value

**Current:**
```
Fix linting issues while preserving code functionality.
```

**Suggested Rewrite:**
```
Remove or replace with specific guidance like 'Run lint pipeline: Biome → oxlint → tsgo → secretlint'
```

**Impact:** +1 point

---

### Issue 3: Workflow Lacks Validation Checkpoints

**Severity:** Medium
**Location:** SKILL.md:Workflow
**Pillar Affected:** Ease of Use

**Problem:** No explicit success criteria or checklist format for complex multi-tool workflow

**Current:**
```
4. Run `npm run lint` again to verify
```

**Suggested Rewrite:**
```
Add checklist: '- [ ] All tools exit with 0; - [ ] No TypeScript errors; - [ ] Tests pass'
```

**Impact:** +2 points

---

### Issue 4: Missing Troubleshooting Section

**Severity:** Medium
**Location:** SKILL.md
**Pillar Affected:** Utility

**Problem:** No guidance for when auto-fix fails or conflicts between tools

**Current:**
```
No troubleshooting section present
```

**Suggested Rewrite:**
```
Add brief troubleshooting: 'If Biome and oxlint conflict: prioritize Biome settings'
```

**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 [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 [yamadashy/repomix](https://github.com/yamadashy/repomix/blob/main/.claude/skills/lint-fixer/SKILL.md)*

## JSON Output

```json
{
  "skill_name": "lint-fixer",
  "evaluated_at": "2025-12-29T17:31:43.479104",
  "files_reviewed": [
    ".claude/skills/lint-fixer/SKILL.md"
  ],
  "scores": {
    "spec_compliance": {
      "total": 11,
      "max": 15,
      "breakdown": {
        "frontmatter_validity": {
          "score": 4,
          "max": 5,
          "assessment": "Valid YAML but minor formatting issues"
        },
        "name_conventions": {
          "score": 4,
          "max": 4,
          "assessment": "Correct hyphen-case format"
        },
        "description_quality": {
          "score": 3,
          "max": 4,
          "assessment": "Only 1-2 trigger phrases"
        },
        "optional_fields": {
          "score": 0,
          "max": 2,
          "assessment": "No optional fields used (no penalty)"
        }
      }
    },
    "pda": {
      "total": 23,
      "max": 30,
      "breakdown": {
        "token_economy": {
          "score": 8,
          "max": 10,
          "assessment": "Concise content with minimal fluff; each section serves a purpose though some bullets could be tighter"
        },
        "layered_structure": {
          "score": 7,
          "max": 10,
          "assessment": "Self-contained skill with no reference files; appropriate for scope but missed opportunity to offload config details"
        },
        "reference_depth": {
          "score": 4,
          "max": 5,
          "assessment": "No references needed given simplicity; config files mentioned but not elaborated in separate docs"
        },
        "navigation_signals": {
          "score": 4,
          "max": 5,
          "assessment": "Clear section headers; file under 100 lines so no TOC needed; structure is navigable"
        }
      }
    },
    "ease_of_use": {
      "total": 20,
      "max": 25,
      "breakdown": {
        "metadata_quality": {
          "score": 8,
          "max": 10,
          "assessment": "Name follows conventions; description includes trigger terms but could be more specific about when to invoke"
        },
        "discoverability": {
          "score": 5,
          "max": 6,
          "assessment": "Good trigger terms (lint, fix, code changes, style guidelines); activates appropriately for linting tasks"
        },
        "terminology_consistency": {
          "score": 4,
          "max": 4,
          "assessment": "Consistent terminology throughout; tools named clearly and used consistently"
        },
        "workflow_clarity": {
          "score": 3,
          "max": 5,
          "assessment": "Numbered workflow steps present but lacks checklist format; no explicit validation gates"
        }
      }
    },
    "writing_style": {
      "total": 8,
      "max": 10,
      "breakdown": {
        "voice_and_tense": {
          "score": 3,
          "max": 4,
          "assessment": "Mostly imperative/infinitive form; occasional descriptive statements; no second-person"
        },
        "objectivity": {
          "score": 3,
          "max": 3,
          "assessment": "No marketing language; purely instructional and factual"
        },
        "conciseness": {
          "score": 2,
          "max": 3,
          "assessment": "Good density but some lines like 'Fix linting issues while preserving code functionality' are generic"
        }
      }
    },
    "utility": {
      "total": 14,
      "max": 20,
      "breakdown": {
        "problem_solving_power": {
          "score": 5,
          "max": 8,
          "assessment": "Addresses common linting workflow but lacks troubleshooting guidance for complex scenarios"
        },
        "degrees_of_freedom": {
          "score": 4,
          "max": 5,
          "assessment": "Appropriate constraints for task; clear tool sequence but allows judgment on manual fixes"
        },
        "feedback_loops": {
          "score": 3,
          "max": 4,
          "assessment": "Run\u2192verify\u2192test pattern present; lacks explicit success/failure criteria"
        },
        "examples_and_templates": {
          "score": 2,
          "max": 3,
          "assessment": "No input/output examples; config file locations noted but no sample output or error patterns"
        }
      }
    }
  },
  "modifiers": {
    "penalties": [],
    "bonuses": [
      {
        "name": "grep_friendly_structure",
        "points": 1
      }
    ],
    "net": 1
  },
  "final_score": 77,
  "grade": "C",
  "critical_issues": [
    {
      "rank": 1,
      "title": "Missing Error Pattern Examples",
      "severity": "Medium",
      "location": "SKILL.md:Workflow",
      "pillar": "Utility",
      "problem": "No examples of common lint errors and their fixes",
      "current": "3. Fix issues - Biome/oxlint auto-fix most style issues",
      "suggested": "Add section with 2-3 common error patterns and resolution approaches",
      "impact": "+2 points"
    },
    {
      "rank": 2,
      "title": "Generic Opening Statement",
      "severity": "Low",
      "location": "SKILL.md:line 8",
      "pillar": "Writing Style",
      "problem": "Opening line is generic and doesn't add value",
      "current": "Fix linting issues while preserving code functionality.",
      "suggested": "Remove or replace with specific guidance like 'Run lint pipeline: Biome \u2192 oxlint \u2192 tsgo \u2192 secretlint'",
      "impact": "+1 point"
    },
    {
      "rank": 3,
      "title": "Workflow Lacks Validation Checkpoints",
      "severity": "Medium",
      "location": "SKILL.md:Workflow",
      "pillar": "Ease of Use",
      "problem": "No explicit success criteria or checklist format for complex multi-tool workflow",
      "current": "4. Run `npm run lint` again to verify",
      "suggested": "Add checklist: '- [ ] All tools exit with 0; - [ ] No TypeScript errors; - [ ] Tests pass'",
      "impact": "+2 points"
    },
    {
      "rank": 4,
      "title": "Missing Troubleshooting Section",
      "severity": "Medium",
      "location": "SKILL.md",
      "pillar": "Utility",
      "problem": "No guidance for when auto-fix fails or conflicts between tools",
      "current": "No troubleshooting section present",
      "suggested": "Add brief troubleshooting: 'If Biome and oxlint conflict: prioritize Biome settings'",
      "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:

```markdown
## 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](https://agentskills.io/) 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:

```bash
# HTTPS URL
skilz install -g https://github.com/yamadashy/repomix

# SSH URL
skilz install --git git@github.com:yamadashy/repomix.git
```

### Claude Code

Install to user home (available in all projects):
```bash
skilz install -g https://github.com/yamadashy/repomix
```

Install to current project only:
```bash
skilz install -g https://github.com/yamadashy/repomix --project
```

### OpenCode

Install for [OpenCode](https://opencode.ai):
```bash
skilz install -g https://github.com/yamadashy/repomix --agent opencode
```

Project-level install:
```bash
skilz install -g https://github.com/yamadashy/repomix --project --agent opencode
```

### Gemini

Project-level install for Gemini:
```bash
skilz install -g https://github.com/yamadashy/repomix --agent gemini
```

### OpenAI Codex

Install for OpenAI Codex:
```bash
skilz install -g https://github.com/yamadashy/repomix --agent codex
```

Project-level install:
```bash
skilz install -g https://github.com/yamadashy/repomix --project --agent codex
```


### Install from Skillzwave Marketplace
```
# Claude to user home dir ~/.claude/skills
skilz install yamadashy_repomix/-claude__skills__lint-fixer

# Claude skill in project folder ./claude/skills
skilz install yamadashy_repomix/-claude__skills__lint-fixer --project

# OpenCode install to user home dir ~/.config/opencode/skills
skilz install yamadashy_repomix/-claude__skills__lint-fixer --agent opencode

# OpenCode project level
skilz install yamadashy_repomix/-claude__skills__lint-fixer --agent opencode --project

# OpenAI Codex install to user home dir ~/.codex/skills
skilz install yamadashy_repomix/-claude__skills__lint-fixer

# OpenAI Codex project level ./.codex/skills
skilz install yamadashy_repomix/-claude__skills__lint-fixer --agent opencode --project


# Gemini CLI (project level) -- only works with project level
skilz install yamadashy_repomix/-claude__skills__lint-fixer --agent gemini

```

See this site [skill Listing](https://skillzwave.ai/skill/yamadashy__repomix__-claude__skills__lint-fixer__SKILL/) 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](https://skillzwave.ai/platforms/) or see the [skilz-cli GitHub repository](https://github.com/SpillwaveSolutions/skilz-cli)


<a href="https://skillzwave.ai/">Largest Agentic Marketplace for AI Agent Skills</a> and
<a href="https://spillwave.com/">SpillWave: Leaders in AI Agent Development.</a>

```

---

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

Pillar	Score	Max
Spec Compliance	11	15
Progressive Disclosure	23	30
Ease of Use	20	25
Writing Style	8	10
Utility	14	20
Modifiers	+1	±15

Pillar	Score	Max
Progressive Disclosure Architecture	23	30
Ease of Use	20	25
Spec Compliance	11	15
Writing Style	8	10
Utility	14	20
Modifiers	+1	±15

Criterion	Score	Max	Assessment
Token Economy	8	10	Concise content with minimal fluff; each section serves a purpose though some bullets could be tighter
Layered Structure	7	10	Self-contained skill with no reference files; appropriate for scope but missed opportunity to offload config details
Reference Depth	4	5	No references needed given simplicity; config files mentioned but not elaborated in separate docs
Navigation Signals	4	5	Clear section headers; file under 100 lines so no TOC needed; structure is navigable

Criterion	Score	Max	Assessment
Metadata Quality	8	10	Name follows conventions; description includes trigger terms but could be more specific about when to invoke
Discoverability	5	6	Good trigger terms (lint, fix, code changes, style guidelines); activates appropriately for linting tasks
Terminology Consistency	4	4	Consistent terminology throughout; tools named clearly and used consistently
Workflow Clarity	3	5	Numbered workflow steps present but lacks checklist format; no explicit validation gates

Criterion	Score	Max	Assessment
Frontmatter Validity	4	5	Valid YAML but minor formatting issues
Name Conventions	4	4	Correct hyphen-case format
Description Quality	3	4	Only 1-2 trigger phrases
Optional Fields	0	2	No optional fields used (no penalty)

Criterion	Score	Max	Assessment
Voice And Tense	3	4	Mostly imperative/infinitive form; occasional descriptive statements; no second-person
Objectivity	3	3	No marketing language; purely instructional and factual
Conciseness	2	3	Good density but some lines like 'Fix linting issues while preserving code functionality' are generic

Criterion	Score	Max	Assessment
Problem Solving Power	5	8	Addresses common linting workflow but lacks troubleshooting guidance for complex scenarios
Degrees Of Freedom	4	5	Appropriate constraints for task; clear tool sequence but allows judgment on manual fixes
Feedback Loops	3	4	Run→verify→test pattern present; lacks explicit success/failure criteria
Examples And Templates	2	3	No input/output examples; config file locations noted but no sample output or error patterns

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

Uh oh!

Skill Grading Report: lint-fixer - Score 77/100 (C) #1032

Description

📝 Skill Grading Report

Quick Summary

Pillar Scores

Issues Found: 4

📊 Full Grading Report

Skill Evaluation Report: lint-fixer

Overall Score: 77/100

Executive Summary

Detailed Scores

Progressive Disclosure Architecture (23/30)

Ease of Use (20/25)

Spec Compliance (11/15)

Writing Style (8/10)

Utility (14/20)

Modifiers Applied (+1)

Critical Issues (Top 4)

Issue 1: Missing Error Pattern Examples

Issue 2: Generic Opening Statement

Issue 3: Workflow Lacks Validation Checkpoints

Issue 4: Missing Troubleshooting Section

General Recommendations

Grade Scale

About This Report

JSON Output

📦 Recommended: Add Universal Installer Instructions

Git URL Options

Claude Code

OpenCode

Gemini

OpenAI Codex

Install from Skillzwave Marketplace

Other Supported Agents

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions