Skills near-kit

📦

near-kit

Name: near-kit
Author: internet-court

Content revision r1 Safe ⚙️ External commands🌐 Network access📁 Filesystem access

Build NEAR Apps with TypeScript

NEAR integrations often need transaction, wallet, key, and testing patterns. This skill gives concise near-kit examples for TypeScript apps, React hooks, wallets, and sandbox tests.

Supports: Claude Codex Code(CC)

📊 76 Adequate

Install with my Agent

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

Agent request

Review the Skillstore skill "near-kit" from https://skillstore.io/skills/internet-court-near-kit.md and its manifest at https://skillstore.io/api/skills/internet-court-near-kit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

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-near-kit.md Signed manifest GET /api/skills/internet-court-near-kit/manifest Signed lockfile GET /api/skills/internet-court-near-kit/lockfile

Test it

Using "near-kit". I need a wallet-connected guestbook call in React.

Expected outcome:

A component-level integration plan using NearProvider, wallet connection state, and a signed contract call.
Notes on signer identity, gas settings, pending states, and user-visible errors.

Using "near-kit". I need to deploy and test a NEAR contract locally.

Expected outcome:

A sandbox testing sequence with account creation, contract deployment, initialization, and assertions.
Guidance on unique account names, startup timeouts, and cleanup after tests.

Using "near-kit". I need a secure NEP-413 login flow.

Expected outcome:

A client and server flow for message signing, challenge creation, signature verification, and nonce expiration.
Security checks for recipient matching, replay prevention, and trusted backend storage.

Security Audit

Safe

v2 • 7/21/2026 Open versioned report

All 99 static findings are false positives caused by Markdown fences, TypeScript template literals, placeholders, or legitimate NEAR development documentation. The reviewed materials contain no embedded credentials, prompt-injection text, unauthorized command execution, or evidence of data exfiltration. Key-handling examples should still be used only with protected server-side secrets.

Files scanned

1,524

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (41)

🌐 Network access (4)

references/keys-and-testing.md:323 references/transactions.md:186 references/wallets.md:36 references/wallets.md:37

📁 Filesystem access (6)

references/keys-and-testing.md:269 references/keys-and-testing.md:44 references/keys-and-testing.md:44 references/transactions.md:75 SKILL.md:146 SKILL.md:146

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: claude 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-near-kit/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/internet-court-near-kit.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). near-kit security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/internet-court-near-kit/audits/2

BibTeX citation

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

CITATION.cff

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

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Create a dApp Wallet Flow

Use React hooks and wallet adapters to connect accounts, call contracts, and display balances.

Build Server-Side NEAR Automation

Configure signed transactions, key stores, relayer flows, and message verification for trusted server processes.

Test Contract Integrations

Use sandbox examples to create accounts, deploy WASM contracts, call methods, and validate integration behavior.

Try These Prompts

Create a Read-Only Client

Show me how to use near-kit to read a NEAR contract view method on testnet. Include imports, client setup, and error handling notes.

Add Wallet Calls in React

Help me add @near-kit/react to a React app. Use wallet-based signing and show the provider, account state, and a contract call.

Design a Transaction Flow

Plan a near-kit transaction that creates an account, funds it, deploys a contract, and initializes it. Include gas and deposit guidance.

Review Keys and Relayers

Review my near-kit key management and relayer design. Check private key handling, nonce validation, recipient checks, and server-only boundaries.

Best Practices

Use wallet adapters in browsers and keep private keys in trusted server environments only.
Replace example accounts, URLs, gas, and deposit values with values reviewed for the target network.
Add explicit nonce, recipient, expiry, and signer checks for login and meta-transaction flows.

Avoid

Do not paste real private keys or seed phrases into prompts, examples, logs, or source files.
Do not use placeholder domains, contract IDs, or account IDs in production deployments.
Do not let browser code manage server private keys or relayer signing keys.