framer-debug-bundle
Collect Framer debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Framer problems. Trigger with phrases like "framer debug", "framer support bundle", "collect framer logs", "framer diagnostic". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill framer-debug-bundle --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Framer Debug Bundle ## Overview Collect diagnostic information for Framer plugin or Server API issues including package versions, API connectivity, and configuration. ## Instructions ### Step 1: Create Debug Bundle ```bash #!/bin/bash BUNDLE="framer-debug-$(date +%Y%m%d-%H%M%S)" mkdir -p "$BUNDLE" echo "=== Framer Debug Bundle ===" | tee "$BUNDLE/summary.txt" echo "Date: $(date -u)" >> "$BUNDLE/
What does the framer-debug-bundle skill do?
Collect Framer debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Framer problems. Trigger with phrases like "framer debug", "framer support bundle", "collect framer logs", "framer diagnostic". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill framer-debug-bundle --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
