Agent skill · software engineering · jeremylongshore
linktree-reference-architecture
Define ownership and trust boundaries across Linktree Admin, public profiles, destinations, analytics exports, and private partner automation. Use when reviewing a Linktree system design. Trigger with "architect Linktree integration".
Why this skill is useful
Adds a complete executable architecture for integrating with Linktree, including caching strategies and event handling that aren't in public docs.
What it needs
Requires node, postgresql, rabbitmq, redis 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 Integration Authority Architecture Overview Produce a repo-grounded architecture that distinguishes Linktree-owned public behavior, account-owner decisions, destination systems, approved exports, and contract-private interfaces. 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 The public profile and Linktree Admin are documented product surfaces; destinations remain independently owned systems. Insights and audience exports have plan, privacy, and handling constraints. Partner APIs and SDKs are program-gated, so private interface details require contract 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-reference-architecture--6e9088