identity

You can configure agent identity persistence by setting frontmatter-driven placeholders for DISPLAY_NAME, TEAM, and ONCHAIN_IDENTITY. This ensures every action is anchored to a consistent profile across conversations and external services.

An on-chain identity is a verifiable domain identity exposed to external services via the ONCHAIN_IDENTITY placeholder. You need it when agents must interact with workflows or systems requiring cryptographic verification of their on-chain affiliation.

To configure agent identity context, set the DISPLAY_NAME, TEAM, and ONCHAIN_IDENTITY values in the frontmatter. The identity context loads at activation, allowing each agent in a team to reveal its identity consistently in chats and logs.

Yes, you can use ENS names for your agent's on-chain identity integration. The Skill exposes the ONCHAIN_IDENTITY placeholder to external services, allowing verifiable ENS domain identities to be referenced securely in on-chain workflows.

Dynamic placeholders work by substituting configured frontmatter values into agent responses at runtime. When referenced, the agent uses the TEAM placeholder to present its team affiliation, ensuring coherent identity across conversations.

No, agent identity configuration does not require manual updates for every new conversation. Once frontmatter-driven placeholders are set, the identity context loads automatically at activation, eliminating confusion about who is speaking across contexts.