Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gotempsh/add-node-sdk
Integrate the Temps Node.js SDKs for server-side platform access, KV storage, and Blob storage.
Passed 22 of 22 test cases with the skill, and 7 of 22 without it.
and 23 more in the full report
15 fixed7 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to import the official platform API client package for Temps in my TypeScript backend. Which package import path should I use when setting up the client instance?
| Checked | Without skill | With skill |
|---|---|---|
| Imports client from @temps-sdk/node-sdk package | Missed | Passed |
| Does not import from @temps-sdk/node package | Passed | Passed |
The instructions your model reads when the skill loads.
Integrate Temps platform features in Node.js / TypeScript apps.
Verified against the real published packages. A prior version of this skill referenced
@temps-sdk/node(which does not exist),new Temps({ apiKey, projectId }),temps.track(),new KV({ apiKey, namespace }),kv.has(),blob.get(),blob.getSignedUrl(),TempsError— none of those exist. Confirm any API before changing it:npm pack @temps-sdk/node-sdk@latest @temps-sdk/kv@latest @temps-sdk/blob@latest for t in temps-sdk-*-*.tgz; do tar -xzf "$t"; echo "== $t =="; cat package/dist/index.d.ts | head -60; rm -rf package; done
| Package | Purpose |
|---|---|
@temps-sdk/node-sdk | Full platform API client (generated) + Sentry-style server error tracking |
@temps-sdk/kv | Vercel-KV-style key/value store |
@temps-sdk/blob | Vercel-Blob-style file store |
There is no
@temps-sdk/node. The platform client package is@temps-sdk/node-sdk.
npm install @temps-sdk/node-sdk # platform API + error tracking
npm install @temps-sdk/kv # optional: KV storage
npm install @temps-sdk/blob # optional: blob storage
@temps-sdk/node-sdkTempsClient is a generated client (hey-api) over the Temps OpenAPI surface. Construct it with a baseUrl and apiKey, then call resource sub-namespaces.
import { TempsClient } from '@temps-sdk/node-sdk';
const temps = new TempsClient({
baseUrl: process.env.TEMPS_API_URL!, // e.g. https://app.temps.sh
apiKey: process.env.TEMPS_API_KEY, // create under Settings → API Keys
});
// Resource namespaces (each maps to OpenAPI operations):
// temps.projects, temps.deployments, temps.analytics, temps.sessionReplay,
test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.