Agent skill · software engineering · jeremylongshore
linktree-sdk-patterns
Design a testable adapter around an approved Linktree partner contract without claiming a public SDK or endpoint schema. Use when implementing authorized partner automation. Trigger with "design Linktree adapter".
Why this skill is useful
Adds a complete SDK implementation for Linktree with error handling, request building, and testing utilities that are not available in public documentation.
What it needs
Requires axios, 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 Partner-Contract Adapter Boundary Overview Translate user-supplied partner documentation into a narrow internal port, redacted fixtures, and contract tests while keeping undocumented behavior outside the implementation. 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 publicly invites developers to register interest for APIs and SDKs and sends existing partners to its Marketplace. That page does not establish package names, hosts, authentication, schemas, event types, quotas, or service guarantees. The signed partner contract and current partner portal evidence are authoritative for private automation. 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-sdk-patterns