GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins.
Install Temps Plugin
$ npx skills add gotempsh/temps --skill temps-plugin -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gotempsh/temps temps-plugin --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-plugin .claude/skills/temps-plugin && 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-plugin" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-plugin into .claude/skills/temps-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-plugin", 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-pluginType 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-plugin -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gotempsh/temps temps-plugin --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-plugin .agents/skills/temps-plugin && 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-plugin" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-plugin into .agents/skills/temps-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-plugin", 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-plugin -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gotempsh/temps temps-plugin --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-plugin .cursor/skills/temps-plugin && 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-plugin" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-plugin into .cursor/skills/temps-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-plugin", 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-plugin--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-plugin -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gotempsh/temps temps-plugin --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-plugin .gemini/skills/temps-plugin && 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-plugin" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-plugin into .gemini/skills/temps-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-plugin", 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-pluginInstalls 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-plugin -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-plugin .github/skills/temps-plugin && 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-plugin" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-plugin into .github/skills/temps-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-plugin", 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-plugin -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-plugin --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-plugin .opencode/skills/temps-plugin && 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-plugin" agent skill from https://github.com/gotempsh/temps/tree/main/skills/temps-plugin into .opencode/skills/temps-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "temps-plugin", 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.
Facts
- Skill name
temps-plugin- GitHub stars
- 826
- Token cost
- ~1.8k tokens
- SKILL.md length
- 845 words
- Files
- 4 (incl. references)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins.
- Works in 5 steps: Establish the contract → Scaffold an independently buildable… → Build the product → …
- Creating a plugin
- SKILL.md covers 1. Establish the contract, 2. Scaffold an independently…, 3. Build the product and 4. Verify the TypeScript…, plus 1 more section
- Calls bunx
What it does
Temps Plugin is an agent skill from gotempsh/temps. Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins. Use for creating a plugin, adding an embedded console UI or deployment-event automation, testing host permissions and AI, installing from GitHub, or submitting a plugin to the public catalog. End-to-end publishing covers TypeScript GitHub-source plugins, not Rust native-package releases or in-process TempsPlugin backend crates.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/design.md`, `references/development.md` and `references/publishing.md`).
It sits in DevOps & Cloud, covering Deployment. It works with TypeScript, Rust and GitHub. 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.
When your agent uses it
- Creating a plugin
- Adding an embedded console UI
- Deployment-event automation
- Testing host permissions and AI
Example prompts
- “/temps-plugin”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5e7963a. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
bunx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Temps Plugin loads about 1.8k tokens when it runs, and up to ~7.7k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 845 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from gotempsh/temps at commit 5e7963a, republished under its Apache-2.0 licence (© gotempsh). 845 words, ~1,815 tokens.
Download SKILL.mdSave it as
.claude/skills/temps-plugin/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- temps-plugin
- description
- Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins. Use for creating a plugin, adding an embedded console UI or deployment-event automation, testing host permissions and AI, installing from GitHub, or submitting a plugin to the public catalog. End-to-end publishing covers TypeScript GitHub-source plugins, not Rust native-package releases or in-process TempsPlugin backend crates.
Create and ship a Temps plugin
For TypeScript/Bun, deliver a working external plugin, an installable source repository, and evidence of what was verified. Continue an existing project when provided; preserve its identity, storage, and user changes. Publishing is a separate outcome from building or installing.
Rust support here is limited to development and local simulator testing. Rust distribution requires the separate signed native npm-package/catalog pipeline, which this skill does not teach. Do not route a Cargo repository through the TypeScript GitHub installer or suggest copying/symlinking a binary into the host plugin directory. If Rust publication is requested, establish the supported native release procedure before claiming an end-to-end plan; do not silently change the user's implementation language.
1. Establish the contract
Record the plugin's purpose, intended user, entry point in Temps, input/output, persisted data, required host permissions, resource limits, and supported host/SDK versions. Resolve only missing decisions that affect the implementation. Prefer TypeScript + Bun for a new GitHub-installable plugin; retain Rust for existing Rust plugins or an explicit choice.
Read applicable repository instructions. Inspect the installed CLI's plugin --help
and the SDK's exports instead of assuming commands from another release exist.
The canonical TypeScript starter is
gotempsh/temps-plugin-template.
Use its current README, manifest, lockfile, and CI. The template may evolve ahead of the
npm CLI; lack of a CLI command is not a reason to invent one.
Current evidence sources in a Temps checkout:
apps/temps-cli/src/commands/plugin/: init, build, install, update, grants and dev simulator.crates/temps-external-plugins/src/repository.rs: actual source-installer build contract.crates/temps-core/src/external_plugin/: protocol, permissions, manifest and events.sdks/node/packages/plugin-sdk/src/andcrates/temps-plugin-sdk/src/: SDK APIs.- Root
DESIGN.md,web/src/components/ui/, andweb/src/globals.css: current console design.
Read development.md when scaffolding or changing runtime behavior, design.md for UI work, and publishing.md before preparing a distributable repository.
2. Scaffold an independently buildable project
Use the GitHub template or, when supported by the installed CLI:
bunx --bun @temps-sdk/cli plugin init my-plugin --name @your-scope/my-pluginThis command scaffolds local files; it does not publish. Inspect generated files before continuing. Replace placeholder identity, author, repository, version and description; keep package metadata and runtime manifest consistent. Add only tested platforms. Commit the lockfile. Keep credentials, local databases, logs, auth material, and simulator session files out of Git.
For GitHub installation, select either the repository root or a self-contained plugin
subdirectory with --path. Use --ref for a branch, tag, or commit. Verify
that a clean checkout compiles through the host installer path: lifecycle scripts and
custom UI build commands are not implicitly run. See the publishing reference for the
embedded-asset consequence.
3. Build the product
Use the SDK to own the protocol handshake and transport. Keep protocol stdout clean; log diagnostics to stderr. Use verified caller context for authorization, typed errors, and plugin-owned storage in its assigned data directory. Host data and host-brokered AI come through the SDK, never database/provider credentials copied from the host.
Declare the minimum host permissions and handle absent configuration and revoked grants visibly. Manifest declarations request permissions; administrators grant them. Permissions protect host APIs: native plugins still run with the host OS account's permissions. Do not describe the installed plugin as sandboxed.
Register discoverable navigation for a UI plugin. Use the selected Temps design standard,
embed assets, and test its real proxy path. For deployment automation, subscribe to
deployment.succeeded, keep receipt handling quick, and use bounded persistent jobs,
idempotency, cancellation and explicit environment/project settings.
Show full SKILL.md (303 more words)Show less
4. Verify the TypeScript lifecycle at three levels
- Unit and integration checks: success, validation, failures, persistence/restart, bounded work, and relevant security cases. Typecheck and compile the actual binary.
- Local plugin simulator: real binary + SDK protocol + mock host. Exercise sidebar UI, event delivery, duplicates, denied/granted/revoked permissions, and role restrictions.
- Installed Temps instance: install a reviewed repository revision, open the plugin through Temps, trigger the intended user workflow, change permissions, and update the same source. Verify persistence and relevant actor/audit attribution where supported.
Read development.md for simulator commands. A standalone unauthenticated UI preview proves layout only. Simulator/mock AI results are not real provider calls or a full host installation. A received event is not proof the job finished. Do not label end-to-end verification complete unless the installed workflow was exercised; record a concrete limitation when that environment is unavailable.
5. Distribute, list, and maintain TypeScript plugins
The default workflow is GitHub repository → reviewed source installation → catalog PR.
No npm publication, cloud publisher token, or registry signing key is needed for this path.
Read publishing.md for exact metadata and installation examples.
plugin publish is a separate native npm/signed-catalog flow, not shorthand for listing a
GitHub repository; use it only when that distribution channel is explicitly requested.
Prepare and validate all artifacts before an external publication step. Respect the user's existing authorization: creating a skill or building a plugin does not itself request public npm publication, a release tag, or installation into production. When publication is requested, show the concrete repository/version/permissions and execute only that scope. Never ask users to paste credentials into chat.
Finish with source location, preview/install instructions, declared permissions, verification evidence, distribution/catalog state and remaining limitations. For updates, retain the stable identity, version deliberately, migrate storage safely, and test a same-source upgrade. Pushing a commit does not automatically update installed plugins.
© 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
Files
SKILL.md and 3 other files (references) in skills/temps-plugin of gotempsh/temps.
- SKILL.md
- references/design.md
- references/development.md
- references/publishing.md
Open the folder on GitHubat commit 5e7963a
Compare with similar skills
Temps Plugin 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 Plugin this skillgotempsh/temps | 826 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| AI News RadarLearnPrompt/ai-news-radar | 1.8k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Reflexo ReleaseMyriad-Dreamin/typst.ts | 1.2k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Use Vercel Actionamondnet/vercel-action | 764 | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
AI News Radar
LearnPrompt/ai-news-radar
A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…
Reflexo Release
Myriad-Dreamin/typst.ts
Guide Reflexo/typst.ts release preparation and operator handoffs.
Use Vercel Action
amondnet/vercel-action
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.
1panel App Builder
arch3rPro/1Panel-Appstore
A skill your agent uses when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories…
More from gotempsh/temps
All 15 skills in this repoTemps
gotempsh/temps
Manage, deploy, operate, and instrument applications with Temps.
Add React Analytics
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…
Temps Best Practices
gotempsh/temps
Best-practices reference for preparing and instrumenting applications on Temps.
Temps CLI
gotempsh/temps
Operate Temps through the pinned @temps-sdk/cli package with bunx or npx.
Add Custom Domain
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.
Add Error Tracking
gotempsh/temps
Add Temps error tracking to applications using the Sentry-compatible SDK.
Related
Works with
Categories
Questions about Temps Plugin
What does Temps Plugin do?
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins. Temps Plugin is an agent skill from gotempsh/temps. Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins.
When should I use Temps Plugin?
Temps Plugin fits situations like: creating a plugin; adding an embedded console UI; deployment-event automation; testing host permissions and AI.
How do I install Temps Plugin in Claude Code?
Run `npx skills add gotempsh/temps --skill temps-plugin -a claude-code`. Or copy the skill folder (skills/temps-plugin in gotempsh/temps) into .claude/skills/temps-plugin in your project. Claude Code loads it when a task matches its description.
How do I install Temps Plugin in Codex?
Run `npx skills add gotempsh/temps --skill temps-plugin -a codex`. Or copy the skill folder (skills/temps-plugin in gotempsh/temps) into .agents/skills/temps-plugin in your project. Codex loads it when a task matches its description.
Can I use Temps Plugin in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gotempsh/temps --skill temps-plugin -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-plugin, .gemini/skills/temps-plugin, .github/skills/temps-plugin and .opencode/skills/temps-plugin in your project.
What does Temps Plugin need to run?
Going by SKILL.md and its folder, Temps Plugin needs the command-line tools its instructions call (bunx).
Does Temps Plugin access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Temps Plugin safe to install?
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.
What licence does Temps Plugin use?
Temps Plugin 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.
How many tokens does Temps Plugin use?
About 1.8k tokens (SKILL.md is roughly 7.3k 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 5.9k tokens, read only when the agent opens those files.
What are the alternatives to Temps Plugin?
Skills that share tags, products or a category with Temps Plugin: GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), AWS Cdk Development (zxkane/aws-skills, 367 stars), AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars) and Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Temps Plugin?
gotempsh (a GitHub organization) maintains it in gotempsh/temps, which has 826 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.