← Back to Skills Marketplace
shifenghu

aicade galaxy skills

by shifenghu · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
105
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install aicade-galaxy-skills
Description
Use AICADE Galaxy on https://www.aicadegalaxy.com/ to discover and invoke platform tools for AI monetization, paid APIs, subscriptions, memberships, blockcha...
README (SKILL.md)

AICADE Galaxy Skills

Use This Skill When

  • The user wants to use AICADE Galaxy platform capabilities from https://www.aicadegalaxy.com/
  • The user wants AI payment, paid API, membership, subscription, earning, or token-based tool access
  • The user wants to discover the latest platform tools from the AICADE Galaxy gateway

Core Rule

  • On first install or first activation, always run bootstrap before doing anything else
  • bootstrap must complete environment setup and artifact export in the same flow
  • Do not call invoke_artifact before bootstrap succeeds
  • Host integrations should read skill-entry.json as the machine-readable source of truth for install, export, list, and invoke commands
  • If the host platform supports an install hook or post-install command, bind it to scripts/bootstrap.mjs or scripts/bootstrap.py
  • If the host platform does not support install hooks, the first command after install must still be bootstrap

Runtime Rule

  • Prefer node first
  • If node is unavailable, use python3
  • If both are unavailable, ask the user to install Node.js

Required Environment

This skill uses these .env variables:

  • AICADE_GALAXY_BASE_URL
  • AICADE_GALAXY_API_KEY
  • AICADE_GALAXY_OUTPUT_PATH

Authentication:

  • Header name: X-API-Key
  • Header value source: AICADE_GALAXY_API_KEY

Default output directory:

  • output

Install And Prepare

Run this on install or first activation:

node {baseDir}/scripts/bootstrap.mjs

Fallback when node is unavailable:

python3 {baseDir}/scripts/bootstrap.py

Bootstrap behavior:

  • Checks whether .env already has required values
  • Runs setup_env when values are missing
  • Runs export_artifact immediately after setup
  • Produces {AICADE_GALAXY_OUTPUT_PATH}/aicade-galaxy-skill.json

Main Capabilities

Discover Current Platform Tools

Export the latest dynamic tool list from /admin/gateway/services:

node {baseDir}/scripts/export_artifact.mjs

Fallback:

python3 {baseDir}/scripts/export_artifact.py

Artifact path:

{AICADE_GALAXY_OUTPUT_PATH}/aicade-galaxy-skill.json

Invoke A Platform Tool

Pass request parameters through an args file:

node {baseDir}/scripts/invoke_artifact.mjs --artifact {AICADE_GALAXY_OUTPUT_PATH}/aicade-galaxy-skill.json --tool TOOL_NAME --args-file /tmp/invoke.json

Fallback:

python3 {baseDir}/scripts/invoke_artifact.py --artifact {AICADE_GALAXY_OUTPUT_PATH}/aicade-galaxy-skill.json --tool TOOL_NAME --args-file /tmp/invoke.json

Args file example:

{
  "city": "Beijing",
  "responsePaths": ["reason", "error_code"]
}

Invoker behavior:

  • Reads the artifact and finds the target tool by name
  • Reads parameters from --args-file
  • Validates required fields against inputSchema
  • Calls the real platform endpoint with the tool's metadata
  • Returns normalized JSON output

Normalized output:

  • Success: {"ok": true, "status": 200, "tool": "...", "serviceId": "...", "data": ..., "raw": ...}
  • Failure: {"ok": false, "status": 4xx/5xx, "tool": "...", "serviceId": "...", "error": {"message": "...", "raw": ...}}

List Current Supported Tools

SKILL.md does not hardcode the live service list. The latest supported tools come from the exported artifact.

Use:

node {baseDir}/scripts/list_tools.mjs --artifact {AICADE_GALAXY_OUTPUT_PATH}/aicade-galaxy-skill.json

Fallback:

python3 {baseDir}/scripts/list_tools.py --artifact {AICADE_GALAXY_OUTPUT_PATH}/aicade-galaxy-skill.json

Use the artifact or list_tools result as the source of truth for current services.

Usage Guidance
This skill is largely what it claims: it exports a list of AICADE Galaxy tools and invokes them using an API key. Before installing: - Backup any existing .env in the working directory. The setup scripts write .env (they replace the file with only the skill's keys), which can remove other environment entries or credentials. - Prefer creating a dedicated AICADE_GALAXY_API_KEY with minimal privileges. Do not use a broad cloud/root credential. - Inspect the artifact output (output/aicade-galaxy-skill.json) before running tool invocations to verify what remote endpoints will be called and what parameters they expect. - If you are uncomfortable with automatic bootstrap behavior, run the bundled scripts manually in a safe environment (node scripts/bootstrap.mjs or python3 scripts/bootstrap.py) so you can control input values and observe output. - Note the small template leftover: scripts also check CLAWHUB_BASE_URL as a fallback — verify the base URL points to the expected aicadegalaxy endpoint. - Consider disabling autonomous invocation for this skill (or restrict agent permissions) if you don't want the agent to call monetized/paid endpoints on its own. Given the .env overwrite behavior and the metadata mismatch, proceed only after taking the above precautions.
Capability Analysis
Type: OpenClaw Skill Name: aicade-galaxy-skills Version: 1.0.0 The aicade-galaxy-skills bundle is a legitimate toolset for interacting with the AICADE Galaxy platform (aicadegalaxy.com). It implements a dynamic discovery pattern where it fetches available service definitions from a gateway and generates a local artifact to guide the AI agent. The scripts (bootstrap, setup_env, export_artifact, and invoke_artifact) are well-structured, use standard libraries (Node.js 'http/https' and Python 'urllib'), and strictly operate within the user-configured environment variables (AICADE_GALAXY_BASE_URL and AICADE_GALAXY_API_KEY). No evidence of data exfiltration, malicious prompt injection, or unauthorized code execution was found.
Capability Assessment
Purpose & Capability
Name/description, scripts, and runtime behavior align: the skill discovers services from an AICADE Galaxy gateway and invokes them using an API key. The declared interaction (GET /admin/gateway/services, X-API-Key header, exporting an artifact, invoking tools) is consistent with the stated purpose. Minor oddity: setup scripts accept/mention a CLAWHUB_BASE_URL fallback (leftover from a template) but that does not change core behavior.
Instruction Scope
SKILL.md instructs the host to run bootstrap/export/list/invoke scripts which only read/write a local .env, write an artifact to the configured output dir, and call the configured base_url. The scripts do not attempt to read unrelated system files, but they will issue HTTP requests to the configured base URL and may log request/response previews when debug is enabled. This is expected for the skill's purpose, but the bootstrap/setup step will create/overwrite .env and always runs export_artifact after setup; that file I/O is broader than mere read-only configuration.
Install Mechanism
No install spec that downloads external binaries; this is instruction-only with local Node/Python scripts bundled in the skill. Scripts run locally and do not fetch arbitrary code. There are no external download URLs or archive extraction steps.
Credentials
The skill legitimately needs AICADE_GALAXY_BASE_URL and AICADE_GALAXY_API_KEY to call the platform and an output path. However, registry metadata lists 'Required env vars: none' while SKILL.md and the scripts require and use three environment variables — an inconsistency that can mislead users or automated installers. The API key requirement is proportionate, but the mismatch in declared vs. actual required env vars is a red flag.
Persistence & Privilege
Bootstrap/setup will write a .env file (setup_env.* writes the file replacing it with the skill's keys). That can overwrite or remove unrelated environment settings in an existing .env (risking loss of other service credentials). The skill does not request always:true and does not modify other skills, but its write-to-disk behavior and unconditional export step warrant caution.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install aicade-galaxy-skills
  3. After installation, invoke the skill by name or use /aicade-galaxy-skills
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of the AICADE Galaxy Skills. - Provides commands to bootstrap environment, export dynamic tool lists, and invoke platform tools for AI monetization and blockchain-based payments. - Supports both Node.js and Python runtimes with automatic fallback. - Exports and manages platform tool data via a machine-readable artifact. - Uses environment variables for platform connectivity and authentication. - Always runs `bootstrap` on install or first use to ensure proper setup.
Metadata
Slug aicade-galaxy-skills
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is aicade galaxy skills?

Use AICADE Galaxy on https://www.aicadegalaxy.com/ to discover and invoke platform tools for AI monetization, paid APIs, subscriptions, memberships, blockcha... It is an AI Agent Skill for Claude Code / OpenClaw, with 105 downloads so far.

How do I install aicade galaxy skills?

Run "/install aicade-galaxy-skills" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is aicade galaxy skills free?

Yes, aicade galaxy skills is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does aicade galaxy skills support?

aicade galaxy skills is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created aicade galaxy skills?

It is built and maintained by shifenghu (@shifenghu); the current version is v1.0.0.

💬 Comments