# Register and Verify Starknet Agents

Teams need a consistent way to register agents and assess their on-chain trust signals. This skill provides ERC-8004 workflows for identity, feedback, and validation on Starknet.

## Install

```bash
npx skillstore add internet-court/starknet-identity
```

## Metadata

- Status: approved
- Slug: internet-court-starknet-identity
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r2
- Version status: not\_bumped
- Tree hash: a03fef1b813abc4c7e96de46586d0e462f6f4d0e41ca6b8d53f4731d5ae35b11
- Author: internet-court
- GitHub username: internet-court
- License: Apache-2.0
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/starknet/starknet-identity
- Ref: 1c2ebded2116f8124f45dba86a2e567f56e64d8e
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/internet-court-starknet-identity
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-starknet-identity/manifest

## Capabilities

- Explain the ERC-8004 identity, reputation, and validation registries.
- Show TypeScript patterns for registering agents with metadata.
- Show how to query ownership, metadata, reputation, and validation status.
- Describe signed feedback authorization with expiry and chain identifiers.
- Connect on-chain identity data with an A2A Agent Card.
- Map common registration, authorization, validation, and signature errors to recovery steps.

## Use Cases

- Register an Agent: Create an ERC-8004 identity, attach metadata, and interpret the registration transaction.
- Review Trust Signals: Query ownership, feedback summaries, client addresses, and validation results before integrating an agent.
- Publish Agent Discovery Data: Align an A2A Agent Card with the agent registry and document recovery paths for operational errors.

## Prompt Templates

### Explain ERC-8004

```
Explain the identity, reputation, and validation registries in ERC-8004 using a simple Starknet example.
```

### Plan Registration

```
Create a checklist for registering my Starknet agent, including metadata, registry addresses, fees, ownership, and transaction verification.
```

### Design Feedback Authorization

```
Review this feedback flow and identify authorization, expiry, chain ID, signer, replay, and self-feedback checks that must be tested: [paste flow].
```

### Audit Agent Trust Data

```
Analyze this ERC-8004 and A2A integration design. Identify inconsistent identity data, unsafe signer handling, stale reputation assumptions, and validation lifecycle gaps: [paste design].
```

## Limitations

- It does not deploy or verify Starknet contracts.
- It does not provide wallet custody, key management, or transaction execution by itself.
- Registry addresses, ABIs, chain settings, and SDK behavior require project-specific verification.
- On-chain reputation and validation data can be incomplete, stale, or transferred with the agent NFT.

## Best Practices

- Verify registry addresses, chain IDs, ownership, and transaction receipts before trusting results.
- Keep private keys outside source files and logs; use a wallet or external signer for funded accounts.
- Treat feedback and validation as scoped, time-sensitive claims that require independent verification.

## Anti Patterns

- Hardcode private keys, funded accounts, or production signer credentials in examples.
- Treat an agent NFT, reputation score, or validation count as proof of current behavior.
- Reuse expired or stale authorization data after ownership, chain, or registry state changes.

## Security Audit

- Audited at: 2026-08-07T09:01:35.011\+00:00
- Summary: The static findings are predominantly false positives caused by Markdown code fences, documentation URLs, examples, and standard configuration syntax. The private-key signer example is a confirmed high-impact secret-handling risk, so publication requires author remediation.

## Stats

- Views: 0
- Downloads: 6
- Favorites: 1
- Popularity score: 0