sui-suins
Use when integrating SuiNS (SUI Name Service) — resolving .sui names to addresses, reverse lookups, or registering names. Triggers on "SuiNS", ".sui name", "name resolution", "reverse lookup", "human-readable address", or any name service integration. Also use when the user wants to display user-friendly names instead of hex addresses.
Best use case
sui-suins is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when integrating SuiNS (SUI Name Service) — resolving .sui names to addresses, reverse lookups, or registering names. Triggers on "SuiNS", ".sui name", "name resolution", "reverse lookup", "human-readable address", or any name service integration. Also use when the user wants to display user-friendly names instead of hex addresses.
Teams using sui-suins should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sui-suins/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sui-suins Compares
| Feature / Agent | sui-suins | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when integrating SuiNS (SUI Name Service) — resolving .sui names to addresses, reverse lookups, or registering names. Triggers on "SuiNS", ".sui name", "name resolution", "reverse lookup", "human-readable address", or any name service integration. Also use when the user wants to display user-friendly names instead of hex addresses.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SUI SuiNS Integration
**Human-readable names for SUI addresses (like ENS for Ethereum).**
## SDK Versions
Targets: `@mysten/suins` 1.1.4 (^1.1), `@mysten/sui` 2.17.0 (^2.16). Tested: 2026-05-21.
**Compatibility notes:** `@mysten/sui` is a peer dependency. Use `SuinsClient.getNameRecord(name): Promise<NameRecord | null>` (NameRecord has `targetAddress`) — there is no `getAddress` / `getName`. Reverse lookup goes through `client.core.defaultNameServiceName({ address })`.
## Overview
SuiNS provides:
- Human-readable names (alice.sui)
- Reverse address lookup
- Name ownership and trading
- Subdomains support
## SUI v1.69 SuiNS API Changes
**GraphQL Breaking Changes:**
- `Query.suinsName(name: ...)` → `Query.address(name: ...)` for resolving SuiNS names
- `IAddressable.defaultSuinsName` → `IAddressable.defaultNameRecord.target` for reverse lookup
- New `Query.nameRecord` for fetching the full SuiNS NameRecord for a given name
```graphql
# Old (deprecated)
query { suinsName(name: "alice.sui") { address } }
# New (v1.64+, current)
query { address(name: "alice.sui") }
query { nameRecord(name: "alice.sui") { ... } }
```
## Use Cases
- User profiles
- Wallet address display
- Social features
- Payment requests
- Any user-facing addresses
## Quick Start
### Register Name
```move
use suins::registry;
public fun register_name(
name: String,
duration_years: u64,
payment: Coin<SUI>,
ctx: &mut TxContext
) {
registry::register(
name,
duration_years,
payment,
ctx
);
}
```
### Resolve Name to Address
```move
public fun resolve(name: String): Option<address> {
registry::lookup(name)
}
```
## Frontend Integration
```typescript
// @check:skip
import { SuinsClient } from '@mysten/suins';
import { SuiGrpcClient } from '@mysten/sui/grpc';
const client = new SuiGrpcClient({
network: 'mainnet',
baseUrl: 'https://fullnode.mainnet.sui.io:443',
});
const suins = new SuinsClient({ client, network: 'mainnet' });
// Resolve name to address via NameRecord
async function resolveName(name: string): Promise<string | null> {
const record = await suins.getNameRecord(name);
return record?.targetAddress ?? null;
}
// Reverse lookup: address to default name (provided by SuiGrpcClient core)
async function getName(address: string): Promise<string | null> {
const res = await client.core.defaultNameServiceName({ address });
return res.data.name;
}
// Register new name
async function registerName(name: string, years: number) {
const tx = new Transaction();
const [coin] = tx.splitCoins(tx.gas, [tx.pure(calculateCost(years))]);
tx.moveCall({
target: `${SUINS_PACKAGE}::registry::register`,
arguments: [
tx.pure(name),
tx.pure(years),
coin
]
});
return await signAndExecute({ transaction: tx });
}
```
## Display Name in UI
```tsx
// @check:skip
function AddressDisplay({ address }: { address: string }) {
const { data: name } = useQuery({
queryKey: ['suins', address],
queryFn: () => getName(address)
});
return (
<span>
{name || `${address.slice(0, 6)}...${address.slice(-4)}`}
</span>
);
}
```
## Best Practices
- Cache name resolutions
- Handle missing names gracefully
- Display both name and address
- Support .sui TLD
- Validate name format
## Common Mistakes
❌ **Not caching name resolutions**
- **Problem:** Excessive RPC calls, slow UI, rate limiting
- **Fix:** Use React Query with 5-minute cache for name lookups
❌ **Assuming all addresses have names**
- **Problem:** UI breaks when address has no SuiNS name
- **Fix:** Fallback to truncated address if name is null
❌ **Not validating name format**
- **Problem:** Invalid names sent to contract, transaction fails
- **Fix:** Validate: lowercase, alphanumeric+hyphens, ends with .sui
❌ **Forgetting to handle subdomain resolution**
- **Problem:** sub.alice.sui fails to resolve
- **Fix:** Use SuiNS SDK which handles subdomains automatically
❌ **Hard-coding name prices**
- **Problem:** Prices change, registration fails
- **Fix:** Query current pricing from SuiNS contract
❌ **Not showing expiration dates**
- **Problem:** Users lose names without warning
- **Fix:** Display expiration, send renewal reminders
❌ **Using names without ownership verification**
- **Problem:** Phishing via name squatting
- **Fix:** Verify name ownership on-chain before trusting
Query SuiNS docs:
```typescript
// @check:skip
const suinsInfo = await sui_docs_query({
type: "github",
target: "suins",
query: "name registration and resolution API"
});
```
---
**Make SUI addresses human-friendly!**Related Skills
sui-zklogin
Use when implementing zkLogin on SUI — OAuth login (Google, Facebook, Apple, Twitch) with zero-knowledge proofs for privacy-preserving authentication. Triggers on "zkLogin", "social login on SUI", "Google login", "OAuth", "ephemeral keypair", "JWT proof", or any authentication flow that derives a SUI address from an OAuth provider. Also use when the user mentions "login without wallet extension".
sui-walrus
Use when storing or retrieving files using Walrus — SUI's decentralized blob storage. Triggers on "Walrus", "blob storage", "upload file to chain", "decentralized storage", "store NFT image", "IPFS alternative on SUI", "where to store NFT metadata", "host a site on-chain", or any off-chain data storage needs on SUI. Also use for Walrus Sites (decentralized web hosting), storing game assets, media files, or when the user asks "where do I put large files on SUI".
sui-wallet
Use when performing on-chain transactions (transfer, Move call, publish) through the agent's CLI wallet via MCP tools. Triggers on "transfer SUI", "call Move function", "publish package", "wallet status", "sign transaction", or any agent-driven on-chain operation. This is for headless/backend wallet operations — for browser wallet UI (React/Vue), use sui-frontend instead.
sui-tester
Use when writing Move tests, setting up test suites, running gas benchmarks, or planning test strategy for SUI contracts. Triggers on "write tests", "test this module", "#[test]", "test coverage", "gas benchmark", "property-based test", or any Move testing task. Use even for simple "how do I test this function" questions.
sui-security-guard
Use when setting up security scanning, detecting leaked secrets/API keys, implementing pre-commit hooks, or auditing a Sui Move contract for security/architecture/quality issues. Triggers on "security scan", "detect secrets", "pre-commit hook", "security audit setup", "API key leaked", and on contract-level review requests like "audit this contract", "review access control", "is this Move safe", "check for vulnerabilities", "Move security review" — these load the SEC/DES/PAT/TST/QA/CFG finding registry in references/move-security-findings.md. For offensive/adversarial testing (attack vector discovery, writing exploits/PoCs), use sui-red-team instead. For Move style/idiom quality (non-security), use move-code-quality.
sui-seal
Use when implementing data encryption, access control, or secrets management on SUI using the Seal protocol. Triggers on threshold encryption, data privacy, token-gated content, encrypted storage, decryption policies, paywall, gated access, encrypted NFT metadata, private data sharing, or any scenario requiring on-chain access control for off-chain data. Also use when the user mentions Seal, pay-to-decrypt, "only NFT holders can see", or subscriber-only content on SUI.
sui-red-team
Use when performing adversarial security testing on SUI Move contracts — generating attack tests for access control bypass, integer overflow, object manipulation, economic exploits, reentrancy, and DoS vectors. Triggers on "red team", "attack test", "find vulnerabilities", "exploit", "pentest", "security test", or when the user wants to stress-test their contract's security. For defensive security setup (scanning, hooks, checklists), use sui-security-guard instead.
sui-passkey
Use when implementing WebAuthn passkeys or biometric authentication (Face ID, fingerprint, hardware keys) on SUI. Triggers on "passkey", "WebAuthn", "biometric login", "Face ID", "fingerprint auth", "FIDO2", or passwordless auth that uses device authenticators instead of seed phrases. Different from zkLogin (which uses OAuth providers).
sui-nautilus
Use when building verifiable off-chain computation, integrating external APIs with on-chain proof, or running trusted execution environments on SUI. Triggers on Nautilus, off-chain oracle, "verify API data on-chain", "connect external API to Move", "prove off-chain result", trusted compute, AWS Nitro Enclave, attestation, price feed, weather data on-chain, or any scenario requiring cryptographically verified external data. Also use when the user asks "how do I get real-world data into my SUI contract" or needs an oracle-like pattern.
sui-kiosk
Use when building NFT marketplaces, enforcing royalties, or managing transfer policies using SUI's Kiosk standard. Triggers on "Kiosk", "NFT marketplace", "transfer policy", "royalty enforcement", "list NFT for sale", "purchase rules", or any NFT commerce on SUI. Also use when the user asks about listing, delisting, or trading NFTs with enforced rules.
sui-install
Use when installing or updating the Sui CLI, managing CLI versions with suiup, or resolving environment/setup problems — "install sui", "update sui", "command not found", "sui not found", "client/server api version mismatch", build errors about "old dependencies", switching CLI versions per network, or installing toolchain components (Walrus, MVR, Move Analyzer, site-builder). Also use for first-time client setup, getting faucet tokens, recovering keys from a phrase, or "Cannot find gas coin for signer address". For deploying/upgrading packages use sui-deployer; for on-chain data queries use sui-ts-sdk.
sui-indexer
Use when building custom indexers, data pipelines, or event processors for the SUI blockchain. Triggers on "indexer", "data pipeline", "backfill", "event processor", "index transactions", "analytics dashboard", "aggregate on-chain data", "historical query", "track all trades", or any custom data extraction from SUI chain history. Also use when the user needs to build dashboards from on-chain data, process historical transactions, or set up real-time event streams.