podverse/interactive-prompts
.cursor/skills/interactive-prompts/SKILL.md
Do not complete steps that require interactive prompts (inquirer, CLI input). Tell the user their input is needed and provide exact instructions. Use when verification or workflows involve prompts, wizards, or interactive CLI tools.
$ install --global
skillsauthnpx skillsauth add podverse/podverse interactive-promptsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 10:48 PM12.6s1 file scanned
SKILL.md
- name:
- interactive-prompts
- description:
- Do not complete steps that require interactive prompts (inquirer, CLI input). Tell the user their input is needed and provide exact instructions. Use when verification or workflows involve prompts, wizards, or interactive CLI tools.
Interactive Prompts
When a workflow or verification step requires the user to enter input at a prompt (e.g. inquirer, readline, “Enter…”, “Select…”), the agent must not try to complete that step automatically (e.g. by piping input, simulating keystrokes, or assuming default choices).
Rule
- Do not run or “complete” steps that depend on interactive prompts.
- Do stop before those steps and tell the user that their input is needed to finish.
- Do give clear, copy-pasteable instructions: exact commands, what to choose at each prompt, and what to enter (e.g. report name, options).
Example: Bundle Analyzer
The bundle analyzer (tools/web-perf/bundle-analyzer) prompts for:
- “Select a previous report to compare against (or Skip comparison)”
- “Enter a description for report N”
Agent behavior: Do not run the analyzer in the background expecting to satisfy prompts. Instead, after implementing changes, say that the user needs to run the analyzer and complete the prompts, and provide:
- The command to run (e.g.
cd tools/web-perf/bundle-analyzer && npm run analyze:web). - What to choose at each prompt (e.g. “Skip comparison” or which report to compare).
- What to enter for the report name (e.g.
post-measurement-fix). - What to check afterward (e.g. open the generated JSON and confirm
clientBundleSize/serverBundleSizematch total asset size).
Summary
- Don’t: Pipe input, fake prompts, or mark interactive steps as “done” without user action.
- Do: State that the user must complete the prompt steps and give them the exact instructions to do it.
Related Skills
podverse/podverse-workers-patterns
documentation
VerifiedTrustedCommunity
Per-job env validation and config patterns for the workers app. Use when adding or changing worker commands, touching workers startup validation, or documenting worker env vars.
4SKILL.mdUpdated Apr 16, 2026
podverse/podverse-web-patterns
development
VerifiedTrustedCommunity
Common patterns and examples for the podverse-web Next.js application
4SKILL.mdUpdated Apr 16, 2026
podverse/time-format-local
tools
VerifiedTrustedCommunity
Ensures client-side time displays use formatDateTimeAbbrev for localized, readable timestamps. Use when rendering dates/times in the UI or when the user mentions time formatting or local timezone display.
4SKILL.mdUpdated Apr 16, 2026
podverse/.cursor/skills/testing-policy
testing
VerifiedTrustedCommunity
--- name: podverse-testing-policy description: Skip test implementation unless the user explicitly asks. Use when a plan or task includes adding unit tests, a test phase, or "Phase 3: Tests". version: 1.0.0 --- # Testing policy — skip tests for now ## When to use - When a plan or task includes adding unit tests, a test phase, or "Phase 3: Tests". - When deciding whether to implement tests for a feature. ## Rules 1. **We are not concerning ourselves with tests at this time.** Skip test imp
4SKILL.mdUpdated Apr 16, 2026