Przejdź do treści
Biblioteka skilli
AI i agenci · Budowanie i kod

meta-skill-improve

/meta-skill-improve

Wdraża ulepszenia skilla według przygotowanego planu poprawek i aktualizuje jego treść.

Licencja
CC-BY-4.0
Ostatnia zmiana repozytorium
26.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

CC-BY-4.0, otwarta.

Co robi i kiedy

Wdraża ulepszenia skilla według przygotowanego planu poprawek i aktualizuje jego treść.

Oryginalny opis (EN)

Use when the user asks to ”apply skill improvements”, ”update skill from plan”, or ”execute improvement plan”.

Jak działa

  1. Core Workflow
  2. When to Use
  3. Step-by-Step Guide
  4. Priority Handling
  5. Integration with Skill Quality Reviewer
  6. Additional Resources
  7. Best Practices
  8. Usage Examples
Sekcje z nagłówków SKILL.md, w oryginale · 247 linii, 869 słów
Podgląd SKILL.md
---
name: meta-skill-improve
description: "Use when the user asks to ”apply skill improvements”, ”update skill from plan”, or ”execute improvement plan”."
version: 1.0.0
---

# Skill Improver

Execute improvement plans generated by `skill-quality-reviewer` to automatically update and fix issues in Agent 技能(Skills).

## Core Workflow

```
Read improvement-plan-{name}.md
    ↓
Parse improvement items (High/Medium/Low priority)
    ↓
Group changes by file
    ↓
Detect and resolve conflicts
    ↓
Backup original files
    ↓
Execute updates (Edit or Write tools)
    ↓
Verify results
    ↓
Generate update-report
```

## When to Use

**Trigger phrases:**
- "Apply improvements from improvement-plan-git-workflow.md"
- "Update my skill based on the quality report"
- "Execute the improvement plan for api-helper"
- "Fix the issues identified in quality review"

**Use this skill when:**
- Applying improvements from an improvement plan
- Updating a skill based on quality review feedback
- Executing recommended fixes from `skill-quality-reviewer`
- Implementing structured improvements to skill documentation

## Step-by-Step Guide

### Step 1: Load the Improvement Plan

Read the `improvement-plan-{skill-name}.md` file generated by `skill-quality-reviewer`.

```bash
# Plan is typically in current directory
ls improvement-plan-*.md

# Or specify full path
read /path/to/improvement-plan-my-skill.md
```

**Validate the plan:**
- File exists and is readable
- Contains priority sections (High/Medium/Low)
- Has structured improvement items
- Includes file paths and suggested changes

See `references/plan-format.md` for detailed plan structure.

### Step 2: Parse and Group Changes

Extract all improvement suggestions and organize by target file.

**Extract from each item:**
- File path (e.g., `SKILL.md:line:line` or `references/file.md`)
- Dimension (Description Quality, Content Organization, etc.)
- Impact (+X points)
- Current content
- Suggested content
- Reason for change

**Build update queue:**
```
by_file = {
  "SKILL.md": [change1, change2, ...],
  "references/guide.md": [change3, ...],
  "examples/demo.md": [change4, ...],
}
```

### Step 3: Detect and Resolve Conflicts

Check for conflicts when multiple changes affect the same content.

**Resolution strategy:**
1. High priority takes precedence over medium/low
2. If same priority, preserve first change
3. Flag conflicts for manual review
4. Document resolution in update report

See `references/merge-strategies.md` for detailed merge logic.

### Step 4: Sort by Priority

Order changes by priority within each file.

**Priority order:**
1. High Priority (execute first)
2. Medium Priority (execute second)
3. Low Priority (execute last)

### Step 5: Backup and Execute

**Backup location:** `_backup/{skill-name}-{timestamp}/` inside the repo (gitignored temp area; never write outside the checkout)

```bash
# Use backup script
skills/meta-skill-improve/scripts/backup-skill.sh <skill-path>(ACAT-GOVERNANCE:上游脚本未随本仓库集成,宿主安装路径已废弃;2026-09-23 宿主中性化改写,改用本仓技能目录内路径)
```

**Apply changes:**
- Use Edit tool for existing content
- Use Write tool for new files
- Verify each change was applied

### Step 6: Verify and Report

**Verification checks:**
1. YAML syntax valid
2. All modified files exist and are valid
3. New files were created successfully
4. No unintended changes occurred

```bash
# Use verify script
skills/meta-skill-improve/scripts/verify-update.sh <skill-path>(ACAT-GOVERNANCE:上游脚本未随本仓库集成,宿主安装路径已废弃;2026-09-23 宿主中性化改写,改用本仓技能目录内路径)
```

**Generate update-report-{skill-name}-{timestamp}.md** documenting:
- Summary (files modified, files created, total changes)
- Changes Applied (per-file breakdown)
- Quality Improvement (before/after scores)
- Verification Results
- Backup Location

See `examples/update-report-example.md` for report template.

## Priority Handling

### High Priority
Execute first. These typically address:
- Critical description issues
- Major writing style problems
- Missing structural elements
- Security-related concerns

### Medium Priority
Execute after High. These typically address:
- Content organization improvements
- Additional examples
- Documentation enhancements

### Low Priority
Execute last. These typically address:
- Minor clarifications
- Nice-to-have improvements
- Polish and refinement

## Integration with Skill Quality Reviewer

This skill works seamlessly with `skill-quality-reviewer`:

```
Current Skill (67/100 D+)
    ↓ [skill-quality-reviewer]
Improvement Plan
    ↓ [skill-improver]
Improved Skill (87/100 B+)
    ↓ [skill-quality-reviewer]
Quality Report (validation)
```

**Iterate until desired quality level reached.**

## Additional Resources

### Reference Files

- **`references/plan-format.md`** - Improvement plan file structure and format
- **`references/merge-strategies.md`** - Detailed merge algorithms and conflict resolution
- **`references/error-handling.md`** - Error handling strategies
- **`references/supported-updates.md`** - Supported update types with examples

### Example Files

- **`examples/improvement-plan-example.md`** - Sample improvement plan
- **`examples/update-report-example.md`** - Sample update report

### Scripts

- **`scripts/backup-skill.sh`** - Create backup of skill before updates
- **`scripts/verify-update.sh`** - Verify skill integrity after updates

## Best Practices

### Before Applying Updates

1. **Review the improvement plan** - Understand what will change
2. **Verify backup location** - Ensure backups can be restored
3. **Check for manual changes** - Note any uncommitted local modifications
4. **Estimate impact** - Review expected quality improvement

### During Update Execution

1. **Process in priority order** - High → Medium → Low
2. **Verify after each file** - Check updates were applied correctly
3. **Log all changes** - Document what was modified
4. **Handle conflicts gracefully** - Flag for review if needed

### After Applying Updates

1. **Review the update report** - Confirm all changes were intended
2. **Test the skill** - Verify it still works correctly
3. **Compare scores** - Check quality improvement matches expectations
4. **Keep backup** - Retain backup until confident in changes

## Usage Examples

**Example 1: Apply improvements to local skill**
```
User: "Apply improvements from improvement-plan-git-workflow.md"

[Claude executes the workflow:]
1. Reads improvement-plan-git-workflow.md
2. Parses all improvement items
3. Groups changes by file
4. Detects and resolves conflicts
5. Sorts by priority
6. Backs up git-workflow skill
7. Executes updates
8. Verifies results
9. Generates update-report-git-workflow-timestamp.md
```

**Example 2: Update skill from quality review**
```
User: "Update my api-helper skill based on quality report"

[Claude:]
1. Locates improvement-plan-api-helper.md
2. Applies all recommended changes
3. Verifies skill structure
4. Reports quality improvement: 72/100 → 91/100
```
Pliki w paczce (2)
  • ASSET-GAP.md 1 KB
  • SKILL.md 7 KB

Wersje

W bazie nie ma innych skilli o nazwie meta-skill-improve.

Migawka bazy z 13.11.2026 · wersja paczki 1f3b9bbfd6b6 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100meta-skill-review
    Ocenia jakość skilla, analizuje jego opis i treść oraz wskazuje, co warto poprawić.
  • 100skill-improver
    Wczytuje pliki planu poprawy wygenerowane przez recenzenta i scala zalecane zmiany w skillach Claude oraz je wykonuje.
  • 92apply-improvements
    Wdraża propozycje ulepszeń z pliku zapisanego przez retrospektywę potoku w plikach wtyczki.
  • 95plan-orchestrate
    Wykonuje plan równoległymi pracownikami TDD na żądanie, wymagając wcześniej przygotowanego planu z plan-create.
  • 100skill-builder
    Tworzy lub ulepsza skilla: dodaje, aktualizuje, pakuje i testuje SKILL.md, references i scripts, a powtarzalny workflow zamienia w skill.
  • 100evaluate-improve
    Proponuje ulepszenia treści SKILL.md, opisów i konfiguracji narzędzi na podstawie wyników ewaluacji, aby podnieść pass rate i poprawić wyzwalanie.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.