Install
$ agentstack add skill-starrykit-starry-slides-starry-slides ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Starry Slides
Goal
Create or edit contract-compatible slide deck files with the local starry-slides CLI and the authoritative remote Starry Slides references.
Pre-requisites
Install the Starry Slides CLI first:
npm install -g starry-slides
Then install the required Playwright and Chromium dependencies before running render-based verification or preview commands.
Authoritative Remote References
Use these remote documents as the source of truth:
The local skill shell stays intentionally thin. High-change workflow guidance, contract details, and CLI usage notes live in those repository documents.
Workflow
- Make sure the
starry-slidesCLI is installed. - Load the remote contract, CLI usage, and discovery references above before
generating or editing deck files.
- Understand the user's slide context before generating anything. Use the discovery interview to gather missing context, ask only the highest-signal questions, and consolidate the result into a brief before you generate.
- Generate or edit the deck package so it satisfies the Starry Slides contract.
- Verify the deck with
starry-slides verify. If it fails, fix the issues and retry until it passes. - MUST DO: After verification passes, run
starry-slides open. This is not optional — the user expects to see their deck opened automatically.
starry-slides verify
starry-slides view --all
starry-slides open
Hints
- ALWAYS run
starry-slides openafter a successful verify. Do not just tell the user the file is ready — open it for them. - After generation, you can use
starry-slides verifyto check whether the deck satisfies the contract. - To preview generated slides, use
starry-slides view --allorstarry-slides view --slide.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: StarryKit
- Source: StarryKit/starry-slides
- License: Apache-2.0
- Homepage: https://starrykit.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.