Agent skill · data analytics · jeremylongshore

linktree-common-errors

Triage common Linktree publishing, login, destination, rendering, and Insights symptoms with bounded evidence. Use when an operator reports a Linktree problem. Trigger with "troubleshoot Linktree".

Why this skill is useful

Provides specific error handling patterns and API integration knowledge for Linktree that the AI wouldn't reliably generate on its own.

What it needs

Requires linktree account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Linktree Operator Troubleshooting Triage Overview Classify the failing layer before changing anything: account access, Linktree status, profile configuration, browser rendering, destination system, analytics delay, or private integration. Prerequisites An authorized Linktree account or a clearly bounded design-only task The profile, Workspace, destination, campaign, data, or integration owner appropriate to the requested change Current account evidence for plan-dependent features and user-supplied approved partner documentation for every private interface Tool Discipline Use Read, Glob, and Grep to inspect repository specifications, sanitized fixtures, policies, tests, and prior receipts. Use WebFetch only for current official Linktree documentation or explicitly approved partner documentation. Use Write or Edit only after confirming scope, target, owners, data classification, and approval state. These tools do not confer Linktree access, account authority, or permission to process visitor data. Return exact operator steps or an approval-gated handoff when a live action is not authorized. Current Contract A visible Linktree button and its destination are separate failure domains. Linktree documents account-login recovery and states that Insights data may not appear immediately. Private partner behavior cannot be diagnosed from invented public response codes or endpoints. Authentication For Admin work, use only the operator's individually provisioned Linktree account, documented Workspace role, and enabled MFA. Never request passwords, one-time codes, browser cookies, recovery codes, or session material. For partner automation, use only the authentication method, environment, scope, storage, rotation, and revocation process in the user-supplied approved partner contract. Public help pages do not establish a general API credential. Instructions 1. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/linktree-common-errors

View the source on GitHub

Browse the @skills marketplace