impersonate

Files (1)

• SKILL.md

SKILL.md (first lines)

# ArchAstro Agent Embed

The current CLI command is `archastro embed`; `impersonate` is the legacy skill name and is not a CLI command.

Manage ArchAstro agent embedding through the ArchAstro CLI and keep the Claude Code session aligned with the active identity file.

This skill assumes the ArchAstro CLI is already installed and authenticated. Use the `/archastro:install` and `/archastro:auth` commands in this same plugin instead of trying to install or authenticate the CLI manually inside this skill.

## Always Start with State

Every invocation must begin by checking the current impersonation state. Do not ask the user what action to take — determine it from state and intent.

```
archastro embed status --json
```

Then route based on the combination of current state and user intent.

## Routing

### CLI not installed or too old

Before any impersonation work, verify the CLI:

- Read `plugin-compatibility.json` from the plugin root. Prefer `plugins.archastro.minimumCliVersion`, fall back to the top-level `minimumCliVersion`.
- Run `archastro --version`. If missing or older than the resolved minimum, direct the user to `/archastro:install`.
- If authentication or app selection is missing, direct the user to `/archastro:auth`.

### Inactive + user wants to start

```
archastro embed start <agent-id-or-lookup-key> --harness codex --install-scope project
```

Then:

```
archastro embed status --json
```

Read `state.identity_file` from the returned JSON (`active`, `path`, and `state`). Open and read that file. Adopt the identity for the current Claude Code session while retaining your normal capabilities.

`embed start` automatically installs linked skills for detected harnesses by default. Choose the actual current harness and intended scope explicitly (the example above uses Codex/project); supported harnesses are `claude`, `codex`, `cursor`, and `rovo`, with user scope the default. After adoption, inspect `state.skills`, `state.loaded_skills`, and returned warnings to report what installed successfully:

```
archastro embed list skills --json
```

### Active + user asks about status (or no specific intent)

Summarize the current state from the JSON already fetched:

- Agent name and ID
- App ID
- Tool count and skill count
- Loaded (installed) skills and their invocations
- Timestamps

If the identity file has not been read in this session yet, read it and adopt the identity.

### Active + user wants to sync/refresh

```
archastro embed sync
```

Then:

```
archastro embed status --json
```

Re-read `state.identity_file` and re-adopt the refreshed identity. Report what changed (new/removed tools or skills).

### Active + user wants to stop

```
archastro embed stop
```

Drop the impersonated identity from the current session. Confirm that local state was removed.

### Active + user asks about tools

List the impersonated agent's tools:

```
archastro embed list tools --json
```

To execute a tool directly:

```
archastro embed run tool <tool-name> --input '<json>' --json
```

### Active + user asks about skills

List available skills:

```
archastro embed list skills --json
```

Show what's available vs what's already installed (from `state.loaded_skills`).

To install a skill:

```
archastro embed install skill <skill-id-or-slug>
```

After install, report the invocation command (e.g., `/<skill-name>`) so the user knows how to use it.

For Codex:

```
archastro embed install skill <id> --harness codex --install-scope project
```

From ArchAstro/archastro, MIT.

More from ArchAstro/archastro