Agent skill · software engineering · jeremylongshore
linktree-hello-world
Run the smallest documented Linktree publish-and-verify workflow without inventing an API. Use when launching a profile or proving a new Linktree setup. Trigger with "smoke test Linktree".
Why this skill is useful
Provides specific API commands and error handling for Linktree that the AI wouldn't generate on its own.
What it needs
Requires npm 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 First-Publish Smoke Test Overview Prove one bounded path from an approved destination to a visible classic link, then verify the visitor experience on mobile and desktop before broader promotion. 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 documents classic links and Link Apps as separate experiences created from the Links area. A classic link sends a visitor to the configured destination; an app can embed an experience on the profile. The public developer page invites registration for broader API and SDK access; it is not a public automation specification. 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-hello-world