home / skills / plurigrid / asi / d

d skill

This skill helps you manage Aptos blockchain interactions via MCP tools for balance, transfer, swap, stake, and view.

npx playbooks add skill plurigrid/asi --skill d

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.6 KB
---
name: d
description: 'World D Skill'
version: 1.0.0
---

# World D Skill

**Trit**: -1 (MINUS (validator/constrainer))
**Color Range**: Cold hues (180-300°)
**Index**: 3
**Wallet**: world_d_aptos
**MCP Server**: `mcp__world_d_aptos__*`

## GF(3) Role

This world operates as **MINUS (validator/constrainer)** in the triadic system.

Conservation law: `Σ trits ≡ 0 (mod 3)` across all parallel operations.

## Usage

Access blockchain operations via MCP tools:

```
mcp__world_d_aptos__aptos_balance      # Check APT balance
mcp__world_d_aptos__aptos_transfer     # Transfer APT (requires approval)
mcp__world_d_aptos__aptos_swap         # Swap tokens on DEX
mcp__world_d_aptos__aptos_stake        # Stake with validator
mcp__world_d_aptos__aptos_view         # Call view function (read-only)
mcp__world_d_aptos__aptos_intent       # Natural language intent
mcp__world_d_aptos__aptos_pending      # List pending decisions
mcp__world_d_aptos__aptos_approve      # Approve/reject decision
```

## World Description

Claykind data science notebooks

## Triadic Coordination

When operating in parallel with other worlds:

| Your Role | Partner Roles | Combined |
|-----------|--------------|----------|
| -1 | Need +1, 0 | Σ = 0 ✓ |

## Related Skills

- `aptos-agent` - Core Aptos interaction patterns
- `aptos-society` - World Extractable Value (WEV) contracts
- `gay-mcp` - Deterministic color generation from seed
- `plurigrid-asi-integrated` - Unified skill orchestration

## Customization

Add world-specific configurations below this line:

---

<!-- World D custom content -->

Overview

This skill exposes World D operations for Aptos through MCP tooling and frames the world as a triadic MINUS (validator/constrainer) participant. It provides wallet access, token operations, stake/validator actions, and read-only views while enforcing a GF(3) conservation rule across parallel worlds. The skill is tailored for automation and orchestration within multi-world MCP environments.

How this skill works

The skill maps a set of MCP commands (mcp__world_d_aptos__*) to common Aptos actions: balance checks, transfers, swaps, staking, view calls, natural-language intents, and pending decision workflows. It enforces the trit role (-1) and the conservation law Σ trits ≡ 0 (mod 3) when coordinating in parallel with other worlds. Operators interact via the MCP server to execute or simulate actions, and approval workflows manage constrained decisions.

When to use it

  • Managing an Aptos wallet and token operations (balance, transfer, swap).
  • Participating as a validator/constrainer in triadic coordinated workflows.
  • Automating stake and validator interactions with on-chain tooling.
  • Running Claykind data science notebooks that rely on Aptos state.
  • Coordinating multi-world decisions that require approval or rejection.

Best practices

  • Always track and log each world's trit to maintain Σ trits ≡ 0 (mod 3).
  • Use the mcp__world_d_aptos__aptos_approve endpoint for formal decisions.
  • Test transfers and swaps on a sandbox or testnet before mainnet use.
  • Limit private key exposure: run MCP commands from secure environments.
  • Monitor pending decisions and automate retries for transient failures.

Example use cases

  • Check wallet balance and prepare a transfer to another Aptos account.
  • Stake tokens with a validator while logging the action for audits.
  • Execute a token swap on a DEX and record price results for notebooks.
  • Approve or reject governance-like decisions through the pending queue.
  • Integrate with orchestration skills to maintain triadic role consistency.

FAQ

What does the trit -1 role mean?

Trit -1 designates this world as the MINUS (validator/constrainer) participant. It affects how the world must combine with partners so the modular sum constraint holds.

How do I ensure Σ trits ≡ 0 (mod 3)?

Coordinate roles across participating worlds and verify each world’s trit value before executing parallel operations. Use orchestration skills to compute and enforce the modular sum.