How do I install the Eliza App Development skill?

Run npx skillmds@latest add gabrielmoreira/eliza-app-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Eliza App Development safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Eliza App Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Eliza App Development free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Eliza App Development?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Eliza App Development by gabrielmoreira

Name: Eliza App Development
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Eliza App Development

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.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

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 packages/app/ for UI work and packages/app-core/platforms/electrobun/ for the Electrobun native shell.
Treat packages/cloud/ as the Eliza Cloud product and backend surface.

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 start
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/ui/src/first-run/ and packages/app-core/src/runtime/
Shipped default skills: bundled in @elizaos/skills, seeded into the state-dir skills folder by packages/app-core/scripts/ensure-skills.mjs
Eliza Cloud backend or monetization: packages/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

---name: eliza-app-developmentdescription: 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 `packages/app/` for UI work and `packages/app-core/platforms/electrobun/` for the Electrobun native shell. - Treat `packages/cloud/` as the Eliza Cloud product and backend surface. ## 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 ```bash bun install bun run verify bun run test ``` Narrower commands when useful: ```bash bun run start 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/ui/src/first-run/` and `packages/app-core/src/runtime/` - Shipped default skills: bundled in `@elizaos/skills`, seeded into the state-dir skills folder by `packages/app-core/scripts/ensure-skills.mjs` - Eliza Cloud backend or monetization: `packages/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

Frequently asked questions