skills.rest
514-labs
514-labsOFFICIAL
Explore all skills by this author →
Website𝕏@514hqGitHub

moose-basics

Run and debug local MooseStack environments with CLI commands and MCP inspection.

3|2|Updated Feb 5, 2026
Search Tags:#logs#mcp#infrastructure#health-check#local-dev#moose-basics#moose-stack
One-click install
npx skills add https://github.com/514-labs/agent-skills --skill moose-basics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moose-basics
Source: https://github.com/514-labs/agent-skills/tree/main/skills/moose/basics
Command: npx skills add https://github.com/514-labs/agent-skills --skill moose-basics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moose developers often struggle with onboarding and setting up a reliable local analytics stack. This skill guides users through running MooseStack locally, inspecting logs, using the moose-dev MCP, and recovering from broken dev state.

Core Features & Use Cases

  • Step-by-step guidance for starting and debugging a MooseStack project end-to-end, including moose dev, moose clean, moose ls, moose query, and moose docs.
  • Clear instructions for reading logs, diagnosing common failures, and using the moose-dev MCP for introspection.
  • Practical definitions of core primitives (OlapTable, Stream, IngestApi, MaterializedView, WebApp) and recovery recipes when hot-reload breaks.

Quick Start

Start the local MooseStack dev environment with moose dev --dockerless and verify health via the MCP and the health endpoint.

Frequently Asked Questions about moose-basics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run MooseStack locally for development?▼

Run MooseStack locally by executing the moose dev --dockerless command, then verify the environment is healthy using the health endpoint and the moose-dev MCP for introspection.

What are the core primitives in a MooseStack analytics project?▼

The core MooseStack primitives are OlapTable, Stream, IngestApi, MaterializedView, and WebApp, which collectively define the end-to-end data workflow from ingestion to analytics.

How do I inspect logs and diagnose failures in a local dev stack?▼

Inspect local dev stack logs and diagnose failures using the moose-dev MCP for introspection, reading log outputs directly, and running health checks to identify broken dev states.

What is the best way to recover a broken MooseStack dev state?▼

Recover a broken MooseStack dev state by running moose clean to reset the environment, then use moose ls to inspect the current stack status and restart with moose dev.

What should I do when hot-reload breaks in MooseStack?▼

When hot-reload breaks in MooseStack, apply the provided recovery recipes to reset the dev environment, using moose clean and restarting the stack to restore live reloading functionality.

Does MooseStack require Docker for local infrastructure setup?▼

MooseStack does not strictly require Docker for local infrastructure setup, as you can start the development environment in a dockerless mode using the moose dev --dockerless command.

Related Skills

Explore More Software Engineering Skills→
xotongxotong

ce-setup

Diagnose and configure a Compound Engineering environment with guided health checks and setup.

Community
Advanced
sunrise-hjxsunrise-hjx
12

vibeflow-moose

Coordinate MOOSE-based simulation workflows inside VibeCAE.

Community
Advanced
nirukk52nirukk52
1

dev-log-monitoring

Monitor Encore.ts and SvelteKit logs to diagnose drift and verify run events.

Community
Advanced
Davie521Davie521
7

docker-patterns

Design reusable Docker and Docker Compose patterns for local development workflows.

Community
Advanced