linktree-debug-bundle
Debug Bundle for Linktree. Trigger: "linktree debug bundle".
Best use case
linktree-debug-bundle is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Debug Bundle for Linktree. Trigger: "linktree debug bundle".
Teams using linktree-debug-bundle should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/linktree-debug-bundle/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How linktree-debug-bundle Compares
| Feature / Agent | linktree-debug-bundle | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Debug Bundle for Linktree. Trigger: "linktree debug bundle".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# Linktree Debug Bundle
## Overview
This debug bundle collects diagnostic evidence from Linktree link-in-bio API integrations
for troubleshooting profile rendering, link analytics, and webhook delivery issues. It
captures OAuth token validity, profile metadata retrieval, individual link status checks,
click analytics availability, and webhook endpoint health. The resulting tarball gives
support engineers the data needed to diagnose broken links, missing analytics events,
profile sync failures, and API permission issues without requiring Linktree admin access.
## Prerequisites
- `curl`, `jq`, `tar` installed
- `LINKTREE_API_KEY` set (OAuth bearer token from Linktree developer portal)
## Debug Collection Script
```bash
#!/bin/bash
set -euo pipefail
BUNDLE="debug-linktree-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE"
# Environment check
echo "=== Environment ===" > "$BUNDLE/environment.txt"
echo "API Key: ${LINKTREE_API_KEY:+SET (redacted)}" >> "$BUNDLE/environment.txt"
echo "Node: $(node -v 2>/dev/null || echo 'not installed')" >> "$BUNDLE/environment.txt"
echo "Timestamp: $(date -u)" >> "$BUNDLE/environment.txt"
# API connectivity — user profile
echo "=== API Health ===" > "$BUNDLE/api-health.txt"
curl -sf -o "$BUNDLE/api-health.txt" -w "HTTP %{http_code} in %{time_total}s\n" \
-H "Authorization: Bearer ${LINKTREE_API_KEY}" \
"https://api.linktree.com/v1/user" 2>&1 || echo "UNREACHABLE" > "$BUNDLE/api-health.txt"
# Profile links enumeration
echo "=== Links ===" > "$BUNDLE/links.json"
curl -sf -H "Authorization: Bearer ${LINKTREE_API_KEY}" \
"https://api.linktree.com/v1/links" \
>> "$BUNDLE/links.json" 2>&1 || echo '{"error":"FAILED"}' > "$BUNDLE/links.json"
# Link click analytics (last 7 days)
echo "=== Analytics ===" > "$BUNDLE/analytics.json"
curl -sf -H "Authorization: Bearer ${LINKTREE_API_KEY}" \
"https://api.linktree.com/v1/analytics?period=7d" \
>> "$BUNDLE/analytics.json" 2>&1 || echo '{"error":"ANALYTICS_FAILED"}' > "$BUNDLE/analytics.json"
# Recent logs
echo "=== Recent Logs ===" > "$BUNDLE/app-logs.txt"
tail -100 /var/log/linktree-sync/*.log >> "$BUNDLE/app-logs.txt" 2>/dev/null || echo "No sync logs found" >> "$BUNDLE/app-logs.txt"
# Rate limit status
echo "=== Rate Limits ===" > "$BUNDLE/rate-limits.txt"
curl -sI -H "Authorization: Bearer ${LINKTREE_API_KEY}" \
"https://api.linktree.com/v1/user" 2>/dev/null | grep -i "x-rate\|retry-after\|x-ratelimit" >> "$BUNDLE/rate-limits.txt" || echo "No rate limit headers" >> "$BUNDLE/rate-limits.txt"
# Package versions
echo "=== Dependencies ===" > "$BUNDLE/deps.txt"
npm ls 2>/dev/null | grep -i linktree >> "$BUNDLE/deps.txt" || echo "No Linktree npm packages found" >> "$BUNDLE/deps.txt"
tar -czf "$BUNDLE.tar.gz" "$BUNDLE" && rm -rf "$BUNDLE"
echo "Bundle: $BUNDLE.tar.gz"
```
## Analyzing the Bundle
```bash
tar -xzf debug-linktree-*.tar.gz
cat debug-linktree-*/environment.txt # Verify API key is set
cat debug-linktree-*/api-health.txt # Check HTTP status and latency
jq '.links | length' debug-linktree-*/links.json # Count active links
jq '.totalClicks' debug-linktree-*/analytics.json # Verify analytics data
```
## Common Issues
| Symptom | Check in Bundle | Fix |
|---------|----------------|-----|
| 401 Unauthorized | `environment.txt` shows key NOT SET | Generate new API key in Linktree Developer Settings |
| Profile returns but links empty | `links.json` has empty array | Ensure links are published (not draft); check link visibility settings |
| Analytics returns 403 | `analytics.json` shows permission error | Analytics API requires Pro plan or higher; upgrade Linktree subscription |
| Click counts stuck at zero | `analytics.json` shows `totalClicks: 0` | Analytics lag up to 24h; verify links have `tracking` enabled |
| 429 rate limited | `rate-limits.txt` shows retry-after | Linktree allows 100 req/min; implement request queuing with backoff |
| Webhook not firing | App logs show no delivery attempts | Verify webhook URL in Linktree admin; check SSL cert validity on receiving endpoint |
## Automated Health Check
```typescript
async function checkLinktreeHealth(): Promise<{
status: string;
latencyMs: number;
profileOk: boolean;
linkCount: number;
analyticsAvailable: boolean;
}> {
const apiKey = process.env.LINKTREE_API_KEY;
const headers = { Authorization: `Bearer ${apiKey}` };
const start = Date.now();
const profileRes = await fetch("https://api.linktree.com/v1/user", { headers });
const linksRes = await fetch("https://api.linktree.com/v1/links", { headers });
const analyticsRes = await fetch("https://api.linktree.com/v1/analytics?period=7d", { headers });
let linkCount = 0;
if (linksRes.ok) {
const data = await linksRes.json();
linkCount = data.links?.length ?? 0;
}
return {
status: profileRes.ok ? "healthy" : "degraded",
latencyMs: Date.now() - start,
profileOk: profileRes.ok,
linkCount,
analyticsAvailable: analyticsRes.ok,
};
}
```
## Resources
- [Linktree Developer Docs](https://linktr.ee/marketplace/developer)
- [Linktree Status Page](https://status.linktr.ee)
- [Linktree API Changelog](https://developers.linktr.ee/changelog)
## Next Steps
See `linktree-rate-limits`.Related Skills
workhuman-debug-bundle
Workhuman debug bundle for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman debug bundle".
wispr-debug-bundle
Wispr Flow debug bundle for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr debug bundle".
webflow-debug-bundle
Collect Webflow debug evidence for support tickets and troubleshooting. Gathers SDK version, token validation, rate limit status, site connectivity, CMS health, and error logs into a single diagnostic bundle. Trigger with phrases like "webflow debug", "webflow support bundle", "collect webflow logs", "webflow diagnostic", "webflow troubleshoot".
vercel-debug-bundle
Collect Vercel debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Vercel problems. Trigger with phrases like "vercel debug", "vercel support bundle", "collect vercel logs", "vercel diagnostic".
veeva-debug-bundle
Veeva Vault debug bundle for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva debug bundle".
vastai-debug-bundle
Collect Vast.ai debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Vast.ai problems. Trigger with phrases like "vastai debug", "vastai support bundle", "collect vastai logs", "vastai diagnostic".
twinmind-debug-bundle
Collect comprehensive diagnostic information for TwinMind issues. Use when preparing support requests, investigating complex problems, or gathering evidence for bug reports. Trigger with phrases like "twinmind debug", "twinmind diagnostics", "collect twinmind info", "twinmind support bundle".
together-debug-bundle
Together AI debug bundle for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together debug bundle".
techsmith-debug-bundle
TechSmith debug bundle for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith debug bundle".
supabase-debug-bundle
Collect Supabase diagnostic info for troubleshooting and support tickets. Use when debugging connection failures, auth issues, Realtime drops, Storage errors, RLS misconfigurations, or preparing a support escalation. Trigger: "supabase debug", "supabase diagnostics", "supabase support bundle", "collect supabase logs", "debug supabase connection".
stackblitz-debug-bundle
Collect WebContainer diagnostic info: boot state, file system, process list. Use when working with WebContainers or StackBlitz SDK. Trigger: "stackblitz debug".
speak-debug-bundle
Collect diagnostic information for Speak API issues: auth verification, audio format validation, session inspection, and network testing. Use when implementing debug bundle features, or troubleshooting Speak language learning integration issues. Trigger with phrases like "speak debug bundle", "speak debug bundle".