fish-shell-config

I took a look at your fish-shell-config skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 58/100, solidly in F territory. This is based on Anthropic's best practices for skill development. Your Ease of Use is strong (21/25) with great keyword coverage and clear structure, but Spec Compliance is completely failing (0/15) because of frontmatter issues. The good news? These are fixable problems that could push you well into passing range.

What's Working Well

• Keyword discovery is solid - Your description nails it with "fish, config, alias, abbr, function, prompt" - that's exactly what helps people find your skill
• Practical, example-heavy - You've got abundant code snippets and function templates that actually show people how to do things, not just talk about them
• Well-organized sections - Core Principles, Configuration, Functions, Abbreviations... the logical flow is there and makes sense
• Real problem-solving - You're addressing an actual gap for Fish shell users with comprehensive coverage

The Big One: Fix Your Frontmatter (Priority #1)

Your SKILL.md frontmatter is truncated/invalid. The description cuts off mid-word ("description: Expert Fish shell configuration...crea"). This breaks everything from an automated perspective and tanks your spec compliance score by 15 points.

Fix: Complete your frontmatter properly:

---
name: fish-shell-config
description: Configure Fish shell environments including config files, functions, abbreviations, and prompts. Use when asked to "setup Fish shell", "Fish configuration help", or "configure Fish shell functions".
---

This alone gets you +5 points on frontmatter validity and +4 on description quality. You'll probably hit 68-70/100 just from this.

Other Things Worth Fixing

1. Create a references directory - Your SKILL.md is 500+ lines. Extract the "Migrating from Bash" section to references/bash-migration.md and the detailed examples to references/examples.md. This respects Progressive Disclosure Architecture and saves ~150 tokens. Impact: +8 points

2. Add a Table of Contents - Files over 100 lines need navigation. Add a simple TOC after your frontmatter pointing to each major section. Takes 30 seconds, improves navigation. Impact: +3 points

3. Tighten the workflow section - Your "Output Instructions" at the end are a bit loose. Add explicit numbered steps and verification checklists for each output type. Impact: +2 points

Quick Wins

Most impactful first:

• Fix frontmatter immediately - straightforward, worth 9 points
• Split into references directory - 500 lines → 250 + refs (8 points)
• Add TOC after frontmatter - 5 minutes (3 points)
• Tighten workflow steps - make them more checklist-oriented (2 points)

You've built something genuinely useful here. These fixes are all structural/presentational - your content is already strong. Getting to 80+ is totally doable.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.