Run any Skill in Manus with one click

doctor

Stars3

Forks0

UpdatedJuly 17, 2026 at 23:20

Diagnose the Spantail plugin's configuration for this repository. Use when sessions are missing from Spantail, land in the wrong workspace or project, or the user wants to check where telemetry is going.

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

spantail

spantail/spantail

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	doctor
description	Diagnose the Spantail plugin's configuration for this repository. Use when sessions are missing from Spantail, land in the wrong workspace or project, or the user wants to check where telemetry is going.
disable-model-invocation	true
allowed-tools	["Bash"]

Report how the Spantail plugin's configuration resolves in this repository and what to fix.

Run the bundled doctor script:
```
"${CLAUDE_PLUGIN_ROOT}/hooks/spantail-doctor.sh"
```
It prints each config key with its resolved value and source layer (credentials are masked), warnings about ignored keys in .spantail/ files, and a verdict on telemetry, attribution, and MCP availability.
Relay the report and turn any problem into the concrete next step:
- telemetry: DISABLED — the plugin's user config is incomplete; re-run the install dialog (reinstall the plugin) or wire SPANTAIL_API_URL / SPANTAIL_AGENT_TOKEN manually.
- attribution: NOT LINKED — run /spantail:link to link this repository to a workspace and project; until then sessions depend on the agent token's default workspace and may be dropped entirely.
- warning: … ignored — the repo file sets keys the hooks refuse to read; move apiUrl/tokens back to the plugin config.
- mcp: apiToken unset — only relevant if the user wants the Spantail skills/agents; telemetry works without it.
Never echo token values; the script already masks them — keep it that way in your summary.

More from this repository

same repository

link

spantail/spantail

Link this repository to a Spantail workspace and project so its agent sessions are attributed there. Use when the user wants to set or change where this repo's sessions are recorded in Spantail.

2026-07-173

run-demo

spantail/spantail

Launch Spantail locally with demo data and drive it in a browser from a natural-language request (English or Japanese) — run a scenario, take screenshots, or record a walkthrough. Also the launch/seed/D1 recipe for manual checks and end-to-end verification.

2026-07-113

log-work

spantail/spantail

Log a work entry to Spantail. Use when the user wants to record time spent, log what they worked on, or capture the current session's work as a Spantail work entry.

2026-07-063

create-report

spantail/spantail

Create or update a Spantail report from work entries. Use when the user asks for a weekly/monthly report, a client-facing summary of logged work, or wants to preview report output before saving it.

2026-07-053

summary

spantail/spantail

Turn sending this session's plan title to Spantail on or off. Use when the user says something like "/spantail:summary on", "record what this session was about in Spantail", or "don't send this session's summary".

2026-07-053

name	doctor
description	Diagnose the Spantail plugin's configuration for this repository. Use when sessions are missing from Spantail, land in the wrong workspace or project, or the user wants to check where telemetry is going.
disable-model-invocation	true
allowed-tools	["Bash"]

Report how the Spantail plugin's configuration resolves in this repository and what to fix.

Run the bundled doctor script:
```
"${CLAUDE_PLUGIN_ROOT}/hooks/spantail-doctor.sh"
```
It prints each config key with its resolved value and source layer (credentials are masked), warnings about ignored keys in .spantail/ files, and a verdict on telemetry, attribution, and MCP availability.
Relay the report and turn any problem into the concrete next step:
- telemetry: DISABLED — the plugin's user config is incomplete; re-run the install dialog (reinstall the plugin) or wire SPANTAIL_API_URL / SPANTAIL_AGENT_TOKEN manually.
- attribution: NOT LINKED — run /spantail:link to link this repository to a workspace and project; until then sessions depend on the agent token's default workspace and may be dropped entirely.
- warning: … ignored — the repo file sets keys the hooks refuse to read; move apiUrl/tokens back to the plugin config.
- mcp: apiToken unset — only relevant if the user wants the Spantail skills/agents; telemetry works without it.
Never echo token values; the script already masks them — keep it that way in your summary.