Agent skill · software engineering · jeremylongshore
linktree-upgrade-migration
Plan and verify a Linktree plan, profile, Workspace, username, or integration migration with preserved evidence and rollback. Use when account structure changes. Trigger with "migrate Linktree".
Why this skill is useful
Adds executable scripts for detecting Linktree API version and migrating link schemas that aren't in public docs.
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 Plan, Profile, and Workspace Migration Overview Inventory current state, classify plan-dependent and externally referenced assets, rehearse the change, and verify public and operator paths without assuming portability. 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 Plan capabilities, analytics history, profiles, and Workspace behavior must be verified against current official guidance and the target account. Public profile URLs, QR codes, social bios, campaign materials, and external destinations can create dependencies outside Linktree. Private partner integrations require contract-specific migration and credential evidence. 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-upgrade-migration