Menu

Individual skill

temps-platform-setup

Provision, verify, and connect a self-hosted Temps platform instance on an explicitly authorized machine. Use when the user wants an agent to install Temps with the official deploy script, configure a local CLI context, start browser device authorization, present the approval URL, wait for approval, or perform initial platform, DNS, TLS, user, and service setup without exposing credentials.

skills/temps-platform-setup/SKILL.md

Read pinned source

Source commit 9c5f782f466f81a77a4fb3877e19c58c635184c6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
904
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Temps Platform Setup

Provision a Temps instance and hand it back as a verified CLI context while
keeping infrastructure scope, browser approval, and credentials under the
user's control.

## Safety contract

Apply these rules to every workflow:

1. **Require an explicit target.** Before provisioning, identify the exact
   server hostname/IP, SSH identity, setup mode, release channel or pinned
   version, administrator email, and local context name. The user's direct
   request to provision that target is authorization for the scoped install;