Agent skill · data analytics · jeremylongshore
linktree-core-workflow-b
Turn documented Linktree Insights into a bounded content decision with comparable windows and a reversible experiment. Use when reviewing campaign performance. Trigger with "analyze Linktree Insights".
Why this skill is useful
Adds specific commands and workflows for extracting and analyzing Linktree analytics data that the AI wouldn't reliably generate on its own.
What it needs
Requires npm 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 Insights Decision Loop Overview Review views, clicks, click rate, sources, and individual-link performance without conflating correlation with attribution or manufacturing unavailable data. 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 defines total and unique views and clicks, click rate, subscribers, and sources in its Insights documentation. History, filters, visitor detail, and CSV exports vary by plan and feature availability. Linktree notes that an operator's own test clicks are included and may take time to appear. 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-core-workflow-b