Agent skill · software engineering · jeremylongshore
linktree-local-dev-loop
Rehearse Linktree-related changes locally with synthetic profile fixtures and destination checks before touching an account. Use when developing campaign tooling or a partner adapter. Trigger with "rehearse Linktree change".
Why this skill is useful
Adds a local development workflow with mock API responses and integration patterns specific to Linktree that the AI wouldn't reliably generate on its own.
What it needs
Requires @types/express, @types/node, axios, dotenv, express, supertest, tsx, typescript, vitest 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 Synthetic Integration Rehearsal Overview Provide a fast local loop for content and integration work using sanitized fixtures, deterministic validations, and no assumption of a public Linktree sandbox. 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 Public Linktree help defines the visible link and profile behaviors that synthetic fixtures may model. The public developer page does not promise a sandbox or publish a general automation contract. Partner-specific behavior must be derived from the approved contract and kept separate from public UI expectations. 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-local-dev-loop