← Back to Skills Marketplace
S2-Nomad-Agent-Protocol
by
MilesXiang
· GitHub ↗
· v1.1.0
· MIT-0
101
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install s2-nomad-agent-protocol
Description
Instructs the OpenClaw agent on how to request geolocation, claim P-SSSU Habitable Slots with user consent, and negotiate boundaries with other agents in the...
Usage Guidance
This skill appears coherent and implements the consent-first behavior described in its documentation, but before installing you should: (1) verify that the OpenClaw runtime will prompt the user and block any sensor reads until explicit consent is given (the SKILL.md requires this but the manifest still lists geolocation/device permissions); (2) consider whether granting 'localhost' network access is acceptable (it could communicate with local BMS or home-automation services); (3) review handler.py locally (it is short and self-contained) and run it in a sandbox first if you can; and (4) do not grant any 'always-on' or background sensor permissions unless you trust the author and have confirmed the platform enforces human-in-the-loop checks.
Capability Analysis
Type: OpenClaw Skill
Name: s2-nomad-agent-protocol
Version: 1.1.0
The skill bundle implements a spatial computing protocol for 'Nomad Agents' to manage geolocation-based grid claims (P-SSSU). The handler.py contains simulation logic for territory expansion and conflict resolution using an in-memory ledger, while SKILL.md explicitly mandates human-in-the-loop (HITL) authorization and user consent before accessing GPS or claiming slots. No evidence of data exfiltration, unauthorized execution, or malicious prompt injection was found.
Capability Assessment
Purpose & Capability
The name/description (nomad agent: geolocation, claiming P-SSSU slots, boundary negotiation) align with the included files: SKILL.md specifies user-consent flows and the handler.py implements ledger, claim, and ripple expansion logic. Declared permissions (geolocation, environmental_sensors, execute_nomad_expansion) match the described capabilities.
Instruction Scope
SKILL.md explicitly requires explicit user consent prior to reading GPS or invoking expansion tools, which is good. However, the plugin manifest declares device permissions (geolocation/environmental_sensors). That is coherent with the feature set, but it raises an operational question: the platform must enforce the SKILL.md consent flow rather than allowing silent sensor access. Confirm that runtime enforces human-in-the-loop checks before any sensor read or tool invocation.
Install Mechanism
No install spec or external downloads are present; this is effectively an instruction-only skill with an included Python handler. Nothing is fetched from remote URLs or written to unusual locations.
Credentials
The skill requests no environment variables or credentials. The capabilities and permissions are proportionate to a geolocation/territory management tool. There are no unrelated secrets requested.
Persistence & Privilege
always is false and the skill does not request system-wide configuration changes. The manifest grants network access to localhost; while that's reasonable for interacting with local BMS or telemetry services (mentioned in SKILL.md), localhost access can touch sensitive local services. Ensure the platform prompts before granting those permissions and that the skill cannot enable persistent background sensor reads without consent.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install s2-nomad-agent-protocol - After installation, invoke the skill by name or use
/s2-nomad-agent-protocol - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.0
**Summary:**
v1.1.0 introduces mandatory user consent and enhances compliance for outdoor geolocation and grid claiming actions.
- Requires explicit user or system permission before accessing location or claiming grid territory.
- Adds human-in-the-loop (HITL) authorization for all outdoor takeover actions.
- Renames tools for geolocation conversion and clarifies their use.
- Restricts autonomous intervention; agent actions now advisory unless additional authorization is given.
- Expands communication guidelines to maintain user transparency regarding spatial operations.
v1.0.0
- Initial release of s2-nomad-agent-protocol.
- Enables OpenClaw agents to claim and manage outdoor P-SSSU Habitable Slots using geolocation.
- Introduces Ripple Expansion for dynamic territory growth.
- Provides automated boundary negotiation and conflict resolution between agents.
- Adds clear communication guidelines for outdoor operation status.
Metadata
Frequently Asked Questions
What is S2-Nomad-Agent-Protocol?
Instructs the OpenClaw agent on how to request geolocation, claim P-SSSU Habitable Slots with user consent, and negotiate boundaries with other agents in the... It is an AI Agent Skill for Claude Code / OpenClaw, with 101 downloads so far.
How do I install S2-Nomad-Agent-Protocol?
Run "/install s2-nomad-agent-protocol" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is S2-Nomad-Agent-Protocol free?
Yes, S2-Nomad-Agent-Protocol is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does S2-Nomad-Agent-Protocol support?
S2-Nomad-Agent-Protocol is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created S2-Nomad-Agent-Protocol?
It is built and maintained by MilesXiang (@spacesq); the current version is v1.1.0.
More Skills