impersonator-guide

Operate an Ava impersonation lease using the Ava CLI and Python SDK under a borrowed identity.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill impersonator-guide-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impersonator-guide
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/.agents/skills/impersonator-guide
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill impersonator-guide-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a trusted takeover grants you an active Ava impersonation lease, you need a complete operating manual for acting as the borrowed agent: handling pushed messages, acknowledging batches, renewing the lease correctly, and releasing control with a clean handoff summary. ## Core Features & Use Cases - Push-based message handling: Process delivered envelopes containing chat, reminder, cancel, and system_note messages, then ACK exactly the handled ids within the five-minute window. - Lease lifecycle management: Check status with ava impersonate status, renew only in response to expiry reminders, and release with a required concrete summary. - Python SDK under borrowed identity: Attach via ava.external.attach to call any ava.* capability as the impersonated agent, with staged plugin state flushed on exit. - Use Case: An external agent receives an activation push naming session id and agent id, processes inbound chat instructions, sends progress via ava impersonate say, renews once when the reminder arrives, and finishes with ava impersonate release --summary describing completed and open work. ## Quick Start Read the activation push for your session id and agent id, then run ava impersonate status with those values using the cluster checkout's ava executable to confirm the lease is active before processing pushed messages.

Frequently Asked Questions about impersonator-guide

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

FAQPage Schema
How do I act as an Ava agent under an impersonation lease?▼

Start from the activation push, which provides the session id, agent id, and handoff brief. Use the cluster checkout's ava CLI with AVA_IMPERSONATION_TOKEN set, verify the lease is active via ava impersonate status, then process pushed message envelopes and ACK handled ids.

How do I renew an Ava impersonation lease?▼

Renew only in response to a renewal reminder pushed about five minutes before expiry, using ava impersonate renew with a --ttl covering the remaining work. Never renew on a schedule, in a loop, or via a background process.

How do I use the Ava Python SDK under a borrowed identity?▼

Attach with ava.external.attach(session_id, agent_id=agent_id, token=os.environ["AVA_IMPERSONATION_TOKEN"]) from the cluster's interpreter. Inside the attachment, all ava.* calls resolve identity and plugins as the borrowed agent, and attachment.flush() stages state between steps.

What happens if the impersonation lease expires while I am working?▼

Stop immediately, since further CLI and SDK calls fail validation. Control returns to the Ava agent with unacknowledged messages and staged state preserved; do not request a new lease yourself or keep acting under the identity.

Why should I not acknowledge messages I have not handled?▼

Unacknowledged batches are re-delivered until ACKed or the lease ends, so ACKing only handled ids keeps delivery honest. If you cannot handle a message, leave it unacknowledged and note it in your release summary for the resumed agent.