linktree-common-errors
Diagnose and fix Linktree common errors. Trigger: "linktree error", "fix linktree", "debug linktree".
What this skill does
# Linktree Common Errors
## Overview
Linktree's API manages link-in-bio profiles, individual links, appearance settings, and analytics. Common integration errors include URL validation failures when adding links with unsupported schemes, profile-not-found errors from incorrect username lookups, and analytics data lag that causes empty responses for recently created links. Analytics data lags 15-30 minutes behind real-time, which frequently causes confusion when verifying newly created links. This reference covers HTTP errors, link management issues, and analytics-specific quirks that affect Linktree API consumers.
## Error Reference
| Code | Message | Cause | Fix |
|------|---------|-------|-----|
| `400` | `Invalid URL format` | Link URL missing scheme or malformed | Ensure URLs include `https://` prefix and pass URL validation |
| `401` | `Authentication failed` | API key invalid or expired | Regenerate key at linktr.ee developer portal |
| `403` | `Plan feature restricted` | Endpoint requires Pro/Premium plan | Upgrade plan or use alternative endpoint for free tier |
| `404` | `Profile not found` | Username does not exist or is deactivated | Verify username spelling; check profile is active |
| `404` | `Link not found` | Link ID deleted or belongs to another profile | List links first to confirm valid IDs |
| `409` | `Duplicate link` | Same URL already exists on profile | Check existing links before adding; update instead of create |
| `422` | `Validation error` | Title too long or thumbnail URL invalid | Title max 100 chars; thumbnail must be valid image URL |
| `429` | `Rate limited` | Exceeded 100 requests/minute | Implement exponential backoff; check `Retry-After` header |
## Error Handler
```typescript
interface LinktreeError {
code: number;
message: string;
category: "auth" | "rate_limit" | "validation" | "not_found";
}
function classifyLinktreeError(status: number, body: string): LinktreeError {
if (status === 401 || status === 403) {
return { code: status, message: body, category: "auth" };
}
if (status === 429) {
return { code: 429, message: "Rate limited", category: "rate_limit" };
}
if (status === 404) {
return { code: 404, message: body, category: "not_found" };
}
return { code: status, message: body, category: "validation" };
}
```
## Debugging Guide
### Authentication Errors
Linktree API keys are passed via `Authorization: Bearer` header. Keys are scoped per account, not per profile. A 403 may indicate a plan-level restriction rather than a credentials issue -- verify the endpoint is available on your current plan tier before regenerating the key. Free-tier keys cannot access analytics or appearance customization endpoints.
### Rate Limit Errors
The API enforces 100 requests/minute per key. Batch link creation using array endpoints when available. Analytics endpoints have stricter limits (30/min). Use the `Retry-After` header value and implement exponential backoff starting at 1 second.
### Validation Errors
Link URLs must include the `https://` or `http://` scheme. Custom schemes (e.g., `mailto:`, `tel:`) are not supported via API. Titles are capped at 100 characters. Thumbnail URLs must resolve to valid image formats (PNG, JPG, GIF). Profile appearance updates fail silently if the theme ID does not exist -- validate theme availability first.
## Error Handling
| Scenario | Pattern | Recovery |
|----------|---------|----------|
| Link validation fails | URL missing scheme | Prepend `https://` and retry |
| Analytics returns empty | Data not yet available | Analytics lag 15-30 min; retry after delay |
| Profile lookup fails | Username typo or deactivated | Search by email if available; confirm active status |
| Duplicate link on create | Same URL already on profile | Fetch existing links, update instead of create |
| Bulk link import partial failure | Some URLs invalid | Parse error array, fix URLs, retry failed items |
## Quick Diagnostic
```bash
# Verify API connectivity and key validity
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $LINKTREE_API_KEY" \
https://api.linktr.ee/v1/profile
```
## Resources
- [Linktree Developer Docs](https://linktr.ee/marketplace/developer)
- [Linktree API Reference](https://developers.linktr.ee)
## Next Steps
See `linktree-debug-bundle`.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.