← Back to Skills Marketplace
ArkiTek Relay
by
raleighgardner16-source
· GitHub ↗
· v1.0.5
· MIT-0
241
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install arkitek-relay
Description
Connect this agent to ArkiTek for secure remote chat via SSE. No tunnels, no open ports.
README (SKILL.md)
ArkiTek Relay Skill
This skill connects your OpenClaw agent to ArkiTek — a web UI for chatting with AI agents remotely. It opens a secure, outbound-only SSE connection from your agent to ArkiTek's cloud relay. No tunnels, public URLs, or open ports required.
Setup
- Get your API key from arkitekai.com (Agents → Add Agent → Create)
- Set the environment variable or add it to your OpenClaw config:
ARKITEK_API_KEY=ak_your_key_here
- Start the relay by running:
npx arkitek-relay-skill
The skill will connect to ArkiTek and listen for messages. When a user sends a message from the ArkiTek UI, it arrives here. Your response is sent back to ArkiTek automatically.
When to use this skill
- Use this skill when you want to connect to ArkiTek so users can chat with you remotely
- Run
npx arkitek-relay-skillin the background to maintain the connection - The connection auto-reconnects if it drops
How it works
ArkiTek Web UI ←→ ArkiTek Cloud ←——SSE—— Your Agent (this skill)
(user) (relay) ——POST→
All connections are outbound from the agent. Nothing is exposed on the agent's network.
Security
- Outbound-only HTTPS connections — no open ports or public URLs
- TLS enforced — refuses to run if TLS verification is disabled
- API key validated before any network request
- API keys are never logged
Usage Guidance
This skill is coherent for connecting to ArkiTek, but be aware npx will fetch and run code from npm at runtime. Before installing/running: 1) Inspect the arkitek-relay-skill package source on npm/GitHub and review its code (or ask the vendor for a reproducible release). 2) Use a dedicated ArkiTek API key with minimal privileges and be prepared to rotate it. 3) Consider running the relay in an isolated environment (container, VM) if you don't trust the package. 4) Recognize that a long-lived outbound connection will allow remote users to interact with the agent — ensure the agent's capabilities and access to sensitive data are appropriately limited.
Capability Analysis
Type: OpenClaw Skill
Name: arkitek-relay
Version: 1.0.5
The arkitek-relay skill facilitates a remote communication bridge between the agent and an external service (arkitekai.com) using Server-Sent Events (SSE). While its stated purpose is to enable remote chat, this architecture creates a persistent outbound connection that functions as a command-and-control (C2) channel, allowing external entities to send instructions to the agent. The reliance on an external npm package (arkitek-relay-skill) executed via npx introduces significant supply chain risk and potential for unauthorized remote access.
Capability Assessment
Purpose & Capability
Name/description, required binaries (node, npx), required env var (ARKITEK_API_KEY), and the declared npm install (arkitek-relay-skill) all align with a relay/remote-chat integration. Nothing requested appears unrelated to providing an outbound SSE-based relay.
Instruction Scope
SKILL.md instructs only to set ARKITEK_API_KEY and run 'npx arkitek-relay-skill' to open an outbound SSE connection. It does not direct the agent to read unrelated files, other credentials, or send data to unexpected endpoints. It does ask the agent to maintain a background connection and auto-reconnect, which is expected for a relay.
Install Mechanism
Install is via an npm package (arkitek-relay-skill), which is a normal mechanism for Node tooling. However, 'npx' will fetch and execute package code at runtime; because no package source code is included in this skill bundle, you cannot audit what will be executed. This is a moderate installation risk typical of npm installs.
Credentials
Only a single API key (ARKITEK_API_KEY) is required and is declared as primaryEnv. That is proportional to a cloud relay integration. The SKILL.md does not request other credentials or config paths.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide privileges. However, running the relay spawns a long-lived outbound connection that allows remote users to send messages to the agent — consider the operational implications (long-running process, remote-driven interactions). Autonomous invocation is allowed by default (not a unique concern here).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install arkitek-relay - After installation, invoke the skill by name or use
/arkitek-relay - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.5
Initial release of arkitek-relay
- Connects OpenClaw agents to ArkiTek for secure, remote chat via outbound SSE.
- No need for tunnels, public URLs, or open ports.
- Requires only an ArkiTek API key and node environment.
- Easy setup using npm and a single npx command.
- Ensures robust security with TLS enforcement and outbound-only connections.
Metadata
Frequently Asked Questions
What is ArkiTek Relay?
Connect this agent to ArkiTek for secure remote chat via SSE. No tunnels, no open ports. It is an AI Agent Skill for Claude Code / OpenClaw, with 241 downloads so far.
How do I install ArkiTek Relay?
Run "/install arkitek-relay" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is ArkiTek Relay free?
Yes, ArkiTek Relay is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does ArkiTek Relay support?
ArkiTek Relay is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created ArkiTek Relay?
It is built and maintained by raleighgardner16-source (@raleighgardner16-source); the current version is v1.0.5.
More Skills