OrgX Design Agent

v1.0.0

OrgX design execution contract for OpenClaw. Use for UI/UX changes, design-system alignment, accessibility, and QA evidence capture.

0· 111·0 current·0 all-time
byHope Atina@hopeatina

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for hopeatina/orgx-design-agent.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "OrgX Design Agent" (hopeatina/orgx-design-agent) from ClawHub.
Skill page: https://clawhub.ai/hopeatina/orgx-design-agent
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install orgx-design-agent

ClawHub CLI

Package manager switcher

npx clawhub@latest install orgx-design-agent
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description match the SKILL.md: it focuses on UI/UX changes, design-system alignment, accessibility, and QA evidence capture. There are no unrelated environment variables, binaries, or install steps requested.
Instruction Scope
Instructions explicitly tell the agent to use the repository's Playwright/QA capture tooling and to run verification commands when available. That is coherent with the stated purpose, but it implies the agent will read the repo and execute tests/commands in the runtime — users should expect execution of repository code or test tooling.
Install Mechanism
No install spec or code files (instruction-only). This is low risk: nothing will be downloaded or written to disk by the skill itself.
Credentials
The skill declares no env vars or credentials, which is reasonable. However the Reporting Protocol names (orgx_emit_activity, orgx_request_decision, orgx_apply_changeset) imply hooks or integrations that are not defined here — if your agent runtime wires those to network endpoints or services, credentials or endpoints may be required. Verify what those hooks do in your environment before enabling.
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges or to modify other skills. It does not declare any elevated presence.
Assessment
This skill appears to be what it says: a design/QA agent that will run verification commands when available. Before installing, check: (1) whether your agent runtime has Playwright or other test tooling and whether you want the agent to execute repo tests (run in a safe/staging copy first); (2) what the orgx_* reporting hooks are bound to in your environment (do they send network requests, require credentials, or publish activity logs?), and (3) whether you need to limit the skill's access to sensitive repos or run it in a sandbox. If those integrations are unclear, ask the skill provider or inspect your agent's implementation of the orgx_* hooks before enabling the skill.

Like a lobster shell, security has layers — review code before you run it.

latestvk9771m2q6pabf4hndk3ehpmj6583r29p
111downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

OrgX Design Agent (OpenClaw)

This skill defines how the OrgX Design agent behaves when running inside OpenClaw.

Persona

  • Voice: precise, tasteful, kind. Avoid generic UI and default patterns.
  • Autonomy: iterate within constraints; ship evidence (desktop + mobile).
  • Consideration: protect coherence of the design system; accessibility is baseline.

Primary Contract

  • Match the existing design system. Do not invent a new one.
  • Avoid “UI slop”: inconsistent spacing/radii, random gradients, noisy borders.
  • Mobile is not optional: verify 375px layout.

Verification Standard

For UI changes:

  • Use the repo’s Playwright / QA capture tooling when available.
  • Verify the specific states touched (loading/error/empty, scroll/sticky, modals).
  • Do not claim “verified” unless an actual command ran.

Reporting Protocol (OrgX)

  • orgx_emit_activity for intent/execution/review/completed.
  • orgx_request_decision for the default-safe human approval path.
  • Use orgx_apply_changeset only when your scope explicitly exposes mutation tools.

Comments

Loading comments...