Skills starknet-identity

📦

starknet-identity

Name: starknet-identity
Author: internet-court

v1.0.0 Content revision r2 High Risk ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables

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.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "starknet-identity" from https://skillstore.io/skills/internet-court-starknet-identity.md and its manifest at https://skillstore.io/api/skills/internet-court-starknet-identity/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/internet-court-starknet-identity.md Signed manifest GET /api/skills/internet-court-starknet-identity/manifest Signed lockfile GET /api/skills/internet-court-starknet-identity/lockfile

Test it

Using "starknet-identity". What should I verify before registering an agent on Starknet?

Expected outcome:

Confirm the target registry address and ABI.
Use a funded account through secure wallet or signer infrastructure.
Validate metadata fields, token URI, chain ID, and transaction receipt.
Record the emitted agent ID and verify its owner.

Using "starknet-identity". Why was feedback authorization rejected?

Expected outcome:

Refresh the current owner and nonce state, verify the signer and chain ID, check expiry, then create and submit a new authorization.

Using "starknet-identity". How should an Agent Card expose Starknet identity?

Expected outcome:

Publish the card at the standard well-known discovery path.
Use a stable registry address and agent ID.
Keep capabilities and reputation fields synchronized with verified on-chain data.

Security Audit

High Risk

v3 • 8/7/2026 Open versioned report

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.

Files scanned

352

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

High

SKILL.md:54

Crypto seed/private key mention

const account = new Account({ provider, address, signer: privateKey });

The example passes a private key into a funded Starknet account signer. This is legitimate signing setup, but mishandling the key can enable unauthorized transactions and loss of funds.

Risk Factors

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/internet-court-starknet-identity/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/internet-court-starknet-identity/security.svg)](https://skillstore.io/skills/internet-court-starknet-identity?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/internet-court-starknet-identity?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-starknet-identity/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/internet-court-starknet-identity.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

internet-court. (2026). starknet-identity security audit report (audit version 3) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/internet-court-starknet-identity/audits/3

BibTeX citation

@techreport{internet-court-internet-court-starknet-identity-2026,
  author = {internet-court},
  title = {starknet-identity security audit report (audit version 3)},
  institution = {Skillstore},
  year = {2026},
  number = {3},
  url = {https://skillstore.io/skills/internet-court-starknet-identity/audits/3},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "starknet-identity security audit report (audit version 3)"
version: "1.0.0"
type: report
authors:
  - name: "internet-court"
date-released: "2026-08-07"
url: "https://skillstore.io/skills/internet-court-starknet-identity/audits/3"
identifiers:
  - type: other
    value: "skillstore:internet-court-starknet-identity:audit:3"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

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.

Try These Prompts

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].

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.

Avoid

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.

Frequently Asked Questions

What is this skill for?

It explains ERC-8004 identity, reputation, and validation workflows for AI agents on Starknet.

Does it deploy contracts?

No. It provides integration guidance and examples, but contract deployment requires separate tooling and project-specific configuration.

Does it manage private keys?

No. Use secure wallet or signer infrastructure, and never place private keys in source files, prompts, or logs.

How is feedback authorized?

An agent owner signs authorization data containing fields such as agent identity, client, chain, registry, and expiry.

Can reputation change ownership?

The agent identity NFT is transferable, so the new owner inherits the reputation associated with that identity.

What information should I verify?

Verify the registry, chain, owner, transaction receipt, metadata source, feedback authorization, and validation freshness.

Developer Details

Author

internet-court

License

Apache-2.0

Author version

v1.0.0

Skillstore revision

Version notice

The installable content changed, but the author did not update the declared version.

Repository

https://github.com/internet-court/internet-court-skill/tree/main/vendored/starknet/starknet-identity

Ref

1c2ebded2116f8124f45dba86a2e567f56e64d8e

Maintenance freshness

8/7/2026

Usage

3 downloads · 0 views

File structure

📁 agents/

📄 openai.yaml

📄 LICENSE

📄 SKILL.md