upstash/skills
C3Collection of skills for Upstash
★ 10+ · upstash/skills source on GitHub · this plugin in the registry
upstash/skills is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, reads credential-class env vars.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./.dsh-plugin/cordis.patch.yml |
| executes system commands | exec | ×6 src, e.g. scripts/build.mjs:2, scripts/build.mjs:2 |
| reads credential-class env vars | token_env | EU_CENTRAL_1_QSTASH_CURRENT_SIGNING_KEY, EU_CENTRAL_1_QSTASH_NEXT_SIGNING_KEY, QSTASH_CURRENT_SIGNING_KEY, QSTASH_NEXT_SIGNING_KEY, QSTASH_TOKEN, US_EAST_1_QSTASH_CURRENT_SIGNING_KEY |
Services it injects
commands credentials skills
Hooks it attaches
credentials/updated
Outbound domains
qstash.upstash.io console.upstash.com
Environment variables it reads
QSTASH_URL QSTASH_TOKEN QSTASH_CURRENT_SIGNING_KEY QSTASH_NEXT_SIGNING_KEY QSTASH_REGION US_EAST_1_QSTASH_CURRENT_SIGNING_KEY US_EAST_1_QSTASH_NEXT_SIGNING_KEY EU_CENTRAL_1_QSTASH_CURRENT_SIGNING_KEY EU_CENTRAL_1_QSTASH_NEXT_SIGNING_KEY
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.