Near Intents Agent Skill

Cross-chain token swap integration using NEAR Intents 1Click API. Use when building swap widgets, bridge interfaces, or multi-chain transfers across EVM, Solana, NEAR, TON, Stellar, and Tron.

942 tokens

context cost

SKILL.md, read when the skill is used

files

plus reference files

copies elsewhere

how many repositories repackaged it

1 529

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/internet-court/internet-court-skill --skill near-intents

What comes with it

57 545 bytes besides the instruction

LICENSE

references/concepts.md

rules/api-any-input-withdrawals.md

rules/api-deposit-submit.md

rules/api-quote.md

rules/api-status.md

rules/api-tokens.md

rules/deposit-evm.md

rules/deposit-near.md

rules/deposit-solana.md

rules/deposit-stellar.md

rules/deposit-ton.md

rules/deposit-tron.md

rules/intents-balance.md

rules/passive-deposit.md

rules/react-hooks.md

rules/react-swap-widget.md

rules/server-example.md

The instruction itself

7 sections, as written by the author

NEAR Intents Integration

Cross-chain token swaps via 1Click REST API. Get a quote, API provides deposit addresses, you build the deposit transaction and receive the resulting token automatically.

Quick Start - Pick Your Path

| Use Case | Start Here |

|----------|------------|

| React App | react-swap-widget.md - Example showing the pattern |

| Node.js / Script | server-example.md - Example showing the pattern |

| API Reference | api-quote.md → api-tokens.md → api-status.md |

| Chain-specific Deposits | deposit-{chain}.md |

Integration Flow

GET /v0/tokens → POST /v0/quote (dry) → POST /v0/quote (wet) → Deposit TX → POST /v0/deposit/submit → GET /v0/status

Rule Categories

| Priority | Category | Files |

|----------|----------|-------|

| 1 | Examples | react-swap-widget.md, server-example.md |

| 2 | API | api-quote.md, api-tokens.md, api-status.md, api-deposit-submit.md |

| 3 | Deposits | deposit-evm.md, deposit-solana.md, deposit-near.md, deposit-ton.md, deposit-tron.md, deposit-stellar.md |

| 4 | React Hooks | react-hooks.md |

| 5 | Advanced | intents-balance.md, passive-deposit.md |

Critical Knowledge

Use assetId from /v0/tokens - never construct manually
dry: true = preview only, dry: false = get deposit address (valid ~10 min)
Poll status until terminal: SUCCESS, FAILED, REFUNDED, INCOMPLETE_DEPOSIT
Chain-to-chain is default - depositType and recipientType default to chain endpoints

Index

Examples (HIGH)
react-swap-widget - Minimum viable React swap implementation with wagmi
server-example - Node.js script for server-side swaps

API Reference (CRITICAL)
api-tokens - Fetch supported tokens, cache result
api-quote - Get swap quote, dry=true for preview, dry=false for deposit address
api-deposit-submit - Notify API after deposit to speed up processing
api-status - Poll until terminal state (SUCCESS, FAILED, REFUNDED)
api-any-input-withdrawals - Query withdrawals for ANY_INPUT quotes

Chain Deposits (HIGH)
deposit-evm - Ethereum, Base, Arbitrum, Polygon, BSC transfers
deposit-solana - Native SOL and SPL token transfers
deposit-near - NEP-141 token transfers via wallet selector
deposit-ton - Native TON transfers via TonConnect
deposit-tron - Native TRX and TRC-20 transfers
deposit-stellar - Stellar transfers (MEMO REQUIRED)

React Hooks (MEDIUM)
react-hooks - Reusable hooks for tokens, quotes, status polling

Advanced (LOW)
intents-balance - Hold balances in intents.near for faster swaps
passive-deposit - QR code flow for manual transfers

References
concepts - Swap lifecycle, statuses, CEX warning, authentication

Resources

Docs: https://docs.near-intents.org/near-intents/integration/distribution-channels/1click-api
API Keys: https://partners.near-intents.org/
OpenAPI: https://1click.chaindefuser.com/docs/v0/openapi.yaml

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×16

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

2.3k tokens scripts

Finishing A Development Branch

by ZhanlinCui

×9

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Vercel React Best Practices

by ratacat

×7

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

1.3k tokens

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

1k tokens

How to use it

Copy the folder

Take internet-court/near-intents from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.