Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotempsh/temps-plugin
Build external plugins for the Temps deployment platform.
Passed 19 of 23 test cases with the skill, and 7 of 23 without it.
and 15 more in the full report
12 fixed7 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are scaffolding a new extension from scratch and want to run npm init @temps/plugin or npx temps-cli init. What exact scaffolding command should we execute?
| Checked | Without skill | With skill |
|---|---|---|
| Scaffolds using the Bun executor command bunx --bun @temps-sdk/cli plugin init. | Missed | Passed |
| Instructs committing the lockfile to the git repository. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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/ and crates/temps-plugin-sdk/src/: SDK APIs.DESIGN.md, web/src/components/ui/, and web/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.
test cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.