Agent skill · software engineering · jeremylongshore
linktree-performance-tuning
Improve a Linktree visitor path with destination, mobile, content-order, and Insights evidence. Use when a profile is slow, confusing, or underperforming. Trigger with "optimize Linktree performance".
Why this skill is useful
Adds executable scripts for optimizing Linktree API performance through caching, batching, and rate limit handling that aren't in public docs.
What it needs
Requires node, redis installed locally. 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 Visitor-Path Performance Study Overview Optimize the complete visitor path rather than a fictional API: profile render, content hierarchy, link choice, redirect chain, destination experience, and measured outcome. 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 Linktree recommends considering visitor journey, content order, and focused link sets in its link guidance. Insights exposes views, clicks, click rate, sources, and plan-dependent detail for measurement. Destination latency and behavior belong to the destination owner and must be measured separately from Linktree. 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-performance-tuning--0ee0f0