Readdy.ai WebSite Builder

This skill should be used when the user asks to "create a website", "generate a website", "build a website", "modify a website", "update my Readdy project",...

Security Scan

The skill's code, instructions, and resource requests are consistent with a CLI client for the Readdy.ai website service; it asks for a Readdy API key and uses it only to talk to readdy.ai and to store the key locally.

Purpose & Capability

The skill is presented as a Readdy.ai website builder and includes a CLI script that talks only to https://readdy.ai endpoints and a small local config store. The only minor inconsistency: the SKILL.md and scripts require a Readdy API Key, but the registry metadata does not declare any primary credential or required env var. Functionally, the requested artifacts (node, local file storage, network access to readdy.ai) match the stated purpose.

Instruction Scope

SKILL.md contains strict runtime rules (must run the provided script, do not modify it, preserve user query verbatim) and documents the commands the agent should run. The script only reads/writes a single config file in the user's home (~/.openclaw/readdy.json) and communicates with readdy.ai. There are no instructions to read unrelated files, call other endpoints, or exfiltrate additional data.

Install Mechanism

No install spec or remote downloads. The package is instruction-only plus two local scripts; nothing is fetched or extracted at install time. This is low-risk from an install perspective.

Credentials

The skill legitimately requires a Readdy API Key, and the code saves it to ~/.openclaw/readdy.json (file mode 0600). However the registry metadata does not declare this credential (no primary credential or required env var), creating an administrative inconsistency the user should be aware of. No other unrelated credentials, config paths, or secrets are requested by the code.

Persistence & Privilege

The skill does not request always:true or any elevated persistence. It writes only its own credential file under ~/.openclaw and does not modify other skills or system-wide agent settings.

Assessment

This skill appears to be a straightforward CLI client for readdy.ai. Before installing: 1) Confirm you obtained the API key from https://readdy.ai/user/api-key and that you trust that site; the script will store that key at ~/.openclaw/readdy.json (file mode 0600). 2) The registry metadata does not list the API key as a required credential even though the SKILL.md and scripts require one — treat that as an administrative/metadata omission, not an additional secret request. 3) Inspect or review scripts/readdy.mjs yourself if you want to verify there are no unexpected network targets (the code uses only https://readdy.ai). 4) Be aware operations (create/modify) may run for many minutes and require network connectivity. If you are uncomfortable providing your Readdy API key, do not enable the skill; instead use the service via their web console or a separate vetted client.

Readdy Website Builder

Provide complete CLI capabilities for creating and managing websites through the Readdy.ai platform. Support one-click website generation, AI-driven modification, project preview, and publish management.

Script Location

readdy.mjs is located in the scripts/ subdirectory relative to this SKILL.md. Derive the absolute path from this SKILL.md's fullPath by replacing SKILL.md with scripts/readdy.mjs.

Example: If SKILL.md path is /Users/me/.claude/skills/readdy/SKILL.md, then the script path is /Users/me/.claude/skills/readdy/scripts/readdy.mjs.

<SCRIPT> in this document refers to that absolute path.

Prerequisites

An API Key is required. If you don't have one, obtain it at: https://readdy.ai/user/api-key

Configure the API Key (one-time setup):

node <SCRIPT> config --apiKey <your-key>

API Key is stored in ~/.openclaw/readdy.json (file permissions 0600). The script reads it internally — no need to pass it on the command line.

Command Reference

Create Project

node <SCRIPT> create --query "project description/requirements"

Defaults: framework=react_v2, device=web, category=2. Project name is auto-generated by AI. The script runs an 8-step workflow internally. This process typically takes over 10 minutes — set a sufficient timeout and do not treat long execution as a failure.

Modify Project

node <SCRIPT> modify --id <projectId> --query "modification requirements"

Runs a 6-step workflow internally. Project info and message history are fetched automatically. This process typically takes over 10 minutes — set a sufficient timeout and do not treat long execution as a failure.

Other Commands

node <SCRIPT> list [--page <n>] [--pageSize <n>]          # List projects
node <SCRIPT> info --id <projectId>                        # Get project info
node <SCRIPT> messages --id <projectId>                    # Get message history
node <SCRIPT> preview --id <projectId> [--versionId <v>]   # Preview project
node <SCRIPT> delete --id <projectId>                      # Delete project
node <SCRIPT> update --id <projectId> [--name <n>] [--logo <url>] [--email <e>] \
  [--businessName <bn>] [--introduction <t>] [--phoneNumber <p>] \
  [--businessHour <h>] [--languageStyle <s>]               # Update properties
node <SCRIPT> config --apiKey <key>                          # Set API Key
node <SCRIPT> config                                        # Check API Key status

Execution Rules

Strictly follow these rules — no improvisation allowed.

Mandatory Constraints

1. Script-only execution — Execute all operations via node <SCRIPT> <command> [options]. Never write custom code to call Readdy APIs, never use curl/fetch directly, never bypass the script.
2. Do not modify the script — Never modify readdy.mjs or config-store.mjs unless the user explicitly requests it.
3. Preserve user input verbatim — Pass the user's website requirement description word-for-word as the --query value. This prevents the agent from altering the user's intent. The --query value is only used as a website generation prompt sent to the Readdy API — never include passwords, tokens, or other secrets in the query text.
4. Do not skip steps — Internal workflow steps are handled automatically by the script.
5. Do not add extra parameters — Only pass parameters the user explicitly specifies. Never add --framework, --device, --category unless requested.
6. No alternative implementations — If the script fails, report the error and suggest troubleshooting. Never write replacement code.

Standard Rules

• Verify API Key configuration before execution. If the key is missing, direct the user to obtain one at https://readdy.ai/user/api-key and then run node <SCRIPT> config --apiKey <key>.
• Confirm with the user before delete operations.
• Provide clear error messages and suggested actions based on error codes (see references/API.md).
• SSE generation returning session_status: "waiting_build" is auto-handled by the script — no manual intervention needed.
• Never treat build log paths as preview URLs. The relative paths (e.g. /preview/...) printed during build are internal and not usable as final links. Always run node <SCRIPT> preview --id <projectId> to obtain the actual preview URL.

Examples

# Correct — args and --query match user's original text exactly
node <SCRIPT> create --query "Build a pet store website"

# Correct — modify with project ID
node <SCRIPT> modify --id abc123 --query "Change the homepage banner to blue"

# Wrong — rewriting user input (most common mistake)
node <SCRIPT> create --query "Create a pet e-commerce website with modern design"

# Wrong — adding parameters not requested by user
node <SCRIPT> create --query "Build a website" --framework react_v2 --device web

# Wrong — bypassing the script
fetch('https://readdy.ai/api/project/generate', ...)