Frontmcp Production Readiness
agentfront/frontmcp
Pre-production audit, hardening, and go-live checklists for FrontMCP servers.
Operate Temps through the pinned @temps-sdk/cli package with bunx or npx.
$ npx skills add gotempsh/temps --skill temps-cli -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gotempsh/temps temps-cli --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gotempsh/temps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/temps-cli .claude/skills/temps-cli && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "temps-cli" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-cli into .claude/skills/temps-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-cli", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gotempsh/temps/tree/main/skills/temps-cliType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gotempsh/temps --skill temps-cli -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gotempsh/temps temps-cli --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gotempsh/temps.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/temps-cli .agents/skills/temps-cli && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "temps-cli" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-cli into .agents/skills/temps-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-cli", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gotempsh/temps --skill temps-cli -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gotempsh/temps temps-cli --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gotempsh/temps.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/temps-cli .cursor/skills/temps-cli && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "temps-cli" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-cli into .cursor/skills/temps-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-cli", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gotempsh/temps.git --path skills/temps-cli--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gotempsh/temps --skill temps-cli -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gotempsh/temps temps-cli --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gotempsh/temps.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/temps-cli .gemini/skills/temps-cli && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "temps-cli" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-cli into .gemini/skills/temps-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-cli", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gotempsh/temps temps-cliInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gotempsh/temps --skill temps-cli -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gotempsh/temps.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/temps-cli .github/skills/temps-cli && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "temps-cli" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-cli into .github/skills/temps-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-cli", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gotempsh/temps --skill temps-cli -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gotempsh/temps temps-cli --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gotempsh/temps.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/temps-cli .opencode/skills/temps-cli && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "temps-cli" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-cli into .opencode/skills/temps-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-cli", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
temps-cliOperate Temps through the pinned @temps-sdk/cli package with bunx or npx.
Temps CLI is an agent skill from gotempsh/temps. Operate Temps through the pinned @temps-sdk/cli package with bunx or npx. Use when the user mentions Temps CLI, @temps-sdk/cli, a CLI command, or asks to deploy, configure, inspect, automate, or administer Temps from a terminal. Covers contexts, projects, deployments, environments, services, domains, monitoring, backups, telemetry, browser Performance Insights/Core Web Vitals, Cloud, platform administration, and read-only managed-data browsing. Apply the target-context, secret-handling, confirmation, and…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/COMMANDS.md` and `references/WORKFLOWS.md`).
It sits in DevOps & Cloud, covering Deployment, Web performance and Backup and disaster recovery. It works with Bun. The repository describes itself as: AI-native open-source alternative to Vercel + Sentry + PostHog + Pingdom + Resend + E2B. 440+ CLI operations with drop-in skills for Claude Code, Codex & OpenCode — deployments… The licence is Apache-2.0.
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 80aff9a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
bunxnpxrgnpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use bunx, npx and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
TEMPS_TOKENTEMPS_API_TOKENTEMPS_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Temps CLI loads about 2k tokens when it runs, and up to ~79k if it reads all its reference files. Until then it costs about 144 tokens; SKILL.md has 708 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from gotempsh/temps at commit 80aff9a, republished under its Apache-2.0 licence (© gotempsh). 708 words, ~1,974 tokens.
.claude/skills/temps-cli/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Use the pinned zero-install package invocation to operate a Temps server. Prefer
bunx @temps-sdk/cli@0.1.36; use npx @temps-sdk/cli@0.1.36 when Bun is not
available. Treat this skill as procedural guidance and command documentation,
not as authorization to mutate a server.
command -v bunx || command -v npx to select an available package
runner. Prefer bunx when both exist.bunx @temps-sdk/cli@0.1.36 --version (or its pinned npx equivalent).
Never omit the version.bunx @temps-sdk/cli@0.1.36 <group> <command> --help when flags or
behavior may have changed. Runtime help is authoritative.--target-context <name> immediately after the package specifier.For common multi-command journeys, read references/WORKFLOWS.md.
--target-context.--force or --yes.--debug during authentication, credential creation or reveal,
or any operation whose response may contain secrets.Verify the immutable registry artifact before its first execution in a task:
expected_temps_cli_integrity='sha512-Md9Hs2IQug6YIL8mzeq7GyGsI+bN2lttm1gsri27+nfH7S9Knez8ZLbQXbLoM+er6G3sYyYbhjWEEJn6jq8A3A=='
actual_temps_cli_integrity="$(npm view @temps-sdk/cli@0.1.36 dist.integrity)"
test "$actual_temps_cli_integrity" = "$expected_temps_cli_integrity" || {
echo "Refusing to install: @temps-sdk/cli@0.1.36 integrity mismatch" >&2
exit 1
}
bunx @temps-sdk/cli@0.1.36 --versionWhen Bun is unavailable, use the same immutable version with npm:
npx @temps-sdk/cli@0.1.36 --versionNever use unpinned bunx @temps-sdk/cli, npx @temps-sdk/cli, a globally
installed mutable version, or a downloaded script.
For Performance Insights, confirm analytics performance --help exists in the
reviewed runtime. If it does not, report the version gap instead of silently
substituting OTel metrics or the traffic-only analytics top devices query.
The generated catalog contains every command, subcommand, alias, and option for the reviewed release. Search it before loading a command section:
# Find a top-level command and its subcommands
rg -n '^## `backups`|^### `backups ' skills/temps-cli/references/COMMANDS.md
# Find commands related to a capability
rg -n -i 'restore|retention|schedule' skills/temps-cli/references/COMMANDS.mdUse these routing hints:
| User intent | Command group |
|---|---|
| Authenticate or select a server | login, logout, whoami, context, configure |
| Create and deploy an application | projects, deploy, deployments, environments |
| Manage databases and storage | services, backups, data, kv, blob |
| Configure traffic and TLS | domains, custom-domains, dns, dns-provider |
| Inspect runtime behavior | containers, runtime-logs, proxy-logs, services |
| Operate observability or review desktop/mobile Web Vitals | analytics, errors, traces, session-replay, monitors, incidents |
| Configure telemetry forwarding | otel-forward |
| Manage Cloud integration | cloud |
| Manage agent capabilities | sandbox, skills, mcp-servers, secrets, workflow, ai |
| Administer the platform | platform, settings, users, audit |
Use one named context per Temps server. Inspect contexts read-only before a write:
bunx @temps-sdk/cli@0.1.36 context list
bunx @temps-sdk/cli@0.1.36 context show production
bunx @temps-sdk/cli@0.1.36 --target-context production whoamiPlace the global option immediately after the package specifier:
bunx @temps-sdk/cli@0.1.36 --target-context production projects listDo not rely on context use for agentic writes because it mutates ambient
state for subsequent commands.
Use interactive browser login for a person:
bunx @temps-sdk/cli@0.1.36 login https://temps.example.com --context production
bunx @temps-sdk/cli@0.1.36 --target-context production whoamiFor CI, inject TEMPS_TOKEN and TEMPS_API_URL from the CI secret store. Do
not print them or persist them in repository files.
Configuration commands manage non-secret CLI preferences:
bunx @temps-sdk/cli@0.1.36 configure show
bunx @temps-sdk/cli@0.1.36 configure get output-format
bunx @temps-sdk/cli@0.1.36 configure set output-format jsonRelevant environment variables:
| Variable | Purpose |
|---|---|
TEMPS_API_URL | Override the API endpoint |
TEMPS_TOKEN | Supply the preferred authentication token |
TEMPS_API_TOKEN | Supply a CI authentication token |
TEMPS_API_KEY | Supply an API key when required |
TEMPS_DEBUG | Enable debug traffic; avoid around secrets |
NO_COLOR | Disable color output |
Pair every mutation with a read-only check against the same explicit context:
# Mutation shown only as a structural example; confirm before running it.
bunx @temps-sdk/cli@0.1.36 --target-context staging projects create --name example
# Read-only evidence.
bunx @temps-sdk/cli@0.1.36 --target-context staging projects list --jsonPrefer structured output when available. Parse only fields required for the task, and redact values that can contain secrets.
@temps-sdk/cli@0.1.36.© gotempsh, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in skills/temps-cli of gotempsh/temps.
Open the folder on GitHubat commit 80aff9a
Temps CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Temps CLI this skillgotempsh/temps | 822 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Frontmcp Production Readinessagentfront/frontmcp | 146 | — | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| System Design Resilience OpsHoangNguyen0403/agent-skills-standard | 570 | — | ~902 | Automated safety check: Pass | MIT | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence |
agentfront/frontmcp
Pre-production audit, hardening, and go-live checklists for FrontMCP servers.
HoangNguyen0403/agent-skills-standard
Make a design survivable and operable: eliminate single points of failure, pick failover topology, set RPO/RTO, define readiness signals and observability, choose a deployment and rollback strategy.
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
zxkane/aws-skills
AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale.
gotempsh/temps
Manage, deploy, operate, and instrument applications with Temps.
gotempsh/temps
Add Temps analytics to React applications with comprehensive tracking capabilities including page views, custom events, scroll tracking, engagement monitoring, session recording, and Web Vitals…
gotempsh/temps
Best-practices reference for preparing and instrumenting applications on Temps.
gotempsh/temps
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins.
gotempsh/temps
Add a custom domain to a Temps project and provision an automatic SSL/TLS certificate via Let's Encrypt, driven entirely from the @temps-sdk/cli CLI.
gotempsh/temps
Add Temps error tracking to applications using the Sentry-compatible SDK.
Works with
Categories
Operate Temps through the pinned @temps-sdk/cli package with bunx or npx. Temps CLI is an agent skill from gotempsh/temps. Operate Temps through the pinned @temps-sdk/cli package with bunx or npx.
Temps CLI fits situations like: the user mentions Temps CLI; administer Temps from a terminal.
Run `npx skills add gotempsh/temps --skill temps-cli -a claude-code`. Or copy the skill folder (skills/temps-cli in gotempsh/temps) into .claude/skills/temps-cli in your project. Claude Code loads it when a task matches its description.
Run `npx skills add gotempsh/temps --skill temps-cli -a codex`. Or copy the skill folder (skills/temps-cli in gotempsh/temps) into .agents/skills/temps-cli in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gotempsh/temps --skill temps-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/temps-cli, .gemini/skills/temps-cli, .github/skills/temps-cli and .opencode/skills/temps-cli in your project.
Going by SKILL.md and its folder, Temps CLI needs the command-line tools its instructions call (bunx, npx, rg and npm) and credentials named TEMPS_TOKEN, TEMPS_API_TOKEN and TEMPS_API_KEY. Our summary lists: Node.js; A credential in TEMPS_TOKEN; A credential in TEMPS_API_TOKEN.
SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Temps CLI is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 77k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Temps CLI: Frontmcp Production Readiness (agentfront/frontmcp, 146 stars), System Design Resilience Ops (HoangNguyen0403/agent-skills-standard, 570 stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Kubeshark Installer (kubeshark/kubeshark, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
gotempsh (a GitHub organization) maintains it in gotempsh/temps, which has 822 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.
Source: gotempsh/temps on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.