Run any Skill in Manus with one click

backend-server-verification

Stars1

Forks0

UpdatedFebruary 13, 2026 at 19:51

Canonical flow for starting and verifying a backend dev server. Use before running API tests: check port, start from correct directory, confirm readiness via short-timeout health request. Prevents 60–90+ second curl timeouts and port-conflict misdiagnosis.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

pmarashian

pmarashian/cursor-agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	backend-server-verification
description	Canonical flow for starting and verifying a backend dev server. Use before running API tests: check port, start from correct directory, confirm readiness via short-timeout health request. Prevents 60–90+ second curl timeouts and port-conflict misdiagnosis.

Backend Server Verification

Before running any API tests against a backend, verify the server is actually running and reachable.

Before Starting

Check if target port is in use: lsof -i :PORT (or equivalent).
If in use: Kill the process or document using an alternate port. Do not assume "server stuck" or blame Redis/OpenAI—port conflict is a common cause of failures.

Start Command

Always use an explicit directory so CWD is unambiguous across tool invocations.
Example: cd /absolute/path/to/backend && npm run dev (prefer absolute path).

After Start

Wait briefly (e.g. a few seconds for the process to bind).
Confirm readiness: curl -f http://localhost:PORT/api/health --max-time 5.
If curl fails: Read the terminal output for "port in use" or bind errors before retrying with long timeouts.

Two-Step Pattern (Recommended)

Invocation 1: Start the server (background or in a separate terminal).
Invocation 2: Run curl with --max-time 5 to verify; do not run long curls until health succeeds.

Integration

Use with dev-server-lifecycle-management and port-conflict-resolution for port detection and conflict handling.
Use with pre-flight-checklist / pre-implementation-check for backend tasks.

More from this repository

same repository

capacitor-vite-nextjs-backend

pmarashian/cursor-agent-skills

Setup and patterns for a Vite + React frontend with Capacitor and Ionic React, plus a separate Next.js backend in a monorepo. Use when creating or modifying a Capacitor mobile app with a Vite frontend and Next.js API, or when adding Capacitor to an existing Vite app with a Next.js backend.

2026-02-161

update-cursor-settings

pmarashian/cursor-agent-skills

Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

2026-02-131

agent-browser

pmarashian/cursor-agent-skills

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

2026-02-131

agent-workflow-guidelines

pmarashian/cursor-agent-skills

Essential workflow guidelines for AI agents working on development tasks. Use at the start of every task to ensure proper workflow, skill discovery, port detection, testing methodology, and verification. Consolidates critical prompt updates for consistent agent behavior across all tasks.

2026-02-131

asset-integration-workflow

pmarashian/cursor-agent-skills

Integrate external assets (PixelLab, ElevenLabs) into projects with proper error handling, fallback mechanisms, and testing patterns. Use when generating assets, downloading files, or integrating assets into game code. Standardizes workflow and reduces integration time by 25-35%.

2026-02-131

async-operation-handler

pmarashian/cursor-agent-skills

Handle asynchronous operations from MCP servers (PixelLab, ElevenLabs, etc.) with intelligent polling, timeout management, and parallel work opportunities. Use when waiting for async jobs, polling status, or managing long-running operations. Provides exponential backoff, ETA-aware waiting, and prevents premature downloads.

2026-02-131

name	backend-server-verification
description	Canonical flow for starting and verifying a backend dev server. Use before running API tests: check port, start from correct directory, confirm readiness via short-timeout health request. Prevents 60–90+ second curl timeouts and port-conflict misdiagnosis.

Backend Server Verification

Before running any API tests against a backend, verify the server is actually running and reachable.

Before Starting

Check if target port is in use: lsof -i :PORT (or equivalent).
If in use: Kill the process or document using an alternate port. Do not assume "server stuck" or blame Redis/OpenAI—port conflict is a common cause of failures.

Start Command

Always use an explicit directory so CWD is unambiguous across tool invocations.
Example: cd /absolute/path/to/backend && npm run dev (prefer absolute path).

After Start

Wait briefly (e.g. a few seconds for the process to bind).
Confirm readiness: curl -f http://localhost:PORT/api/health --max-time 5.
If curl fails: Read the terminal output for "port in use" or bind errors before retrying with long timeouts.

Two-Step Pattern (Recommended)

Invocation 1: Start the server (background or in a separate terminal).
Invocation 2: Run curl with --max-time 5 to verify; do not run long curls until health succeeds.

Integration

Use with dev-server-lifecycle-management and port-conflict-resolution for port detection and conflict handling.
Use with pre-flight-checklist / pre-implementation-check for backend tasks.