Skip to main content

Skills Hub

Browse and install community skills at skills.telemus.ai.

What you can do​

  • Search published SKILL.md packages from other Telemus operators
  • Inspect skill instructions and README content in the browser
  • Download the public skill package JSON
  • Add to my Telemus when signed in with an active license (copies the skill into your account for use in Telemus apps)

Sign in​

Browsing and downloading are public. Installing a skill into your account requires a Telemus account and an active license assignment. Use Sign in on the Skills Hub or open it from the portal Skills section with Browse public registry.

Account management, billing, and device pairing remain on portal.telemus.ai.

Server-hosted skill secrets​

Operators running a Telemus server can give one installed skill its own API keys, endpoints, and helper PATH entries. Put them in a private <skills dir>/<skill>/.env file (mode 0600), or in VRAI_SKILL_ENV_JSON. Then list the allowed key names in VRAI_SKILL_ENV_ALLOWED_KEYS (for example ACME_*,ACME_API_KEY). Values reach that skill's commands only while that skill is in use. They are redacted from tool output and are never shown to the model, approvals, or audit logs. PATH, VRAI_*, and loader or startup hook variables cannot be granted. Use the secret settings supported by your deployment, and ask your operator if a skill cannot access a required setting.

OpenClaw-compatible tool names​

Skills written for OpenClaw can use exec, read, write, edit, apply_patch, process, and browser directly. Telemus maps them to its own tools before any approval check, so the same confirmations apply. Operators can tune exec output and timeout limits with VRAI_SHELL_EXEC_MAX_OUTPUT_CHARS (default 64000), VRAI_SHELL_EXEC_MAX_STDERR_CHARS (default 16000), and VRAI_SHELL_EXEC_MAX_TIMEOUT_MS (default 1800000).