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

import-plugins

/import-plugins

Przenosi pluginy zainstalowane w Claude Code lub Codex do Kiro albo importuje plugin prosto z adresu GitHub marketplace.

Licencja
MIT
Ostatnia zmiana repozytorium
22.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
3
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

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

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/kiro-port.py

Co robi i kiedy

Przenosi pluginy zainstalowane w Claude Code lub Codex do Kiro albo importuje plugin prosto z adresu GitHub marketplace.

Oryginalny opis (EN)

Bring plugins the user already installed in Claude Code or Codex into Kiro, or import one straight from a marketplace GitHub URL. Use when the user mentions Claude Code plugins, Codex plugins, a plugin marketplace, or asks to bring, move, port or migrate their plugins to Kiro. Not for authoring a new plugin from loose files.

Jak działa

  1. 1. See what there is
  2. 2. Port
  3. 3. Report back, then offer keywords
  4. 4. Removing
  5. What the script guarantees
Sekcje z nagłówków SKILL.md, w oryginale · 103 linii, 739 słów
Podgląd SKILL.md
---
name: import-plugins
description: Bring plugins the user already installed in Claude Code or Codex into Kiro, or import one straight from a marketplace GitHub URL. Use when the user mentions Claude Code plugins, Codex plugins, a plugin marketplace, or asks to bring, move, port or migrate their plugins to Kiro. Not for authoring a new plugin from loose files.
---

# Import Claude Code / Codex plugins into Kiro

A script does the conversion. You run it, read its report back to the user, and help with the one
decision it refuses to make: activation keywords. **Never edit plugin contents yourself** — the
script copies bodies byte-for-byte and stops if one differs, and that guarantee is the point of this
skill.

The script is at a fixed path. Set it once:

```bash
S=~/.kiro/powers/installed/plugin-importer/skills/import-plugins/scripts/kiro-port.py
```

If that path is missing, `ls ~/.kiro/powers/installed/*/skills/import-plugins/scripts/` to find it.
Never glob the home directory — it takes minutes and finds nothing useful.

## 1. See what there is

```bash
python3 $S scan                      # what Claude Code and Codex have installed
python3 $S scan --from <source>      # a marketplace or plugin repo: URL, owner/repo, or local path
```

`scan` prints each plugin's components and where it recommends putting them. Show that list grouped
by tool. Project-scoped Claude Code installs appear only when Kiro runs inside that project, matching
Claude Code's own visibility.

With `--from`, entries whose source points at another git repository print as `remote: <url>`. `port`
fetches only the ones you name, so always pass explicit names unless the marketplace is small.

**Ask which ones rather than defaulting to everything.** Each Power the user does not need is context
they pay for every session, and plugins carrying `node_modules` can exhaust the editor's file
descriptors — the script excludes those trees and warns past 2,000 files.

## 2. Port

```bash
python3 $S port <name>[@<market>] ...          # or --all
python3 $S port --from <source> <name>...
```

Follow the recommendation from `scan` unless the user wants otherwise:

| Plugin holds | Goes to |
|---|---|
| `commands/` or `.mcp.json` | a Power — only a Power can carry those |
| skills (hooks and agents may come along) | `~/.kiro/skills/`, plus `~/.kiro/hooks/` and `~/.kiro/agents/` |
| hooks or agents but no skills | a Power |
| Markdown guidance only | nothing is moved; report the `~/.kiro/steering/` path and stop |

`--as skills` and `--as power` override it. `--as skills` on a plugin with commands or MCP drops
those, and the script says so. `--slash` also exposes a Power's skills as `/name` slash commands
(symlinks under `~/.kiro/skills/`) — use it when the user wants to pick one skill out of a bundle
the way they did with `/command` in Claude Code, or asks for slash commands. `--project-local` writes into the current project's `.kiro/` instead of
installing globally. `--out DIR` only generates, which is how you turn a marketplace into a
Kiro-installable monorepo. `--smoke` checks that Kiro loads the result.

## 3. Report back, then offer keywords

For each plugin:

1. Say what came over and what the report marked `❌` or `⚠️`. **Do not soften the losses.** See
   `references/kiro-mapping.md` for what each one means.
2. `keywords` were derived from names only. Read the plugin's description and its skills'
   `description` lines, then append to the report:

   ```
   ## Suggested keywords
   Phrases the user would actually type when this Power should activate. Add them to
   plugin.json's keywords to apply.
   - commit       — requests like "commit this", "commit my changes"
   - open a PR    — …
   ```

   Three to six phrases in the user's language (Korean, English, or whatever they use), each with
   the situation it covers. **Recommend only** —
   do not write them into `plugin.json` unless asked.
3. Tell them to start a new session. Powers and skills load at session start.
4. If the plugin went into a Power (skills stayed inside it, not `~/.kiro/skills/`), mention that its
   skills resolve by plain-language request in a `kiro-cli --v3` session (a native `Kiro Powers` tool
   reads them by name) — but only there. In classic mode or `--no-interactive`, that tool isn't
   available and asking by name won't reliably find it; giving the skill's exact path
   (`~/.kiro/powers/installed/<plugin>/skills/<skill>/SKILL.md`) is the fallback that works everywhere.

## 4. Removing

```bash
python3 $S unport <name>
```

Removes everything the import installed — Power, skills, hooks, agents, supporting files — and leaves
the original plugin untouched.

## What the script guarantees

- Skill, command and agent bodies and hook scripts are copied byte-for-byte, asserted after the copy.
- The only body edit is `${CLAUDE_PLUGIN_ROOT}` → the installed path.
- `.claude-plugin/`, `commands/`, `agents/` stay in place, so the same directory still works as a
  Claude Code plugin.
- Anything Kiro has no equivalent for is reported, never approximated.
- Powers it did not create are never overwritten.
Pliki w paczce (3)
  • SKILL.md 5 KB
  • references/kiro-mapping.md 10 KB
  • scripts/kiro-port.py 57 KB

Wersje

W bazie nie ma innych skilli o nazwie import-plugins.

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

  • 90Codex CLI Plugins
    Tworzy wtyczki Codex CLI: manifest, pakowanie skilli, marketplace i lokalną instalację.
  • 100claude-plugins
    Opisuje, jak budować i rozpowszechniać wtyczki Claude Code: plugin.json, marketplace.json, polecenia, agenci, skille i hooki.
  • 100plugin-marketplace-creator
    Tworzy i konfiguruje marketplace'y wtyczek Claude Code hostowane na GitHubie: nowe repozytorium, dodawanie wtyczek, ustawienia dystrybucji dla zespołu i rozwiązywanie problemów.
  • 100migrate-agent-settings
    Przenosi serwery MCP, skille, komendy, subagentów i pliki instrukcji z innych agentów do jednej wtyczki Antigravity.
  • 90Claude Code Plugin Builder
    Tworzy pluginy Claude Code z manifestem, strukturą katalogów i komponentami: komendami, agentami, skillami, hookami i MCP.
  • 100codex-plugin-discovery
    Pomaga znaleźć wtyczki Codex: sprawdza dostępne wtyczki, poleca je do zadania i przeszukuje marketplace pod kątem instalowalnych rozszerzeń.

Uwagi i zgłoszenia

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