brycewang-stanford/Auto-Empirical-Research-Skills / skills/33-Galaxy-Dawn-claude-scholar/skills/skill-improver
skill-improver
VerifiedThis skill should be used when the user asks to "apply skill improvements", "update skill from plan", "execute improvement plan", "fix skill issues", "implement skill recommendations", or mentions applying improvements from quality review reports. Reads improvement-plan-{name}.md files generated by skill-quality-reviewer and intelligently merges and executes the suggested changes to improve Claude Skills quality.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.9 KB |
| examples/improvement-plan-example.md | markdown | 2.0 KB |
| examples/update-report-example.md | markdown | 1.2 KB |
| references/error-handling.md | markdown | 812 B |
| references/merge-strategies.md | markdown | 14.1 KB |
| references/plan-format.md | markdown | 10.6 KB |
| references/supported-updates.md | markdown | 791 B |
| scripts/backup-skill.shexecutable | script | 1.4 KB |
| scripts/verify-update.shexecutable | script | 6.9 KB |
references/supported-updates.md
View on GitHub# Supported Update Types
## YAML Frontmatter Updates
Update name or description:
```yaml
# Current
---
name: my-skill
description: A helpful skill for various tasks.
---
# Suggested
---
name: api-contract-manager
description: This skill should be used when the user asks to "validate API contract", "check API compatibility", or "detect breaking changes"
---
```
## SKILL.md Content Updates
Fix writing style (imperative form):
```
# Current
You should create the file first.
You need to validate the input.
# Suggested
Create the file first.
Validate the input.
```
## References/ File Updates
Add new section:
```markdown
## New Section
Content to be added...
```
## New File Creation
Create new example file:
```markdown
# examples/demo.md
Complete example content...
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |