Agent skill · security · jeremylongshore
linktree-security-basics
Establish a Linktree security baseline for account access, Workspaces, destinations, audience data, and incident response. Use when hardening or reviewing a profile. Trigger with "secure Linktree".
Why this skill is useful
Adds executable scripts for secure Linktree API key management, webhook verification, and data protection that aren't in public docs.
What it needs
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 Account and Data Security Baseline Overview Reduce account takeover, malicious-link, overprivilege, and audience-data risks with documented controls and named owners. Produce a reproducible baseline that makes exceptions and remediation accountability visible. 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 documents MFA and new-login notifications as account-security controls. Workspaces and Admin users create access relationships that require lifecycle ownership. Audience, analytics, and destination systems can introduce personal-data and third-party risk beyond the profile itself. 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-security-basics