skill listing polisher
- Repo stars 1,996
- Author repo openclaw-master-skills
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 92 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @LeoYeAI · v0.1.0 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Skill Listing Polisher
Use this skill before publishing or updating a public ClawHub skill.
## What to improve
- title clarity
- description length and truncation risk
- tags that match the actual use case
- changelog that says what changed in plain language
- public package surface that looks normal in review
## Review order
1. shorten the public description if it gets cut off
2. remove internal-only scripts and private identifiers
3. tighten tags to actual buyer intent
4. make the changelog specific and boring
5. check that the package only contains user-facing files
## Fast checks
Run the bundled script:
```bash
./scripts/check-listing.sh /path/to/skill
```
## Output style
When reviewing a skill, return:
1. what weakens trust
2. what weakens discoverability
3. the smallest edit that improves both
Sections and files
Listed in source order.
sections -> What to improve → Review order → Fast checks → Output style
terms -> Use this skill before publishing or updating a public ClawHub skill. · 1. shorten the public description if it gets cut off 2. · 1. what weakens trust 2.
files/cmd -> ./scripts/check-listing.sh · path/to/skill
body sha256 -> e363dcf5c2d8
What to improve
title clarity description length and truncation risk tags that match the actual use case changelog that says what changed in plain language public package surface that looks normal in review
Review order
shorten the public description if it gets cut off remove internal-only scripts and private identifiers tighten tags to actual buyer intent make the changelog specific and boring check that the package only contains user-facing files
Fast checks
Run the bundled script:
Output style
When reviewing a skill, return: what weakens trust what weakens discoverability the smallest edit that improves both