---
name: constellation-status
description: This skill should be used when the user asks "is Constellation working", "check Constellation status", "run a health check", "is the project indexed", "test the connection", or before troubleshooting to confirm whether MCP connectivity, API authentication, and project indexing are healthy.
---

# Constellation Status & Health Check

Check Constellation connectivity, authentication, and indexing using the `code_intel` tool (from the `constellation` MCP server). Two depths: a quick ping for "is it up", a full health check for diagnosis.

## Quick Status (ping)

```javascript
const result = await api.ping();
return result;
```

**If successful** (`result.pong === true`), report:

- Status: Connected
- Authentication valid, project access confirmed
- Note: run the full health check below, or `api.getCapabilities()`, to check indexing status

**If error** (`result.success` is false), report based on error code:

| Error Code | Response |
|------------|----------|
| `AUTH_ERROR` | "Status: Auth Failed - Run `constellation auth` to configure credentials" |
| `PROJECT_NOT_REGISTERED` | "Status: Project Not Found - Verify project ID or check organization access" |
| `PROJECT_INACTIVE` | "Status: Project Inactive - Project has been deactivated" |
| `API_UNREACHABLE` | "Status: API Offline - Check network connectivity and API URL in constellation.json" |
| Other codes | Show error code, message, and guidance from `result.error` |
| Missing error object | Note "Unexpected response structure" and show raw result |

**If the tool call fails entirely**, report that the Constellation MCP server is not running or not configured, and run the full health check below.

## Full Health Check

```javascript
const result = await api.getArchitectureOverview({});
return {
  success: result.success,
  error: result.error,
  primaryLanguage: result.data?.metadata?.primaryLanguage,
  files: result.data?.metadata?.totalFiles,
  symbols: result.data?.structure?.symbols?.total
};
```

Interpret the response and report using this format:

### If the tool call FAILS ENTIRELY (timeout, connection error, MCP not found)

```
Constellation Health Check
===========================
MCP Server:  UNREACHABLE
API Auth:    -

Issue: The Constellation MCP server is not running or not configured.

Quick Fixes:
1. Restart your agent client to reinitialize MCP connections
2. Verify npm can run: npx @constellationdev/mcp@latest --version
3. Check the plugin's mcp.json configuration
```

### If `result.success` is true

```
Constellation Health Check
===========================
MCP Server:  OK
API Auth:    OK
Project:     <primaryLanguage> project
Index:       <files> files, <symbols> symbols

All systems operational.
```

### If `result.success` is false, check `result.error.code`

**AUTH_ERROR:**

```
Constellation Health Check
===========================
MCP Server:  OK
API Auth:    FAILED

Issue: Authentication failed - API key missing or invalid.

Quick Fix: Run `constellation auth` to configure credentials.
```

**PROJECT_NOT_INDEXED:**

```
Constellation Health Check
===========================
MCP Server:  OK
API Auth:    OK
Project:     Not indexed

Issue: This project hasn't been indexed yet.

Quick Fix: Run `constellation index --full` in your project directory.
```

**API_UNREACHABLE:**

```
Constellation Health Check
===========================
MCP Server:  OK
API Auth:    UNREACHABLE

Issue: Cannot reach the Constellation API server.

Quick Fixes:
1. Check network connectivity
2. Verify API URL in constellation.json
3. For self-hosted: ensure API is running at configured URL
```

**Other errors:**

```
Constellation Health Check
===========================
MCP Server:  OK
API Auth:    ERROR

Code: <error.code>
Message: <error.message>

Guidance: <error.guidance if available>
```

Keep the response brief and actionable. For deeper fixes, see the `constellation-troubleshooting` skill.