Agent skill · software engineering · jeremylongshore
linktree-prod-checklist
Review and gate a Linktree profile, campaign, audience, commerce, or partner-integration change before production. Use when approving a release. Trigger with "Linktree production checklist".
Why this skill is useful
Adds a validation script and detailed production checklist for Linktree API integration that enhances reliability and security, which the AI wouldn't generate on its own.
What it needs
Requires typescript 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 Production Change Checklist Overview Issue a fail-closed go/no-go decision across ownership, access, content, destinations, data handling, testing, service status, monitoring, and rollback. 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 features and availability vary by plan, region, and current product state. Public UI workflows and private partner automation have different evidence and authorization requirements. Audience and commerce changes add privacy, consent, payment, and support responsibilities beyond link publishing. 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. Freeze change ID, reviewed revision, target profile and Workspace, operator, approver, window, scope, and excluded changes. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linktree-prod-checklist