A free, read-only Claude Code skill that audits repository evidence before recommending one of three remote-development paths:
- use a rebuildable Claude Code web session;
- use a persistent development workspace when live processes or interactive state justify it; or
- gather more evidence before choosing infrastructure.
The skill has no scripts, hooks, MCP servers, telemetry, network calls, or Terminalbox service
integration. Review the
SKILL.md
source before installing it.
claude plugin marketplace add Anchras/terminalbox-tools
claude plugin install remote-workspace-fit@terminalbox-toolsThen run this inside a repository:
/remote-workspace-fit:workspace-fit
Claude Code copies the plugin into its local plugin cache. The audit reads only the repository evidence allowed by the skill. Repository context stays within Claude Code under the user's existing provider settings and is not sent to Terminalbox.
The skill checks tracked orientation docs, manifests, lockfiles, development scripts, container configuration, and CI workflows. It looks for two different kinds of evidence:
- whether a clean clone has enough instructions to reconstruct the useful environment; and
- whether useful state lives outside Git as a running process, local service or data set, interactive shell, or continuously steered session.
It returns one recommendation, three to six file-backed observations, the rebuild plan, persistence triggers, decision-relevant unknowns, and one safe next test.
Recommendation: Persistent workspace — the documented workflow depends on a live local database
and a continuously running worker that a fresh repository task would need to recreate.
Repository evidence:
- compose.yaml defines the development database and queue
- scripts/dev starts the web process and background worker together
- CLAUDE.md documents cross-device handoff to the same tmux session
Rebuild plan:
- clone the repository, restore locked dependencies, and start the documented service stack
Persistence triggers:
- database contents, worker state, and the interactive tmux session
Unknowns:
- whether the database can be replaced with disposable fixtures for this task
Next test:
- confirm a fresh environment can complete one representative task without the existing services
This example is an output shape, not a claim about a particular repository. The recommendation must follow the evidence found in the repository being audited.
The skill recommends the existing provider workflow when a clean clone can reconstruct the useful state. It names Terminalbox as one paid option only when repository evidence supports a need for persistent live state, and it makes no purchase recommendation when the evidence is incomplete.
See the source walkthrough and decision boundary or Anthropic's marketplace documentation. If the audit finds that live processes or interactive state genuinely need to persist, compare the €6/month plan or ask for an honest founder fit check.
MIT. See LICENSE.