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

dev10x:skill-prune

/dev10x:skill-prune

Wyłącza nieistotne umiejętności w projekcie, by lista nie zajmowała kontekstu i nie wybierała złych umiejętności po instalacji wtyczek.

Repozytorium
dev10x-claude ↗
Licencja
MIT
Ostatnia zmiana repozytorium
08.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format15 / 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 08.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Wyłącza nieistotne umiejętności w projekcie, by lista nie zajmowała kontekstu i nie wybierała złych umiejętności po instalacji wtyczek.

Oryginalny opis (EN)

Use when a project inherits dozens of skills it will never use after installing several plugins — so the skill listing stops spending context on frontend skills in a Django backend (or iOS setup in a web app) and skill matching stops picking the wrong one, without curating the list by hand every session. TRIGGER when: the user asks to prune, hide, or turn off irrelevant skills for this project, or after a new plugin install adds skills. DO NOT TRIGGER when: the user wants a plugin uninstalled everywhere (use /plugin), or wants a single setting changed (use update-config).

Jak działa

  1. Orchestration
  2. What Claude Code can and cannot hide
  3. Workflow
  4. Common Mistakes
Sekcje z nagłówków SKILL.md, w oryginale · 127 linii, 741 słów
Podgląd SKILL.md
---
name: dev10x:skill-prune
invocation-name: dev10x:skill-prune
description: >
  Use when a project inherits dozens of skills it will never use after
  installing several plugins — so the skill listing stops spending
  context on frontend skills in a Django backend (or iOS setup in a web
  app) and skill matching stops picking the wrong one, without curating
  the list by hand every session.
  TRIGGER when: the user asks to prune, hide, or turn off irrelevant
  skills for this project, or after a new plugin install adds skills.
  DO NOT TRIGGER when: the user wants a plugin uninstalled everywhere
  (use /plugin), or wants a single setting changed (use update-config).
user-invocable: true
allowed-tools:
  - Bash(uvx dev10x skill prune-overrides:*)
  - Bash(dev10x skill prune-overrides:*)
  - Read
  - Edit(~/.config/Dev10x/skill-prune.yaml)
  - Glob
  - AskUserQuestion
  - TaskCreate
  - TaskUpdate
---

# dev10x:skill-prune

**Announce:** "Using dev10x:skill-prune to hide the skills this project
will never use."

## Orchestration

This skill follows `references/task-orchestration.md` patterns.

**REQUIRED: Create a task at invocation.** Execute at startup:

1. `TaskCreate(subject="Prune irrelevant skills for this project", activeForm="Pruning skills")`

Mark completed after Step 5: `TaskUpdate(taskId, status="completed")`.

## What Claude Code can and cannot hide

| Skill kind | Listed as | How to hide it per project |
|------------|-----------|----------------------------|
| User or project skill | `deploy` | `skillOverrides: {"deploy": "off"}` |
| Plugin skill | `impeccable:audit` | **Not** by `skillOverrides` — only the whole plugin, via `enabledPlugins: {"impeccable@<marketplace>": false}` |

`skillOverrides` values: `off` (hidden everywhere), `user-invocable-only`
(only the user can call it), `name-only` (name listed, description
dropped), `on`. Claude Code documents that plugin skills ignore
`skillOverrides`, so the planner refuses plugin-skill names rather than
writing an entry that does nothing (GH-1627).

## Workflow

### Step 1: Read the project

Gather the stack cues — do not guess them from the directory name:

- `CLAUDE.md`, `README.md`
- `pyproject.toml`, `package.json`, `Cargo.toml`, `go.mod`, `Gemfile`,
  `*.xcodeproj` (Glob for them at the repo root)
- Frontend markers: `*.svelte`, `*.tsx`, `*.astro`; mobile markers:
  `ios/`, `android/`

Write a one-line stack summary: "Django + Celery backend, no frontend,
no mobile".

### Step 2: Read the current state

1. Current overrides: `Read(.claude/settings.local.json)` — note the
   existing `skillOverrides` and `enabledPlugins`.
2. Allowlist: `Read(~/.config/Dev10x/skill-prune.yaml)` — its `keep:`
   names are never proposed. A missing file means no allowlist.
3. Installed plugin ids (`name@marketplace`): the `enabledPlugins`
   keys in `~/.claude/settings.json` and the project settings files.

**Re-run:** when overrides already exist, show them first and limit
the proposal to skills not yet decided — newly installed ones.

### Step 3: Classify the visible skills

Take the skill list from this session's skill listing. For each skill,
compare its description to the stack summary:

- **Clearly irrelevant** — targets a stack the project does not have
  (Svelte skills in a Django backend, iOS Sentry setup in a web app).
- **Probably irrelevant** — plausible but unlikely here (a marketing
  deck skill in an infra repo).
- **Keep** — matches the stack, is workflow-generic (git, PR, tests),
  or is on the allowlist.

Group plugin skills by plugin. Propose disabling a plugin only when
**every** skill it ships is irrelevant; otherwise list it under
"plugin skills that cannot be hidden one by one" and keep it.

Build the dry run and show its output as the proposed diff:

```bash
uvx dev10x skill prune-overrides --set <name>=off ... --disable-plugin <plugin@market> ...
```

stdout is one JSON object: `skill_changes`, `plugin_disables`,
`unchanged`, `kept_by_allowlist`, `plugin_skills_refused`. A
non-empty `plugin_skills_refused` means a plugin skill was proposed by
name — move it to a plugin decision instead.

### Step 4: Confirm

**REQUIRED: Call `AskUserQuestion`** (do NOT use plain text). Show the
counts per category and the plugins to disable. Options:

- Hide clearly irrelevant (Recommended) — `off` for that category only
- Hide clearly and probably irrelevant — both categories
- User-invocable only — keep them callable by `/name`, out of Claude's
  automatic matching
- Review one by one — ask per skill, then apply the chosen set

**Allowlist offer.** When the user kept any name the classifier
proposed hiding, **REQUIRED: Call `AskUserQuestion`** once (do NOT use
plain text, `multiSelect: true`) listing those names. Options:

- Keep for this project only (Recommended) — nothing is persisted
- One option per kept name — add it to the `keep:` list in
  `~/.config/Dev10x/skill-prune.yaml` (via `Edit`) so no project is
  ever offered it again

**Scope.** The write target is project-local
`.claude/settings.local.json`. Writing user scope
(`~/.claude/settings.json`) or the checked-in `.claude/settings.json`
needs the user to ask for it explicitly — then pass `--settings <path>`.

### Step 5: Apply and report

Re-run the dry-run command with exactly the confirmed set plus
`--apply`. The command merges into existing `skillOverrides` and
`enabledPlugins` under a file lock and leaves every other key alone;
running it again reports `has_changes: false`.

Report what changed and say that it takes effect in the **next**
session.

## Common Mistakes

| Mistake | Consequence |
|---|---|
| Writing `impeccable:audit` into `skillOverrides` | Entry is ignored; the skill still loads and the user believes it is gone |
| Disabling a plugin because most of its skills are irrelevant | The one skill the project needed disappears with it |
| Writing to `~/.claude/settings.json` by default | Every other project loses those skills too |
| Hand-editing the settings JSON | Existing overrides are overwritten and re-runs are no longer idempotent |
Pliki w paczce (2)
  • SKILL.md 6 KB
  • evals/evals.json 4 KB

Wersje

W bazie nie ma innych skilli o nazwie dev10x:skill-prune.

Migawka bazy z 13.11.2026 · wersja paczki a2b5b50dc1bd (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

  • 100skills
    Zarządza skillami agenta przez CLI npx skills: instalacja, usuwanie, lista, aktualizacja i wyszukiwanie.
  • 100plugin-marketplace-setup
    Projektuje publiczne i prywatne marketplace'y skilli i wtyczek dla Cursor, Claude Code, Codex, Zed i npx skills: układ manifestów, macierz instalacji i publikacja na skills.sh.
  • 100skillscout
    Utrzymuje skille aktualne dla różnych rodzajów pracy, sprawdza zmiany w upstreamie i poleca nowe pakiety.
  • 100skill-profiles
    Włącza i wyłącza grupy skilli zależnie od rodzaju pracy, żeby lista skilli mieściła się w budżecie kontekstu, tylko w Claude Code.
  • 100vetskill
    Szuka skilla agenta pod konkretne zadanie i ocenia, czy skill z katalogu skills.sh jest bezpieczny do instalacji.
  • 100skills-creator
    Pomaga dodać nowy skill, agenta, komendę lub plugin i ocenić, czy zadaniu potrzebny jest raczej agent.

Uwagi i zgłoszenia

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