Run any Skill in Manus with one click

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.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/Dexploarer/eliza --skill eliza-app-development

Copy and paste this command into Claude Code to install the skill

Source

Dexploarer/eliza

Stars1

Forks2

UpdatedApril 13, 2026 at 07:22

File Explorer

3 files

SKILL.md

readonly

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

More from this repository

same repository

eliza-cloud

Dexploarer/eliza

Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. Covers app creation, `appId` usage, app auth flows, cloud-hosted APIs, analytics, credits, creator monetization, and custom Docker container deployments.

2026-04-131

elizaos

Dexploarer/eliza

Use when the task involves elizaOS core runtime concepts, plugins, actions, providers, evaluators, services, memories, state composition, or upstream elizaOS development. Covers the main abstractions and the TypeScript runtime mental model.

2026-04-131

yara-authoring

Dexploarer/eliza

Write and test YARA rules for malware detection and threat hunting. Use when creating YARA signatures, detecting malware families, scanning files or memory for indicators of compromise, or building detection rules for threat intelligence.

2026-03-181

apple-reminders

Dexploarer/eliza

Manage Apple Reminders via the `remindctl` CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output. Use when the user asks about reminders, todos, tasks, to-do lists, "remind me", scheduling tasks, checking what is due today, completing or deleting reminders, or managing reminder lists on macOS.

2026-03-171

blucli

Dexploarer/eliza

BluOS CLI (blu) for discovery, playback, grouping, and volume control of Bluesound and NAD speakers. Use when the user wants to play music, stream audio, control speakers, adjust volume, group or ungroup Bluesound players, search TuneIn radio, or manage multi-room streaming setups.

2026-03-171

bluebubbles

Dexploarer/eliza

Handles sending and managing iMessages through BlueBubbles, the recommended iMessage integration. Triggers when the user wants to send a text message, send an iMessage, send a text, text someone, message a contact, react with a tapback, reply to a message thread, send an attachment via iMessage, edit or unsend a sent message, or manage group chat participants. All calls go through the generic message tool with channel="bluebubbles".

2026-03-171

Source

Dexploarer

Dexploarer/eliza

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

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

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

Related Skills

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