app-store-optimization

I noticed your skill focuses on the app marketplace challenge—that's a solid niche where a lot of developers struggle with visibility. At a 65/100, you're hitting the core value proposition, but there's some structural inefficiency we should dig into that might be limiting its reach and adoption.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 65/100, which puts you in the D grade territory. This is based on Anthropic's skill evaluation framework. Your strongest area is Spec Compliance (11/15)—the frontmatter is clean and the name conventions are right. But Progressive Disclosure Architecture is pulling you down hard at 12/30. That's your biggest opportunity for improvement.

What's Working Well

• Solid spec compliance — YAML frontmatter is valid, naming follows conventions, and you've got the required fields in place
• Covers real ASO gaps — Keyword research, metadata optimization, competitor analysis, and platform-specific requirements actually address what devs need
• Structured input format — Your JSON input schemas in the 137-186 line range provide clear, parseable structure for what the skill expects
• Navigation is logical — Headers are well-organized and readers can follow the flow from capabilities through to examples

The Big One: You've Got Everything in One File (Kill Your Darlings)

Your biggest issue? You're jamming 404 lines into a single SKILL.md. The scripts section (lines 226-307), best practices (lines 308-352), and platform specs (lines 56-68) should each live in separate reference files. Right now, every user loads everything regardless of what they need.

Here's the fix:

• Create references/scripts.md for your ASO analysis scripts and implementation details
• Create references/platform-requirements.md for iOS/Android specs
• Create references/best-practices.md for the optimization strategies
• Keep SKILL.md lean—just overview, triggers, and quick examples

This restructure alone could bump you +8 points by improving token efficiency and layered discoverability.

Other Things Worth Fixing

1. Add trigger phrases to your description — You mention "ASO" once but users search for "optimize app store listing" and "improve app rankings." Add these naturally to your frontmatter description. Easy +2 points.

2. Show actual output examples — You describe "before/after metadata comparison" but don't show one. Drop a real example: "Before: MyApp - Tasks | After: MyApp: AI Task Manager & To-Do List" with character counts and keyword density. That's +3 points of credibility right there.

3. Cut the redundant "How to Use" section — Lines 190-223 basically restate what users already know from Input Requirements and Capabilities. Either delete it or reduce to 2 genuinely novel examples. Saves tokens and +2 points.

4. Ditch marketing language — Phrases like "comprehensive," "successfully launching," and "complete ASO capabilities" read like a product pitch. Reframe as: "Provides ASO tools for researching keywords, optimizing metadata, and tracking performance." Clinical, clear, +2 points.

Quick Wins

• Split into references/ — Biggest bang for buck (+8 points)
• Add trigger terms — Users will find you easier (+2 points)
• One real before/after example — Proves the skill works (+3 points)
• Remove marketing fluff — Keep it technical (+2 points)

That's a potential +15 points without rewriting core logic. You're looking at ~80/100 if you nail these structural changes.

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.