near-smart-contracts
NEAR Protocol smart contract development in Rust
Install / Use
npx skills add internet-court/internet-court-skill --skill near-smart-contractsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of near-smart-contracts
near-smart-contracts scores 90/100 on our quality scale, 469th of 1,111 Security skills we index (top 43%).
Its SKILL.md is 14 KB long, well organised into 37 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
With 7,124 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 21 days ago, so near-smart-contracts is actively maintained.
- Our last check on 2026-10-29 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
ReviewOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (3 minor notes below). An AI review judged it risky: The skill file instructs the agent to run three `curl ... | sh` commands to install Rust, cargo-near, and near-cli-rs.
- noteInstalls by piping a downloaded script into a shellline 33
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh - noteInstalls by piping a downloaded script into a shellline 39
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/cargo-near/releases/latest/download/cargo-near-installer.sh | sh - noteInstalls by piping a downloaded script into a shellline 42
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh
AI review: risky
- The skill file instructs the agent to run three `curl ... | sh` commands to install Rust, cargo-near, and near-cli-rs.
- In a skill/rules file, directing the agent to pipe a downloaded remote script into a shell weakens safeguards and is classified as risky.
- Other content (project setup rules, security guidelines, resource links) is benign and does not indicate malicious intent.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
near-smart-contracts compared with similar skills
All 4 of these similar skills score higher than near-smart-contracts; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| near-smart-contracts (this skill)by internet-court | 90 | 7.1k | 21d ago | SKILL.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install near-smart-contracts?
- Run
npx skills add internet-court/internet-court-skill --skill near-smart-contracts. The install tabs above show the steps for each supported agent. - Which AI agents does near-smart-contracts work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is near-smart-contracts safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (3 minor notes below). An AI review judged it risky: The skill file instructs the agent to run three
curl ... | shcommands to install Rust, cargo-near, and near-cli-rs. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand. - Is near-smart-contracts still maintained?
- The repository was last updated 21 days ago, so near-smart-contracts is actively maintained.
Skill content
View source on GitHubname: near-smart-contracts description: NEAR Protocol smart contract development in Rust. Use when writing, reviewing, or deploying NEAR smart contracts. Covers contract structure, state management, cross-contract calls, testing, security, and optimization patterns. Based on near-sdk v5.x with modern macro syntax. license: MIT metadata: author: near version: "1.0.0"
NEAR Smart Contracts Development
Comprehensive guide for developing secure and efficient smart contracts on NEAR Protocol using Rust and the NEAR SDK (v5.x).
When to Apply
Reference these guidelines when:
- Writing new NEAR smart contracts in Rust
- Reviewing existing contract code for security and optimization
- Implementing cross-contract calls and callbacks
- Managing contract state and storage
- Testing and deploying NEAR contracts
- Optimizing gas usage and performance
Getting Started
Prerequisites
Install the required tools before starting development:
# Install Rust (if not already installed)
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
# Add wasm32 target for compiling contracts
rustup target add wasm32-unknown-unknown
# Install cargo-near (build, deploy, and manage contracts)
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/cargo-near/releases/latest/download/cargo-near-installer.sh | sh
# Install near-cli-rs (interact with NEAR network)
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh
Create a New Project
CRITICAL: ALWAYS run
cargo near newto create new projects. NEVER manually create Cargo.toml, lib.rs, or any project files. The command generates all required files with correct configurations.
# REQUIRED: Create a new contract project using the official template
cargo near new my-contract
# Navigate to project directory
cd my-contract
# Build the contract
cargo near build
# Run tests
cargo test
Why cargo near new is mandatory:
- Generates correct
Cargo.tomlwith proper dependencies and build settings - Creates proper project structure with
src/lib.rstemplate - Includes integration test setup in
tests/directory - Configures release profile with
overflow-checks = true - Sets up correct crate-type for WASM compilation
- Avoids common configuration mistakes that cause build failures
DO NOT:
- Manually create
Cargo.toml - Manually create
src/lib.rs - Copy-paste project structure from examples
- Skip this step and create files directly
Project Structure
my-contract/
├── Cargo.toml # Dependencies and project config
├── src/
│ └── lib.rs # Main contract code
├── tests/ # Integration tests
│ └── test_basics.rs
└── README.md
Deploy to Testnet
# Create a testnet account (if needed)
near account create-account sponsor-by-faucet-service my-contract.testnet autogenerate-new-keypair save-to-keychain network-config testnet create
# Build in release mode
cargo near build --release
# Deploy to testnet
cargo near deploy my-contract.testnet without-init-call network-config testnet sign-with-keychain send
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
| --------- | ---------- | -------- | --------- |
| 1 | Security & Safety | CRITICAL | security- |
| 2 | Contract Structure | HIGH | structure- |
| 3 | State Management | HIGH | state- |
| 4 | Cross-Contract Calls | MEDIUM-HIGH | xcc- |
| 5 | Contract Upgrades | MEDIUM-HIGH | upgrade- |
| 6 | Chain Signatures | MEDIUM-HIGH | chain- |
| 7 | Gas Optimization | MEDIUM | gas- |
| 8 | Yield & Resume | MEDIUM | yield- |
| 9 | Testing | MEDIUM | testing- |
| 10 | Best Practices | MEDIUM | best- |
1. Security & Safety (CRITICAL)
security-storage-checks- Always validate storage operations and check depositssecurity-access-control- Implement proper access control usingpredecessor_account_idsecurity-reentrancy- Protect against reentrancy attacks (update state before external calls)security-overflow- Useoverflow-checks = truein Cargo.toml to prevent overflowsecurity-callback-validation- Validate callback results and handle failuressecurity-private-callbacks- Mark callbacks as#[private]to prevent external callssecurity-yoctonear-validation- Validate attached deposits with#[payable]functionssecurity-sybil-resistance- Implement minimum deposit checks to prevent spam
2. Contract Structure (HIGH)
structure-near-bindgen- Use#[near(contract_state)]macro for contract struct (replaces old#[near_bindgen])structure-initialization- Implement proper initialization with#[init]patternsstructure-versioning- Plan for contract upgrades with versioning mechanismsstructure-events- Useenv::log_str()and structured event logging (NEP-297)structure-standards- Follow NEAR Enhancement Proposals (NEPs) for standardsstructure-serializers- Use#[near(serializers = [json, borsh])]for data structsstructure-panic-default- Use#[derive(PanicOnDefault)]to require initialization
3. State Management (HIGH)
state-collections- Use SDK collections fromnear_sdk::store:IterableMap,IterableSet,Vector,LookupMap,LookupSet,UnorderedMap,UnorderedSet,TreeMapstate-serialization- Use Borsh for state, JSON for external interfacesstate-lazy-loading- Use SDK collections for lazy loading to save gas (loaded on-demand, not all at once)state-pagination- Implement pagination with.skip()and.take()for large datasetsstate-migration- Plan state migration strategies using versioningstate-storage-cost- Remember: 1 NEAR ≈ 100kb storage, contracts pay for their storagestate-unique-prefixes- Use unique byte prefixes for all collections (avoid collisions)state-native-vs-sdk- Native collections (Vec, HashMap) load all data; use only for <100 entries
4. Cross-Contract Calls (MEDIUM-HIGH)
xcc-promise-chaining- Chain promises correctlyxcc-callback-handling- Handle all callback scenarios (success, failure)xcc-gas-management- Allocate appropriate gas for cross-contract callsxcc-error-handling- Implement robust error handlingxcc-result-unwrap- Never unwrap promise results without checks
5. Contract Upgrades & Migration (MEDIUM-HIGH)
upgrade-migration- Use enums for state versioning and implementmigratemethod with#[init(ignore_state)]upgrade-self-update- Pattern for contracts that can update themselves programmaticallyupgrade-cleanup-old-state- Always remove old state structures to free storageupgrade-dao-controlled- Use multisig or DAO for production upgrade governance
6. Chain Signatures (MEDIUM-HIGH)
chain-signatures- Derive foreign blockchain addresses, request MPC signatures, and build multichain transactionschain-callback-handling- Handle MPC signature callbacks properlychain-gas-allocation- Allocate sufficient gas for MPC calls (yield/resume pattern)
7. Gas Optimization (MEDIUM)
gas-batch-operations- Batch operations to reduce transaction costsgas-minimal-state-reads- Minimize state reads and writes (cache in memory)gas-efficient-collections- Choose appropriate collection types (LookupMap vs IterableMap)gas-view-functions- Mark read-only functions as view (&selfin Rust)gas-avoid-cloning- Avoid unnecessary cloning of large data structuresgas-early-validation- Userequire!early to save gas on invalid inputsgas-prepaid-gas- Attach appropriate gas for cross-contract calls (recommended: 30 TGas)
8. Yield & Resume (MEDIUM)
yield-resume- Create yielded promises, signal resume, handle timeouts, and manage state between yield/resumeyield-gatekeeping- Protect resume methods from unauthorized callers
9. Testing (MEDIUM)
testing-integration-tests- Usenear-sandbox+near-apifor integration teststesting-unit-tests- Write comprehensive unit tests with mock contextstesting-sandbox- Test with local sandbox environment before testnet/mainnettesting-edge-cases- Test boundary conditions, overflow, and empty statestesting-gas-profiling- Profile gas usage in integration teststesting-cross-contract- Test cross-contract calls and callbacks thoroughlytesting-failure-scenarios- Test promise failures and timeout scenariostesting-time-travel- Usesandbox.fast_forward()for time-sensitive tests
10. Best Practices (MEDIUM)
best-contract-tools- Usenear-sdk-contract-toolsfor NEP standards (FT, NFT, etc.) and NEP-297 structured eventsbest-panic-messages- Provide clear, actionable panic messagesbest-logging- Useenv::log_str()for debugging and event emissionbest-documentation- Document public methods, parameters, and complex logicbest-error-types- Define custom error types or use descriptive stringsbest-constants- Use constants for magic numbers and configurationbest-require-macro- Userequire!instead ofassert!for better error messagesbest-promise-return- Return promises from cross-contract calls for proper trackingbest-sdk-crates- Reuse SDK-exported crates (borsh, serde, base64, etc.)best-account-id-encoding- Encode AccountIds in base32 for 40% storage savings
How to Use
Read individual rule files for detailed explanations and code examples:
rules/security-storage-checks.md
rules/structure-near-bindgen.md
rules/state-collections.md
rules/xcc-promise-chaining.md
rules/upgrade-migration.md
rules/chain-signatures.md
rules/yield-resume.md
rules/best-contract-tools.md
rules/testing-integration-tests.md
Each rule file contains:
- Brief explanation of why it matters
- Incorrect code example with explanation
- Correct code example with explanation
- Additional context and NEAR-specific considerations
Latest Tools & Versions
Development Tools
- cargo-near: Latest - Build, deploy, and manage contracts (
cargo near build,cargo near deploy) - near-cli-rs: Latest - Command-line interface for NEAR (
near contract call,near contract view) - rustc: Latest stable - Rust compiler
- near-sandbox: Latest - Local sandbox environment for integration testing
- near-api-rs: Latest - Rust API client for interacting with NEAR (replaces near-workspaces-rs for tests)
- omni-transaction-rs: Latest - Build transactions for multiple blockchains (Bitcoin, Ethereum, etc.)
SDK Versions
- near-sdk-rs: v5.x (v6.x coming with structured errors support)
- near-sdk-contract-tools: Latest - Derive macros for NEP standards (FT, NFT, Storage Management)
Key Features
- Unified macro syntax:
#[near(contract_state)]replaces#[near_bindgen]+ derives - Flexible serialization:
#[near(serializers = [json, borsh])]for data structs - Store collections:
near_sdk::store::IterableMap,IterableSet,LookupMap,LookupSet,Vector,UnorderedMap,UnorderedSet,TreeMap - Simplified cross-contract calls: High-level promise API with
Promise::new()and.then() - Built-in NEP support: FT (NEP-141), NFT (NEP-171), and other standards
- Result handling:
#[handle_result]for methods returningResult<T, E>without panicking - Yield/Resume: Contracts can yield execution and wait for external services to resume
- Chain Signatures: Sign transactions for other blockchains (Bitcoin, Ethereum, Solana, etc.)
- Contract Tools: Derive macros for Owner, Pause, Role-based access control patterns
Resources
- NEAR Documentation: https://docs.near.org
- Smart Contract Quickstart: https://docs.near.org/smart-contracts/quickstart
- Contract Anatomy: https://docs.near.org/smart-contracts/anatomy/
- NEAR SDK Rust: https://docs.near.org/tools/sdk
- SDK Rust Referenc
Truncated for display — read the full file on GitHub.
Related Skills
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
