arkiv-network/arkiv

Route development tasks involving Arkiv, @arkiv-network/sdk, DB-Chain or Tiramisu to the appropriate skill and explain native entity operations, query constraints and safety rules. Use when building on, reading from or writing to Arkiv, or handling untrusted Arkiv payloads and their claimed instructions; do not activate for unrelated SQL or database questions.

Integrate Arkiv SDK 0.8.x into server APIs, injected-wallet apps and event-driven caches. Use when building a read proxy, signing endpoint, wallet connection, DTO or live cache refresh; use arkiv-indexing for durable checkpointed mirrors and lifecycle skills for the entity mutation itself.

Design typed Arkiv entity models for application queries, PostgreSQL mappings, marketplace schemas and relationships. Use when choosing attributes versus payload, exact numeric encodings, application IDs, entity-key references or consistency rules. Use arkiv-social-graph to read or visualize relationships with arkiv-graph. Importing rows and executing writes require their own authorization.

Encrypt and decrypt Arkiv entity payloads with the published arkiv-encryption package. Use for payload confidentiality with an independent encryption key; attributes and metadata remain public. Use arkiv-security-trust for policy and HMAC index design. Wallet recovery, access gates and encrypted group sharing require separate implementations.

Choose and verify Arkiv Entity Expiration and Lifetime Extension with @arkiv-network/sdk. Use for ExpirationTime helpers, absolute block deadlines, adding time to an existing entity, renewal races, permanent(), expiration sweeps, and expired or missing entities. Use arkiv-entity-lifecycle for permissions and arkiv-write-safety for uncertain transaction outcomes.

Create, patch, transfer, replace, or delete Arkiv entities with @arkiv-network/sdk. Use for readonly and permissionlessExtension flags, mutation permissions, ownership versus creator provenance, patch budgets, native batch order, and restoring entity references. Use arkiv-first-write for setup or a first entity, arkiv-entity-expiration for deadlines and arkiv-write-safety for ambiguous submissions.

Draft and submit an Arkiv bug report or feature request using the official GitHub issue forms. Use when the user asks to report an Arkiv issue or agrees to report a diagnosed Arkiv bug; troubleshoot ordinary errors before offering this flow.

Set up @arkiv-network/sdk on a verified Arkiv testnet and make a first entity write with funding, safe key custody, explicit expiration, seed reconciliation and query read-back. Tiramisu is the default. Use for a first write, quickstart or minimal SDK example; use arkiv-app-integration for authenticated application endpoints.

Design and verify Arkiv-to-application entity mirrors from native operation logs, with checkpoints, replay, reorganization recovery and Entity Expiration sweeps. Use for an app or PostgreSQL projection and arkiv-sync compatibility checks. This skill's worked consumer runs Arkiv to app; use the verified arkiv-sync 0.3.0 release for the separate EVM-events-to-Arkiv direction.

Plan storage and verified retrieval of files and images larger than one Arkiv payload. Use for manifest/chunk design, SHA-256 and byte-length verification, partial uploads, coordinated Entity Expiration, PNG/JPEG storage choices, and external-blob pointers. Check arkiv-chunking and arkiv-images compatibility before adopting them; use arkiv-encryption for confidentiality.

Use an already connected Arkiv MCP for source discovery, optional public-evidence verification and event preparation. Explain tools versus skills and diagnose missing capabilities or stale profiles. Use for Arkiv MCP questions; entity writes belong to SDK skills and this skill does not install or configure a plugin.

Read Arkiv entities with the SDK select builder or raw arkiv_query JSON-RPC. Use for typed predicates, escaping, creator scoping, all-page pagination, cursor recovery, filtered counts, historical block arguments and raw native-operation encoding for non-TypeScript clients. For an existing error string, use arkiv-troubleshooting first.

Define privacy, key custody, publisher trust and authorization for Arkiv applications. Use for sensitive data, third-party entities or an Arkiv security audit. Use arkiv-encryption for its API, arkiv-app-integration for signing endpoints, arkiv-query for query mechanics and arkiv-troubleshooting for ordinary errors. Report evidence without a numeric security score.

Model follows, likes and entity references with arkiv-graph. Use when an Arkiv app needs a graph or tables from explicit relationship rules, including direction, duplicate edges and missing or expired endpoints.

Diagnose Arkiv SDK, query, RPC, wallet and stale-read failures and validate RPC/chain configuration from concrete request evidence. Use for errors or unexpected data; use arkiv-query for new queries, arkiv-first-write for setup and arkiv-write-safety directly for unknown write outcomes. Report unresolved Arkiv defects through arkiv-feedback.

Submit and reconcile Arkiv writes with @arkiv-network/sdk. Use for bulk imports, executeBatch, account writer queues, transaction versus entity nonces, TxParams, preflight funding, transport errors, EntityMutationError.txHash, receipt decoding failures, and durable progress across multiple transactions. Use arkiv-entity-lifecycle for mutation permissions and arkiv-entity-expiration for renewal targets.