Agent skill · software engineering · jeremylongshore
linktree-core-workflow-a
Manage the planning, staging, publication, verification, and rollback of a Linktree campaign link using documented Admin controls. Use when shipping a time-bound campaign or content launch. Trigger with "publish Linktree campaign".
Why this skill is useful
Adds executable scripts for managing Linktree profiles and links via the Linktree API that are not available in public documentation.
What it needs
Requires @linktree/sdk, node 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 Governed Campaign Publish Overview Turn campaign intent into a controlled profile change with a destination owner, content review, placement rationale, schedule, acceptance checks, and rollback receipt. 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 Classic links and Link Apps have different visitor behavior and must be selected intentionally. Link ordering affects prominence, and Linktree documents scheduled links for time-bound availability. Public help guidance supports Admin operations, not an undocumented bulk-publish API. 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. Capture campaign owner, audience, approved copy, destination, link type, start and end time, timezone, placement, and rollback trigger. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linktree-core-workflow-a--4662f3