skill-porting-and-adaptationlisted

# Skill Porting and Adaptation Use this when a user asks whether a skill from an external repo can be installed into Hermes, whether it can be installed standalone, or how to adapt skills written for Claude Code, Codex, Gemini, Copilot, OpenCode, Pi, or another harness. ## Core workflow 1. **Inspect the external skill directory, not only `SKILL.md`.** - Identify whether the target has only a `SKILL.md` or also `references/`, scripts, templates, prompt files, assets, hooks, or platform plugin metadata. - For GitHub repos, clone or fetch the relevant tree and list files under the target skill directory. 2. **Read the target `SKILL.md` and classify references.** Look for: - Other skill invocations (`/grilling`, `writing-plans`, `domain-modeling`, etc.). - Repo-relative file paths (`skills/foo/bar.md`, `scripts/start-server.sh`). - Platform-specific tools or fields (`disable-model-invocation`, Claude Code hooks, `AskUserQuestion`, plugin manifests). - Terminal states or mandatory handoffs to another skill. 3. **Decide standalone viability.** Use this rubric: - **Standalone OK:** main `SKILL.md` contains the full workflow and has no hard dependencies, or optional dependencies are clearly marked “if available”. - **Standalone but degraded:** core text works, but support files/scripts are missing if installed by raw `SKILL.md` URL. - **Not standalone:** the target is a thin wrapper or alias that only invokes another skill; install the core skill