▍ Free Claude Code plugin · manifest checked

Does this repo need a persistent workspace?

Run a read-only evidence audit before choosing remote infrastructure. The plugin recommends a rebuildable Claude Code web session, a persistent development shell, or more investigation.

No telemetry No scripts or hooks No Terminalbox upload Source visible before install
Install from GitHub

Three commands. One local instruction bundle.

The sparse checkout fetches only the marketplace manifest and this plugin from the Terminalbox repository.

  1. 1 Add the marketplace
    claude plugin marketplace add Anchras/terminalbox --sparse .claude-plugin plugins/remote-workspace-fit
  2. 2 Install the plugin
    claude plugin install remote-workspace-fit@terminalbox-tools
  3. 3 Run inside a repository
    /remote-workspace-fit:workspace-fit
What it checks

Repository facts, not infrastructure folklore.

The skill reads orientation docs, tracked manifests, lockfiles, development scripts, container configuration, and CI files. It does not execute the workflow it finds.

01

Rebuildability

Can a clean clone restore tools and dependencies from committed instructions?

02

Live state

Do databases, watchers, queues, containers, or agent processes need to keep running?

03

Interaction

Is the valuable state an interactive shell or tmux session steered across devices?

04

External boundaries

Are private networks, SSH hops, non-GitHub sources, hardware, or local data required?

The decision boundary

The plugin is allowed to say “do not buy.”

Rebuildable web session

A fresh clone restores the useful state.

Use the provider workflow when setup is repeatable and the task can return a branch or pull request asynchronously.

Generate the free setup files →
Persistent workspace

The useful state is still running.

Consider a persistent shell when processes, interactive state, or cross-device continuity are the actual requirement.

See the €6/month persistent option →
Evidence incomplete

The deciding facts are not in the repository.

Ask one focused question or run one safe validation step. The plugin does not recommend buying anything without repository-backed evidence.

Ask for an honest fit check →
Example shape

A short recommendation you can challenge.

Every result separates observed evidence from unknowns and ends with one safe next test.

Recommendation
Rebuildable web session — the tracked lockfiles and CI setup restore the project.

Repository evidence
• package-lock.json and npm ci are committed
• CI provisions the only documented service
• no long-running local process is required

Persistence triggers
None found.

Next test
Confirm one fresh cloud session can run the documented check.
Inspect before trust

A skill file, not an agent hiding a service.

Included

One Markdown skill with the audit workflow, decision rules, and output contract.

Not included

No executable scripts, hooks, MCP servers, agents, credentials, or network client.

Forbidden by the skill

Reading secret values, installing dependencies, starting services, or changing files.

Measurement

This page records bounded view and button labels. Plugin use and repository contents are not sent to Terminalbox.