install

Installs and refreshes Essential agent templates for Claude Code, Codex, and Grok Build.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill install-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install
Source: https://github.com/alvis/.agents/tree/main/plugins/essential/skills/install
Command: npx skills add https://github.com/alvis/.agents --skill install-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up the Essential marketplace's specialist agents across Claude Code, Codex, and Grok Build requires stitching split agent templates into harness-specific formats and, for Grok, attaching startup bootstrap instructions to user configuration. Doing this manually risks stale definitions, conflicting files, and broken bootstrap paths. ## Core Features & Use Cases - Harness-aware installation: Discovers agent templates from source checkouts or enabled same-marketplace plugins and stitches them into Claude Markdown, Codex TOML, or Grok Markdown definitions. - Conflict-safe refresh: Records owned paths and hashes under .essential/, stops before overwriting unowned or modified files, and rolls back failed operations. - Grok bootstrap attachment: Adds a managed, marked instruction block in Grok's AGENTS.md pointing at the absolute GROK.md bootstrap path, preserving other content. - Use Case: After enabling the Essential plugin in Grok Build, run this skill to install all agent definitions into ~/.grok/agents and wire up the startup guidance so a fresh session loads the agent team. ## Quick Start Ask the agent to install the Essential agent team for the current harness, for example: "Run the install skill to set up the Essential agents for Grok Build."

Frequently Asked Questions about install

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install Essential marketplace agents for Claude Code or Codex?

Run the skill's install script with --harness set to claude or codex. The installer discovers agent templates from source-checkout siblings or enabled same-marketplace plugins, stitches them into Markdown or TOML, and writes them to the default agent directory.

How do I set up Grok Build agent definitions and startup instructions?

Run the installer with --harness grok. It resolves enabled plugins via grok inspect --json, installs Markdown agent definitions under GROK_HOME, and attaches a managed bootstrap block in the user AGENTS.md pointing at the absolute GROK.md path.

Does the installer work with OpenCode?

No. In OpenCode the V1 projector owns installation, so the skill reports that and does not run the native installers or modify Grok configuration. Native installation is supported only for Claude Code, Codex, and Grok Build.

What happens when the installer finds conflicting existing agent files?

Installation stops before changing anything when it finds unowned content that differs from generated bytes, modified owned files, or conflicting attachment ownership. You must resolve the reported conflict manually; byte-identical files may be adopted.

How do I verify the agent installation succeeded?

Require a successful installer exit, inspect the reported destination and installed count, and check one emitted agent definition. For Grok, confirm the managed AGENTS.md block exists and that grok inspect --json lists it among project instructions in a fresh session.

How do I remove installed Essential agents?

Use the essential:uninstall skill, which removes this installation's unmodified managed files and the Grok attachment. Never delete the entire agents directory, since it may contain files owned by other tools or your own edits.