skills: add adapt-yourself skill

[enyst]

Adds a new skill (adapt-yourself) that teaches agents/users how to make persistent behavior changes by choosing the right extensibility mechanism:

• repo/user skills (.agents/skills)
• always-on repo instructions (AGENTS.md)
• hooks (.openhands/hooks.json)
• plugins (Claude Code-compatible structure)
• MCP servers (CLI: ~/.openhands/mcp.json; SDK skills/plugins: per-skill .mcp.json)
• and, when necessary, code changes in OpenHands-CLI vs software-agent-sdk.

Also includes references covering uv + uv tool install workflows and version pinning, plus templates.

Changes:

• skills/adapt-yourself/ (SKILL.md, README, references)
• Register in .plugin/marketplace.json

Validation:

• python -m json.tool .plugin/marketplace.json

[all-hands-bot]

🟡 Acceptable - Solves a real problem (agents being asked to "modify yourself"), but SKILL.md is too dense for progressive disclosure. Main issue: section 3 turns into a uv technical manual when it should stay a decision guide.

[enyst]

Addressed the review feedback:

• Trimmed SKILL.md section 3 to stay high-level and moved details to references/INSTALLATION_MODES.md.
• Clarified MCP config locations: CLI uses ~/.openhands/mcp.json (or $OPENHANDS_PERSISTENCE_DIR/mcp.json); SDK skills/plugins use per-skill/per-plugin .mcp.json.
• Updated hooks template to parse structured JSON with jq and return {decision: allow|deny}.
• Reworded the opening clarification guidance to avoid unnecessary “one at a time” ceremony.

Pushed in 52633f7.

[enyst]

Rename update:

• Skill renamed from "modify-openhands" to "adapt-yourself".
• Updated: directory name, SKILL.md frontmatter name, and .plugin/marketplace.json entry.
• PR title/body updated to match.

[all-hands-bot]

🟡 Acceptable - Solves a real problem and the structure is sound after previous revisions. Main issue: one overly-generic trigger that will cause false positives.

[all-hands-bot]

🟠 Important: The trigger "uv tool install" is too generic and will cause false positives. This skill is about self-modification/customization, but this trigger would fire whenever someone mentions uv tool install for any purpose (e.g., "How do I uv tool install ruff?" or "Install pytest with uv").

Why this matters: Trigger pollution degrades the progressive disclosure model. The skill will get loaded unnecessarily, adding context bloat to unrelated conversations.

Fix: Remove the "uv tool install" line from the triggers list. The other triggers ("modify yourself", "customize openhands", "self-modify", etc.) are specific enough to catch actual self-modification requests without false positives.

If you genuinely need to catch uv-related self-modification, rely on the combination of existing triggers + the natural context of the conversation, not a generic command string.

[enyst]

Pulled your latest tweaks (git pull --rebase) and applied the requested cleanup:

• Removed the legacy .openhands/skills/... path from the “Where to put it” list and renumbered (now only .agents/skills and ~/.agents/skills).
• Removed legacy .openhands/skills / ~/.openhands/skills mentions from the architecture reference.

Pushed in 3c3536c.

[enyst]

Updated section “Add tools via MCP” to be more restrictive:

• Only recommend MCP when the user explicitly asks to add an MCP server, or when we can point to an existing MCP server for the capability (from docs/official repo).
• If no MCP server exists, it now directs toward writing a skill (workflow) or treating “build/install an MCP server” as the real work item.

Pushed in 5063dcb.

[enyst]

Pulled latest (git pull --rebase) and fixed the verification checklist wording:

• Made it clear the agent should ask the user to restart / start a fresh conversation, not try to restart itself.
• Clarified that /skills is a user command in the OpenHands CLI TUI.
• Clarified that the user sends the test prompt.

Pushed in 682ba1e.

[enyst]

Did a git pull --rebase and replaced “product(s)” → “project(s)” in the adapt-yourself skill wording.

Changes:

• MCP section: “project’s docs”, “project-specific”
• Architecture reference: “depending on project / SDK config”, “host project”

Pushed in 4e5e8ca.