Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

eliza-app-development

Sterne18.705

Forks5.579

Aktualisiert19. Juni 2026 um 01:42

Use when building or changing an elizaOS-based application in this repository. Covers eliza app architecture, monorepo layout, local versus remote versus cloud routing, where to edit features, and non-negotiable runtime constraints. Eliza is the product name of this particular eliza app checkout.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

elizaOS

elizaOS/eliza

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

4 Dateien

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

eliza-cloud

elizaOS/eliza

Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts — `list my apps`, `delete this app`, `change container size`, `what are my earnings`, `top up credits`, `charge this user`, `check if they paid`, `request payout`, `regenerate api key`, `show analytics`. Covers app creation, `appId` usage, app auth flows, cloud-hosted APIs, analytics, credits, app charge requests, x402 crypto requests, affiliate links, creator monetization, payout redemptions, and custom Docker container deployments. For domain-specific ops defer to `eliza-cloud-buy-domain` / `eliza-cloud-manage-domain`.

2026-07-0218.7k

eliza-cloud-buy-domain

elizaOS/eliza

Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app ("build me X and put it on Y.com"). Uses Cloudflare as registrar after explicit user confirmation, paid from the user's existing cloud credit balance. Pairs with `build-monetized-app` (build first, then buy domain) and `eliza-cloud-manage-domain` (post-purchase: list, edit dns records, detach). Skip when the user is fine with the auto-assigned `*.apps.elizacloud.ai` subdomain.

2026-07-0118.7k

eliza-cloud-manage-domain

elizaOS/eliza

Use after a domain has been purchased through Eliza Cloud (via the `eliza-cloud-buy-domain` skill) when the user wants to look at, edit, or remove a domain or its DNS records. Covers org-wide domain listing, per-app DNS record CRUD on cloudflare-managed zones, status re-sync, external-attachment verification, and detaching a domain from an app. Use this skill any time the user references domains they already own (`my domains`, `edit dns for myapp.com`, `delete that A record`, `is myapp.com still pointing at my app`).

2026-07-0118.7k

build-monetized-app

elizaOS/eliza

Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment requests, payout redemptions, and the survival-economics loop where earnings auto-fund the agent's own hosting. Pairs with the `eliza-cloud` skill (which covers Cloud as a backend in general) by focusing specifically on the build-and-monetize flow.

2026-07-0118.7k

feed

elizaOS/eliza

Interact with Feed (feed.market): A2A and MCP endpoints for prediction markets, perpetuals, social feed, messaging, portfolio, and more. Use when the user wants to trade, post, chat, or query Feed via API key.

2026-06-1918.7k

1password

elizaOS/eliza

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.

2026-06-1918.7k

name	eliza-app-development
description	Use when building or changing an elizaOS-based application in this repository. Covers eliza app architecture, monorepo layout, local versus remote versus cloud routing, where to edit features, and non-negotiable runtime constraints. Eliza is the product name of this particular eliza app checkout.

eliza app development

This repository is an elizaOS application: a local-first assistant with CLI, dashboard, Electrobun desktop shell, connectors, and Eliza Cloud integration. Eliza is this app’s product and CLI name—not a separate platform from elizaOS.

Read These References First

references/repo-map.md for layout, edit targets, and common commands
references/runtime-and-cloud.md for runtime flow, onboarding, service routing, skills, and Eliza Cloud behavior

Editing Heuristics

Prefer packages/app-core/ for app shell behavior (API, CLI, onboarding, config).
Prefer packages/agent/ for agent providers, services, and runtime glue around elizaOS.
Prefer apps/app/ for UI and Electrobun work.
Treat eliza/cloud/ as the Eliza Cloud product and backend surface.
Treat eliza/ as upstream elizaOS. Edit it only when the bug or feature is genuinely upstream.

Hard Constraints

Do not remove NODE_PATH setup.
Do not remove the Bun exports patch.
Do not remove Electrobun startup error guards.
Keep Node and Bun paths working.

Repo Workflow

bun install
bun run verify
bun run test

Narrower commands when useful:

bun run eliza ...
bun run dev
bun run dev:desktop
bun run test:e2e

Where to Look First

Product and runtime behavior: packages/app-core/src/
Prompt, provider, and skill plumbing: packages/agent/src/
Onboarding and routing: packages/app-core/src/onboarding/ and packages/app-core/src/runtime/
Shipped default skills: bundled in @elizaos/skills, seeded into the state-dir skills folder by scripts/ensure-skills.mjs
Eliza Cloud backend or monetization: eliza/cloud/ and the shipped eliza-cloud skill

Cloud Default

If the task involves building an app and Eliza Cloud is enabled, linked, or explicitly requested, treat Cloud as the default managed backend before inventing custom auth, billing, analytics, or hosting. Use the eliza-cloud skill for app, monetization, and container details.

Related Skills

elizaos — core runtime abstractions and upstream plugin patterns
eliza-cloud — apps, billing, monetization, auth, containers