← Back to Skills Marketplace
abstrct

Structs Diplomacy

by Abstrct · GitHub ↗ · v1.2.0 · MIT-0
cross-platform ⚠ suspicious
429
Downloads
0
Stars
0
Active Installs
6
Versions
Install in OpenClaw
/install structs-diplomacy
Description
Handles permissions, address management, and inter-player coordination in Structs. Use when granting or revoking permissions on objects, registering new addr...
Usage Guidance
This skill looks like a straight mapping of CLI commands for managing Structs permissions, but it omits important operational details. Before installing or allowing the agent to use it: (1) Confirm the environment actually has the `structsd` CLI and that you trust that binary. (2) Understand where signing keys live — do not expose private keys or unlock a wallet to the agent unless you explicitly intend it to submit transactions. (3) Prefer running in a testnet or with dry-run steps until you verify behavior. (4) Ask the publisher for missing metadata (required binaries, network/RPC config, expected key management). (5) If you will allow autonomous invocation, require explicit human confirmation for any command that uses `--from` or the `-y` flag to avoid accidental on-chain changes.
Capability Analysis
Type: OpenClaw Skill Name: structs-diplomacy Version: 1.2.0 The skill bundle provides instructions for an AI agent to manage permissions and addresses within the 'Structs' ecosystem using the structsd CLI. It defines a standard bitmask-based permission system and provides query and transaction commands (SKILL.md) consistent with its stated purpose. No indicators of malicious intent, data exfiltration, or prompt injection were found.
Capability Assessment
Purpose & Capability
The SKILL.md repeatedly calls the CLI binary `structsd` and shows TX_FLAGS that require a signer (e.g. `--from [key-name]`), but the skill metadata declares no required binaries, env vars, or config paths. A permission-management skill reasonably needs the `structsd` CLI and access to a signing key / node endpoint; those are missing from the declared requirements.
Instruction Scope
Instructions direct the agent to run transaction commands (e.g. `structsd tx structs permission-grant-on-object ... -y`) that will modify on-chain state and require signing. The SKILL.md does not describe how signing keys are provided, whether a dry-run option should be used, or safeguards to prevent accidental submission. There is no guidance about network/rpc configuration (testnet vs mainnet).
Install Mechanism
This is instruction-only (no install spec), which lowers installer risk. However, because it relies on an external CLI (`structsd`) being present, the absence of a declared install step or requirement means the skill assumes the environment has that tool installed — an implicit dependency that the metadata does not state.
Credentials
No environment variables, credentials, or config paths are declared, yet the workflow requires a signer (`--from [key-name]`) and likely access to local keyrings or node endpoints. The skill does not justify or declare access to wallet keys or node RPC endpoints; this mismatch could lead to unexpected credential use if the agent is allowed to run commands.
Persistence & Privilege
always is false and there is no install hook or self-modifying behavior. The skill does not request elevated persistence or modification of other skills/configs.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install structs-diplomacy
  3. After installation, invoke the skill by name or use /structs-diplomacy
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
Sync with structs-ai upstream: v0.15 combat overhaul, 24-bit permissions, guild rank system, controller=PlayerId, guild-rank-set commands
v1.1.1
structstestnet-111 compatibility; no content changes required
v1.1.0
Updated from structs.ai: fixed reactor-begin-migration signature, guild-bank-mint signature, automated allocation limit docs, capacity=0 false positive, PoW key sequencing warnings, energy ephemeral concept. New: play-structs meta-skill.
v1.0.1
Fixed See Also references to use proper links
v1.0.0
Initial release
v0.1.0
Initial release of structs-diplomacy skill. - Provides commands for querying, granting, revoking, and setting permissions on objects and addresses. - Supports registration, revocation, and management of player addresses, including delegation and multi-address accounts. - Includes explicit TX_FLAGS usage and command syntax examples. - Documents error handling scenarios and verification procedures for permissions and address management. - Reference tables for available actions and queries for ease of use.
Metadata
Slug structs-diplomacy
Version 1.2.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 6
Frequently Asked Questions

What is Structs Diplomacy?

Handles permissions, address management, and inter-player coordination in Structs. Use when granting or revoking permissions on objects, registering new addr... It is an AI Agent Skill for Claude Code / OpenClaw, with 429 downloads so far.

How do I install Structs Diplomacy?

Run "/install structs-diplomacy" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Structs Diplomacy free?

Yes, Structs Diplomacy is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Structs Diplomacy support?

Structs Diplomacy is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Structs Diplomacy?

It is built and maintained by Abstrct (@abstrct); the current version is v1.2.0.

💬 Comments