← Back to Skills Marketplace
OrgX
by
Hope Atina
· GitHub ↗
· v3.1.0
· MIT-0
99
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install orgx
Description
Use when managing work with OrgX — reporting progress, requesting decisions, registering artifacts, syncing memory, checking quality gates, or viewing org st...
Usage Guidance
Do not install or run this plugin blindly. Specific cautions and next steps:
- The SKILL.md asks you to install a third‑party package via npx/openclaw and to set ORGX_API_KEY, but the registry metadata does not declare these—ask the publisher for a source repository and an explicit install spec. Verify the @useorgx package on npm/GitHub and inspect its code before running.
- The integration explicitly pushes local files (MEMORY.md, daily logs) to OrgX; review those files for sensitive data first. Treat this as potential data exfiltration until you can confirm what the remote service stores and who can access it.
- Ask which endpoints the plugin calls, where OrgX is hosted for your installation, and whether traffic is encrypted and retained. Prefer deployments where the OrgX service is under your control (self-hosted) rather than an unknown remote service.
- If you must try it, run the install in a sandboxed environment (VM or disposable container), monitor network calls, and avoid providing high‑privilege credentials until the package is audited.
- Request that the skill metadata be updated to declare required env vars (e.g., ORGX_API_KEY) and a formal install spec, and that the publisher provide a homepage/source repo and release signatures. Without those, the mismatch between instructions and metadata is a red flag.
Capability Analysis
Type: OpenClaw Skill
Name: orgx
Version: 3.1.0
The skill bundle encourages the systematic exfiltration of local agent context, specifically the contents of 'MEMORY.md' and session logs, to an external service (mcp.useorgx.com) via the 'orgx_sync' tool. While this behavior is aligned with the stated purpose of 'multi-agent orchestration,' the instructions in SKILL.md steer the agent to report all progress, artifacts, and internal state to a third-party endpoint by default. Additionally, the setup process suggests executing remote code via 'npx @useorgx/openclaw-plugin', which presents a supply chain risk.
Capability Assessment
Purpose & Capability
The skill claims to integrate with OrgX (reporting, syncing memory, quality gates) but the registry metadata lists no required environment variables, no install spec, and no primary credential. SKILL.md explicitly references an ORGX_API_KEY and installation of @useorgx/openclaw-plugin (via npx or openclaw plugins install). Those requirements are not declared in the metadata, which is inconsistent and unexplained.
Instruction Scope
Runtime instructions tell the agent to push local data (e.g., contents of MEMORY.md and a daily log) and to register artifacts and status. That can exfiltrate sensitive local content. The document also prescribes calling many OrgX APIs and spawning sub-agents (orgx_spawn_check, orgx_run_action) without clearly bounding what data is collected or where it is sent. It also instructs installing and invoking an external plugin via npx, which executes remote code.
Install Mechanism
There is no install specification in the skill metadata, but SKILL.md tells users to run 'openclaw plugins install @useorgx/openclaw-plugin' or 'npx @useorgx/openclaw-plugin'. Those commands would download and execute third-party code from npm (or a plugin registry). Because installation is recommended but not captured in the registry spec, the install path and trustworthiness are unclear — this raises risk (npx runs remote code).
Credentials
SKILL.md references ORGX_API_KEY and implies interactions with external model endpoints (anthropic/claude, ollama/qwen) but the skill metadata declares no required environment variables or credentials. Requesting to sync local memory and dashboard pairing suggests the need for credentials and network access; those are not declared, which is disproportionate and hides important attack surface (credential handling, API access).
Persistence & Privilege
The skill itself is instruction-only and not marked always:true, so it has no built-in persistent presence. However, it explicitly asks the user to install a persistent plugin (@useorgx/openclaw-plugin). That external plugin — not represented in the skill metadata — could persist, gain privileges, or run autonomously. The potential for persistent capability comes from that external install, not the skill metadata.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install orgx - After installation, invoke the skill by name or use
/orgx - Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.1.0
Align the OrgX OpenClaw skill with the current plugin MCP surface and safe reporting contract.
Metadata
Frequently Asked Questions
What is OrgX?
Use when managing work with OrgX — reporting progress, requesting decisions, registering artifacts, syncing memory, checking quality gates, or viewing org st... It is an AI Agent Skill for Claude Code / OpenClaw, with 99 downloads so far.
How do I install OrgX?
Run "/install orgx" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is OrgX free?
Yes, OrgX is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does OrgX support?
OrgX is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created OrgX?
It is built and maintained by Hope Atina (@hopeatina); the current version is v3.1.0.
More Skills