Agent skill · software engineering · jeremylongshore
framer-debug-bundle
Collect Framer debug evidence for support tickets and troubleshooting.
Why this skill is useful
Adds an executable script for collecting comprehensive diagnostic information specific to Framer, which the AI wouldn't generate on its own.
What it needs
Requires bash installed locally. About 1k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Framer Debug Bundle Prerequisites An incident owner, secure evidence location, retention date, redaction rules for tokens and visitor data, and an opaque correlation ID. Error Handling Stop collection if a credential, customer submission, or private page content is found; rotate the affected credential if necessary and preserve only approved evidence. Examples Collect a synthetic staging publish failure using release/version data and an opaque ID, review the bundle for secrets and form submissions, then restrict it to the incident owner and retire it at the retention date. Overview Collect diagnostic information for Framer plugin or Server API issues including package versions, API connectivity, and configuration. Instructions Step 1: Create Debug Bundle Output summary.txt with runtime, packages, connectivity Configuration files (non-sensitive) Compressed archive for support Resources Framer Support Framer Changelog Next Steps For rate limit issues, see framer-rate-limits.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/framer-debug-bundle