synthlabs-setup

Locate, start, and verify a local SynthLabs backend via GET /health.

321|26|Updated Mar 10, 2026

Search Tags:#backend #setup #readiness #health-check #local-development #synthlabs

Ready to run

npx skills add https://github.com/mkurman/tamux --skill synthlabs-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: synthlabs-setup
Source: https://github.com/mkurman/tamux/tree/main/skills/synthlabs/synthlabs-setup
Command: npx skills add https://github.com/mkurman/tamux --skill synthlabs-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locate a SynthLabs checkout, start the documented local services, and verify the backend health before API-dependent work.

Core Features & Use Cases

Locate a SynthLabs checkout and confirm required anchors exist (package.json with name synthlabs-reasoning-generator, server/index.js, and .env.example as anchors).
Start local services using npm, bun, or the repo's Docker Compose path, selecting the appropriate workflow for the environment.
Verify backend readiness via the health endpoint before proceeding with generation, curation, or UI tasks.

Quick Start

Locate a SynthLabs checkout, use the appropriate startup path (npm, bun, or Docker Compose), and verify the backend health before proceeding.

Frequently Asked Questions about synthlabs-setup

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

FAQPage Schema

How do I verify a local backend health check before starting API-dependent development?▼

Verify local backend readiness by sending a GET request to the /health endpoint. This confirms services are running and ready for API-dependent work before proceeding with generation or UI tasks.

Can I use Docker Compose to start local backend services instead of npm or bun?▼

Yes, Docker Compose is supported as a startup workflow alongside npm and bun. The setup detects the repo's Docker Compose path and uses it to start the documented local services for the backend.

Why does local backend setup preserve the existing .env.local file?▼

Preserving the existing .env.local file ensures safe setup by maintaining your current configuration. The process also avoids using placeholder secrets to prevent invalid or insecure backend initialization.

What should I do if the backend health endpoint is not responding after startup?▼

If the health endpoint is not responding, verify the startup workflow completed successfully using npm, bun, or Docker Compose. Check that required repo anchors exist and the readiness contract validates the backend.