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.
Best use case
sui-kiosk is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using sui-kiosk 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-kiosk/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sui-kiosk Compares
| Feature / Agent | sui-kiosk | 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 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.
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 Kiosk Integration
**Official NFT trading standard with transfer policies and royalties.**
## SDK Versions
Targets: `@mysten/kiosk` 1.2.6 (^1.2), `@mysten/sui` 2.17.0 (^2.16). Tested: 2026-05-21.
**Compatibility notes:** `@mysten/kiosk@1.2.x` types `KioskCompatibleClient` as `SuiJsonRpcClient | SuiGraphQLClient` only — `SuiGrpcClient` is not accepted. Re-check on the next minor bump.
## Overview
Kiosk provides:
- Standard NFT marketplace protocol
- Programmable transfer policies
- Automatic royalty enforcement
- Trading rule flexibility
- Marketplace interoperability
## Use Cases
- NFT marketplaces
- Game item trading
- Collectible platforms
- Any NFT trading scenario
## Quick Start
### Create Kiosk
```move
use sui::kiosk::{Self, Kiosk, KioskOwnerCap};
public fun create_kiosk(ctx: &mut TxContext): (Kiosk, KioskOwnerCap) {
kiosk::new(ctx)
}
```
### List NFT in Kiosk
```move
public fun list_nft<T: key + store>(
kiosk: &mut Kiosk,
cap: &KioskOwnerCap,
nft: T,
price: u64
) {
kiosk::place_and_list<T>(kiosk, cap, nft, price);
}
```
### Purchase from Kiosk
```move
use sui::transfer_policy::{Self, TransferPolicy};
use sui::coin::Coin;
use sui::sui::SUI;
public fun purchase_nft<T: key + store>(
kiosk: &mut Kiosk,
item_id: ID,
payment: Coin<SUI>,
policy: &TransferPolicy<T>,
ctx: &mut TxContext
): T {
let (nft, request) = kiosk::purchase<T>(kiosk, item_id, payment);
// Confirm transfer policy
transfer_policy::confirm_request(policy, request);
nft
}
```
## Transfer Policy with Royalties
```move
use sui::transfer_policy::{Self, TransferPolicy, TransferPolicyCap};
// Create policy with royalty rule
public fun create_royalty_policy<T>(
publisher: &Publisher,
royalty_bps: u64, // Basis points (e.g., 500 = 5%)
ctx: &mut TxContext
): (TransferPolicy<T>, TransferPolicyCap<T>) {
let (policy, cap) = transfer_policy::new<T>(publisher, ctx);
// Add royalty rule
royalty_rule::add<T>(
&mut policy,
&cap,
royalty_bps,
ctx
);
(policy, cap)
}
```
## Frontend Integration
```typescript
// @check:skip
import { Transaction } from '@mysten/sui/transactions';
// List NFT for sale
async function listNFT(kioskId: string, nftId: string, price: number) {
const tx = new Transaction();
tx.moveCall({
target: '0x2::kiosk::place_and_list',
arguments: [
tx.object(kioskId),
tx.object(kioskOwnerCapId),
tx.object(nftId),
tx.pure.u64(BigInt(price))
],
typeArguments: [`${PACKAGE_ID}::nft::NFT`]
});
return await signAndExecute({ transaction: tx });
}
// Purchase NFT
async function purchaseNFT(
kioskId: string,
nftId: string,
paymentCoinId: string,
policyId: string
) {
const tx = new Transaction();
tx.moveCall({
target: '0x2::kiosk::purchase',
arguments: [
tx.object(kioskId),
tx.pure.id(nftId),
tx.object(paymentCoinId)
],
typeArguments: [`${PACKAGE_ID}::nft::NFT`]
});
// Confirm transfer policy
tx.moveCall({
target: '0x2::transfer_policy::confirm_request',
arguments: [
tx.object(policyId),
// ... transfer request
]
});
return await signAndExecute({ transaction: tx });
}
```
## Best Practices
- Always use Kiosk for NFT marketplaces
- Implement transfer policies for royalties
- Support multiple payment tokens
- Handle partial fills gracefully
- Test with various NFT types
## Common Mistakes
❌ **Bypassing Kiosk transfer policies**
- **Problem:** Royalties not enforced, seller loses revenue
- **Fix:** Always use `kiosk::purchase` and `transfer_policy::confirm_request`
❌ **Not checking NFT ownership before listing**
- **Problem:** Transaction fails, poor UX
- **Fix:** Verify ownership via `kiosk::has_item` before listing
❌ **Forgetting to delist before transfer**
- **Problem:** NFT locked in Kiosk, cannot be transferred
- **Fix:** Call `kiosk::delist` before any transfer operation
❌ **Hardcoding royalty percentages**
- **Problem:** Cannot update royalties after deployment
- **Fix:** Store royalty in TransferPolicy, use admin functions to update
❌ **Not handling zero-price listings**
- **Problem:** Free listings bypass royalty enforcement
- **Fix:** Enforce minimum price in transfer policy rules
Query Kiosk docs:
```typescript
// @check:skip
const kioskInfo = await sui_docs_query({
type: "docs",
target: "kiosk",
query: "transfer policy and royalty implementation"
});
```
---
**Standard, secure, royalty-enabled NFT trading!**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-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.
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-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.