How do I install the Install skill?

Run npx skillmds@latest add cherwayway/install in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Install safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Install?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Install free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Install?

Cherwayway (@cherwayway) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Install by cherwayway — Agent Skill

Name: Install
Author: Cherwayway

File contents

Install Agent Context Patch

Use this skill only when the user explicitly asks to install Agent Context Patch. This marketplace plugin is a discovery and installation adapter; it is not the Agent Context Patch runtime and it must not silently edit the current workspace.

Stable source

Resolve the latest stable release from:

https://github.com/Cherwayway/agent-context-patch/releases/latest

Require a GitHub-enforced immutable Release that is neither a draft nor a prerelease. Resolve its exact tag and target commit. Download the published archive to a temporary directory and verify its GitHub-published SHA-256 asset checksum before unpacking it. Require the release tag, target commit, archive identity, and unpacked skills/evolve/manifest.json Kit Version to agree.

Never install the runtime from the moving main branch. If release metadata, immutability, the checksum, or any identity check is unavailable or inconsistent, stop and leave the workspace unchanged.

Reviewed installation

After verification, read AGENT_INSTALL.md from the unpacked Release and follow it as the canonical installation contract:

Detect the Agent, workspace root, instruction file, user-level skill target, existing context, and Node capability instead of guessing paths.
Run the candidate Release's Bootstrap in dry-run mode.
Show the complete deterministic plan, exact plan hash, and a separate minimal semantic patch for CLAUDE.md, AGENTS.md, or the matching instruction file.
Obtain explicit approval for both the unchanged plan and the semantic instruction patch before applying anything.
Recompute the plan at apply time, apply only the approved hash, apply the separately approved instruction patch, and run the Release verification seam.
Report installed Kit Version, workspace schema, policy, targets, verification result, and any preserved conflicts without exposing sensitive content.

The installation must preserve existing workspace context and instructions. Bootstrap never merges the instruction file by itself.

---name: installdescription: Safely install or inspect Agent Context Patch when the user asks for durable, reviewable workspace memory for Claude Code or Codex.---# Install Agent Context PatchUse this skill only when the user explicitly asks to install Agent ContextPatch. This marketplace plugin is a discovery and installation adapter; it isnot the Agent Context Patch runtime and it must not silently edit the currentworkspace.## Stable sourceResolve the latest stable release from:`https://github.com/Cherwayway/agent-context-patch/releases/latest`Require a GitHub-enforced immutable Release that is neither a draft nor aprerelease. Resolve its exact tag and target commit. Download the publishedarchive to a temporary directory and verify its GitHub-published SHA-256 assetchecksum before unpacking it. Require the release tag, target commit, archiveidentity, and unpacked `skills/evolve/manifest.json` Kit Version to agree.Never install the runtime from the moving `main` branch. If release metadata,immutability, the checksum, or any identity check is unavailable orinconsistent, stop and leave the workspace unchanged.## Reviewed installationAfter verification, read `AGENT_INSTALL.md` from the unpacked Release andfollow it as the canonical installation contract:1. Detect the Agent, workspace root, instruction file, user-level skill target, existing context, and Node capability instead of guessing paths.2. Run the candidate Release's Bootstrap in dry-run mode.3. Show the complete deterministic plan, exact plan hash, and a separate minimal semantic patch for `CLAUDE.md`, `AGENTS.md`, or the matching instruction file.4. Obtain explicit approval for both the unchanged plan and the semantic instruction patch before applying anything.5. Recompute the plan at apply time, apply only the approved hash, apply the separately approved instruction patch, and run the Release verification seam.6. Report installed Kit Version, workspace schema, policy, targets, verification result, and any preserved conflicts without exposing sensitive content.The installation must preserve existing workspace context and instructions.Bootstrap never merges the instruction file by itself.

Frequently asked questions

Install