agentic-identity

Manage developer identity for session telemetry attribution across global and project scopes.

12|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill agentic-identity-space-dinosaurs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-identity
Source: https://github.com/Space-Dinosaurs/DinoStack/tree/main/.openclaw/skills/agentic-identity
Command: npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill agentic-identity-space-dinosaurs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the developer identity used for session telemetry attribution across global and project scopes, enabling consistent attribution and easy switching between handles.

Core Features & Use Cases

  • Manual identity: set a persistent handle at global or per-project scope.
  • Automatic provisional identity: derive a provisional handle from GitHub and buffer telemetry until confirmation.
  • Project-scoped identities: override the global handle within a git repository; per-developer identities are kept separate and not stored in the repo.
  • Identity lifecycle: confirm provisional identities to flush buffered sessions to both per-project and global logs.

Quick Start

Run agentic-identity init <handle> to set your identity.

Frequently Asked Questions about agentic-identity

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

FAQPage Schema
How do I set developer identity for session telemetry attribution?

Set developer identity for telemetry attribution by running `agentic-identity init <handle>`. This configures your persistent handle for consistent session logging across global and per-project scopes.

Can I override my global telemetry handle for a specific git repository?

Yes, you can override your global telemetry handle with a project-scoped identity within a git repository. Per-developer identities are kept separate and are not stored in the repository itself.

How does automatic identity derivation from GitHub work for telemetry logs?

Automatic identity derivation from GitHub creates a provisional handle and buffers telemetry until confirmation. Running the confirm command flushes these buffered sessions to both per-project and global logs.

Do I need Python or any dependencies to manage per-project telemetry configuration?

You need Python 3 standard library to run the identity management script, with optional `pyyaml` for configuration parsing. There are no other external dependencies required for telemetry setup.

What happens to session logs when my provisional GitHub identity is unconfirmed?

When your GitHub-derived provisional identity is unconfirmed, session logs are securely buffered. They are held until you explicitly confirm your identity, which then flushes the telemetry to global and per-project logs.