skill-listing-polisher_skill

Overview

This skill improves a skill's public listing before publishing or updating it on ClawHub. It tightens the title, shortens descriptions to avoid truncation, aligns tags with buyer intent, sanitizes changelogs, and removes non-user files so listings appear clearer and less suspicious. Use it as a final pass to increase trust and discoverability.

How this skill works

The skill inspects the package and public metadata for common issues: overly long or ambiguous titles, descriptions that will be truncated, irrelevant or internal tags, verbose or vague changelogs, and presence of internal scripts or private identifiers. It suggests minimal edits that improve both trust and searchability, and flags files that should not be published. A bundled check script runs a quick set of heuristics against the skill directory to prioritize fixes.

When to use it

• Before publishing a new skill listing on ClawHub or similar marketplaces
• When updating a skill version to ensure metadata changes are clear and safe
• If reviewers flagged the listing as suspicious or unclear
• Prior to running marketing or paid promotion to maximize discoverability
• When packaging a backup or archive intended for public consumption

Best practices

• Keep titles concise and descriptive — include primary function and one context word
• Limit the public description to the first 120–160 characters for safe display
• Use 4–6 focused tags that reflect buyer intent, not internal concepts
• Write changelog entries in plain language: what changed and why, one line per item
• Remove or exclude internal scripts, API keys, and CI artifacts from the package

Example use cases

• Shortening a verbose title like ‘MySkill v2.0 - Experimental Beta’ to ‘MySkill: automated invoice parsing’
• Replacing long marketing copy with a 140-character summary plus a clear features list
• Converting vague tags (tools, dev) to intent-driven tags (invoice-parsing, ocr, automation)
• Editing changelog entries from ‘misc fixes’ to ‘fixed CSV import bug causing date parse errors’
• Removing .env, internal scripts, and test artifacts from the published package