hedera-agent-kit-v4-migrationlisted

# Migrating Hedera Agent Kit v3 → v4 This skill drives a complete v3 → v4 migration. v4 is the current major; v3 (`hedera-agent-kit@3.x`) no longer receives updates. Use this skill whenever you see code importing from `hedera-agent-kit` (unscoped) or `@hashgraph/sdk`. ## Quick triage — what kind of v3 code is this? Before editing anything, classify the file you are migrating. The migration steps differ. | If the file… | It's a… | Apply | |---|---|---| | Defines a `Plugin` and exports tool factories that return object literals with an `execute` function | **Custom plugin** | Plugin migration + BaseTool migration | | Calls `new HederaLangchainToolkit / HederaAIToolkit / HederaElizaOSToolkit / HederaMCPToolkit` | **Toolkit consumer** | Toolkit migration | | Imports plugins like `coreTokenPlugin`, `coreAccountPlugin`, `coreHTSPlugin` | **Toolkit consumer** (uses built-in plugins) | Toolkit migration + alias rename | | Imports `ResponseParserService` or `HederaMCPServer` from `hedera-agent-kit` | **Toolkit consumer** | Toolkit migration (these moved to toolkit packages) | | Both | Run **toolkit migration first**, then **plugin migration** for each tool | ## Migration workflow ### Step 1 — find every v3 entry point Run these searches at the project root before editing anything. They give you the migration surface in one shot: ```bash # Old package name in source and dependency manifests grep -rn "from ['\"]hedera-agent-kit" . grep -n '"hedera-agent-kit"' package.json # Old