deck@0.13.1
VERIFIED· startup onlyPublisher claims: "Kadal Deck: build it, rehearse it, own the room. Talks written in MDX, with an MCP server and CLI for your AI agent, narration and a teleprompter to rehearse, a phone remote to present, and a live room for polls, Q&A and reactions. Export to PDF, PNG and " Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
KADAL_DECK_TOKENConfiguration, not credentials: DECK_ADMIN_KEY, DECK_HOST, DRAG_PATH, KADAL_DECK_BUILD_RECORD, KADAL_DECK_ENTRY, KADAL_DECK_HOST, KADAL_DECK_HTTPS, KADAL_DECK_KIT, KADAL_DECK_PWA, KADAL_DECK_REMOTE_ASSETS, KADAL_DECK_SUBDIR, KADAL_DECK_TARGET, KADAL_DECK_WITHOUT_NOTES, NOTES_PATH, RESOLVE_PATH, SOURCE_PATH- Where it talks to
- kadal.cc (its own)Also vercel.sh, cloudflare.com, youtube-nocookie.com, twitter.com, bsky.app, revealjs.com, esm.sh, plantuml.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names vercel.sh, cloudflare.com, youtube-nocookie.com, twitter.com, bsky.app, revealjs.com, esm.sh, plantuml.com as well as its own vendor. The guard injects KADAL_DECK_TOKEN only into requests to kadal.cc (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.13.0
vet-skills diff deck 0.13.0 0.13.1In the sandbox, this version reached for nothing 0.13.0 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-21 and scored it 85/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 75 s · 2 scenarios · 0 deviationsStatic findings
content: `// Cloudflare Workers static assets: \`${build} && npx wrangler deploy\`.Fix: Pin versions and sources; vendor anything fetched at install time.const t = text.replace(/^/, "").replace(/\r\n?/g, "\n");Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.case "cloudflare": return `Cloudflare: ${build} && npx wrangler deploy`;Fix: Pin versions and sources; vendor anything fetched at install time.const bom = text.startsWith("");Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.run: (b) => `npx ${b}`Fix: Pin versions and sources; vendor anything fetched at install time.* (`npx wrangler deploy` after the build); Pages' Git integration needs no fileFix: Pin versions and sources; vendor anything fetched at install time.text: no.bom ? `${text}` : text,Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.throw new MissingDependencyError("Rendering slides needs Playwright and Chromium. In the deck folder run: npm install -D playwright && npx playwright install chromium");Fix: Pin versions and sources; vendor anything fetched at install time.if (/Executable doesn't exist|playwright install/i.test(msg)) throw new MissingDependencyError("Playwright is installed but Chromium is not. Run: npx playwright install chromium");Fix: Pin versions and sources; vendor anything fetched at install time.command: "npx kadal-deck login"Fix: Pin versions and sources; vendor anything fetched at install time.const NOT_SIGNED_IN = "Not signed in to a Kadal Deck host. Ask the person to run `npx kadal-deck login` (or set KADAL_DECK_TOKEN), then try again.";Fix: Pin versions and sources; vendor anything fetched at install time.command: "npx kadal-deck login"Fix: Pin versions and sources; vendor anything fetched at install time.…s()) return failure("Not signed in to a Kadal Deck host. Ask the person to run `npx kadal-deck login` in a terminal (it opens a browser to approve this machine), or to set KA…Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.