linktree-ci-integration View full skill →

Gate repository-managed Linktree campaign specifications with deterministic static and synthetic checks.

ReadGlobGrepWebFetchWriteEdit

Linktree Content Change CI Gate

Overview

Turn profile and campaign policy into a fail-closed repository gate without logging in to Linktree or requiring production secrets in pull-request jobs.

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 Admin documentation can ground link-type, order, schedule, and visible-content expectations.
A CI job cannot prove a live profile state unless an approved, documented partner interface explicitly provides that evidence.
Fork and pull-request workflows must remain secretless and synthetic.

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

Define the protected specification format, owners, required reviews, destination policy, schedule format, and evidence retained by CI.
Use Read, Glob, and Grep to inspect workflow files, campaign fixtures, ownership rules, and existing tests.
Add static checks for schema, HTTPS destinations, host policy, duplicate identifiers, title limits defined by local policy, timezone presence, and rollback metadata.
Add synthetic rendering or adapter contract tests that do not contact Linktree and cannot consume production session material.
Make the gate fail closed on validation errors and report concise, redacted diagnostics suitable for untrusted pull requests.
Use Write or Edit to modify the workflow and tests after confirming branch-protection expectations and generated-file ownership.
Use WebFetch only to ve…

linktree-common-errors View full skill →

Triage common Linktree publishing, login, destination, rendering, and Insights symptoms with bounded evidence.

ReadGlobGrepWebFetchWriteEdit

Linktree Operator Troubleshooting Triage

Overview

Classify the failing layer before changing anything: account access, Linktree status, profile configuration, browser rendering, destination system, analytics delay, or private integration.

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

A visible Linktree button and its destination are separate failure domains.
Linktree documents account-login recovery and states that Insights data may not appear immediately.
Private partner behavior cannot be diagnosed from invented public response codes or endpoints.

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

Capture the exact symptom, profile URL, link title, expected result, first-seen time and timezone, affected audience, device class, and latest approved change.
Use Read, Glob, and Grep to inspect change receipts, destination inventory, browser evidence, and sanitized integration logs.
Check official service status, then reproduce signed out and distinguish missing or disabled content from a broken external destination.
For login symptoms, follow documented recovery and MFA guidance; never request a password, one-time code, or session cookie.
For Insights symptoms, verify metric definition, date range, plan availability, test traffic, and documented refresh behavior before declaring data loss.
Use Write or Edit to record the classification, evidence, one reversible next action, and escalation o…

linktree-core-workflow-a View full skill →

Manage the planning, staging, publication, verification, and rollback of a Linktree campaign link using documented Admin controls.

ReadGlobGrepWebFetchWriteEdit

Linktree Governed Campaign Publish

Overview

Turn campaign intent into a controlled profile change with a destination owner, content review, placement rationale, schedule, acceptance checks, and rollback receipt.

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

Classic links and Link Apps have different visitor behavior and must be selected intentionally.
Link ordering affects prominence, and Linktree documents scheduled links for time-bound availability.
Public help guidance supports Admin operations, not an undocumented bulk-publish API.

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

Capture campaign owner, audience, approved copy, destination, link type, start and end time, timezone, placement, and rollback trigger.
Use Read, Glob, and Grep to compare the campaign brief with the local destination registry and prior change receipts.
Validate the destination for HTTPS, expected host, consent and checkout behavior, accessibility, and mobile layout before changing Linktree.
Stage the link disabled or scheduled when the account supports it; obtain content and profile-owner approval on the exact preview.
Publish in the approved window, confirm order and public rendering, and test the destination without submitting real personal or payment data.
Use Write or Edit to record timestamps, operator, approval, evidence, and the exact rollback action.
Use WebFetch only for current official …

linktree-core-workflow-b View full skill →

Turn documented Linktree Insights into a bounded content decision with comparable windows and a reversible experiment.

ReadGlobGrepWebFetchWriteEdit

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

State the decision question, owner, primary metric, guardrail metric, comparison windows, campaign changes, and minimum useful observation period.
Use Read, Glob, and Grep to inspect the campaign log, prior baseline, and measurement plan before viewing results.
In Insights, set the documented date range and record definitions, plan limitations, visible filters, and any test traffic contamination.
Compare equivalent windows and inspect individual-link results and traffic sources; flag launches, outages, or promotions that make them non-comparable.
Choose one reversible content, order, title, or promotion experiment; define success and rollback before applying it.
Use Write or Edit to save a redacted decision receipt and raw-export provenance when an authorized CSV is available.
Use WebFetch …

linktree-cost-tuning View full skill →

Evaluate Linktree plan and feature value from current pricing, actual usage, and documented availability.

ReadGlobGrepWebFetchWriteEdit

Linktree Plan and Feature Value Review

Overview

Build a decision-ready plan review based on needed outcomes, active profiles, operator time, Insights history, and audience or commerce requirements rather than static copied prices.

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 pricing and feature availability can change and must be verified at decision time.
Insights history, filters, exports, and audience capabilities vary by plan according to current help guidance.
A feature's presence does not prove incremental value; actual usage and business outcomes are required.

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

Define the decision date, billing owner, current plan, profiles and Workspaces, renewal terms, required outcomes, and non-negotiable controls.
Use Read, Glob, and Grep to inspect approved invoices, plan inventory, usage receipts, campaign results, and operator-time estimates without exposing payment details.
Use WebFetch to capture current official pricing and help evidence on the review date; record region, billing cadence, tax assumptions, and feature caveats.
Map each used or requested feature to an owner, frequency, measurable outcome, alternative, and documented plan requirement.
Compare keep, upgrade, downgrade, and consolidate scenarios, including migration effort, lost history, access changes, and operational risk.
Use Write or Edit to produce a redacted…

linktree-debug-bundle View full skill →

Assemble a minimal, redacted Linktree troubleshooting bundle for support or incident handoff.

ReadGlobGrepWebFetchWriteEdit

Linktree Redacted Operator Evidence Bundle

Overview

Capture reproducible evidence across the public profile, Admin observation, destination, service status, and approved adapter without leaking sessions, subscribers, or private contracts.

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 status is the public source for platform incident context.
Browser-visible profile and destination behavior can be recorded without claiming access to Linktree internals.
Partner logs and contracts remain private and should be summarized or redacted according to their handling rules.

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

Record incident ID, reporter, symptom, first-seen time and timezone, affected profile, expected behavior, business impact, and current owner.
Use Read, Glob, and Grep to locate relevant change receipts, sanitized logs, fixtures, and destination ownership while excluding credentials and raw audience exports.
Capture Linktree service status, signed-out reproduction steps, device and browser class, link title, expected destination host, and observed redirect or error.
For approved partner automation, include contract revision, request correlation identifier, response class, and redacted timing only when permitted.
Remove tokens, cookies, email addresses, phone numbers, payment data, full query strings, private payloads, and unrelated profile information.
Use Write or Edit t…

linktree-deploy-integration View full skill →

Roll out an approved Linktree profile or campaign change through preview, bounded publication, verification, and rollback.

ReadGlobGrepWebFetchWriteEdit

Linktree Staged Profile Rollout

Overview

Coordinate a human-operated or contract-approved rollout with exact scope, evidence, monitoring, and a tested rollback instead of treating the profile as generic application infrastructure.

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 profile editing, scheduled links, sharing, and Insights through its product surfaces.
Feature and plan availability must be checked on the target account at deployment time.
Any automated deployment requires an approved partner contract; otherwise use documented Admin controls.

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

Freeze the reviewed change ID, profile, operator, approver, release window, expected public state, monitoring window, and rollback trigger.
Use Read, Glob, and Grep to verify the reviewed specification, destination evidence, synthetic test result, and prior profile snapshot.
Confirm Linktree service status and each destination's owner-approved readiness before the change window.
Apply only the reviewed delta through Admin controls or the explicitly approved partner adapter; do not bundle unrelated edits.
Verify signed-out mobile and desktop rendering, order, destinations, schedule, and relevant Insights baseline without submitting personal data.
Use Write or Edit to record the deployed revision, timestamps, evidence, observations, and rollback status.
Use WebFet…

linktree-hello-world View full skill →

Run the smallest documented Linktree publish-and-verify workflow without inventing an API.

ReadGlobGrepWebFetchWriteEdit

Linktree First-Publish Smoke Test

Overview

Prove one bounded path from an approved destination to a visible classic link, then verify the visitor experience on mobile and desktop before broader promotion.

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 classic links and Link Apps as separate experiences created from the Links area.
A classic link sends a visitor to the configured destination; an app can embed an experience on the profile.
The public developer page invites registration for broader API and SDK access; it is not a public automation specification.

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

Confirm the authorized account, profile URL, approved destination, owner, rollback action, and test window.
Inspect local campaign copy, destination inventory, and acceptance notes with Read, Glob, and Grep; do not search credential files.
In Linktree Admin, add one classic link with an unambiguous title and the approved destination, leaving unrelated links unchanged.
Open the public profile in a signed-out mobile viewport and desktop viewport; confirm title, placement, destination, HTTPS, and expected redirect chain.
Exercise one safe failure path with a deliberately unpublished draft or a nonproduction destination, then confirm visitors cannot reach it.
Use Write or Edit to record a redacted receipt containing timestamps, expected and actual destination hosts, and…

linktree-install-auth View full skill →

Establish Linktree account, workspace, role, MFA, and recovery readiness without fabricating developer credentials.

ReadGlobGrepWebFetchWriteEdit

Linktree Account and Access Readiness

Overview

Create an evidence-backed access plan for a Linktree profile or Workspace, keeping human Admin access separate from any approved partner integration credentials.

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 through SMS in listed regions or an authenticator application.
Workspaces are the documented surface for managing Linktrees and team access; available controls can vary by plan.
Developer access is program-gated, so a Linktree login is not evidence of an automation credential or API grant.

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

Identify the profile owner, Workspace, requested duties, approver, recovery contact, and offboarding owner.
Use Read, Glob, and Grep to inspect local access policy, role matrix, and existing integration inventory without opening secrets.
Choose the least-privileged documented Workspace role that satisfies the duties; avoid shared accounts.
Enable and verify an available MFA method, record recovery ownership, and confirm new-login notifications reach the accountable owner.
If partner automation is requested, require the approved partner agreement, credential issuance record, environment, scopes, rotation path, and revocation test before design work.
Use Write or Edit to record the access decision and a redacted joiner/mover/leaver receipt.
Use WebFetch only to verify curre…

linktree-local-dev-loop View full skill →

Rehearse Linktree-related changes locally with synthetic profile fixtures and destination checks before touching an account.

ReadGlobGrepWebFetchWriteEdit

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

Choose one change and define acceptance checks for titles, destination hosts, order, schedule metadata, mobile rendering assumptions, and rollback.
Use Read, Glob, and Grep to locate sanitized profile fixtures, the destination allowlist, adapter boundary, and current tests.
Create or update synthetic fixtures with fake identifiers and non-sensitive example destinations; label every modeled field with its authority source.
Run deterministic checks for malformed URLs, disallowed hosts, duplicate campaign IDs, inaccessible labels, expired schedules, and missing owners.
Exercise success, validation failure, authorization failure at the adapter seam, and rollback without connecting to a Linktree account.
Use Write or Edit to update fixtures, tests, or the rehearsal receipt after the l…

linktree-performance-tuning View full skill →

Improve a Linktree visitor path with destination, mobile, content-order, and Insights evidence.

ReadGlobGrepWebFetchWriteEdit

Linktree Visitor-Path Performance Study

Overview

Optimize the complete visitor path rather than a fictional API: profile render, content hierarchy, link choice, redirect chain, destination experience, and measured outcome.

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 recommends considering visitor journey, content order, and focused link sets in its link guidance.
Insights exposes views, clicks, click rate, sources, and plan-dependent detail for measurement.
Destination latency and behavior belong to the destination owner and must be measured separately from Linktree.

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

Define the visitor goal, target segment, profile, priority link, baseline window, primary metric, guardrail, owner, and rollback threshold.
Use Read, Glob, and Grep to inspect the current content inventory, destination owners, campaign history, and prior Insights decisions.
Test signed-out mobile and desktop paths, recording visible hierarchy, broken assets, redirect hops, destination readiness, accessibility blockers, and confusing labels.
Use the documented Insights definitions and comparable windows to locate drop-off signals without asserting causation.
Choose one reversible change to title, order, link type, destination, or profile presentation; keep other variables stable.
Use Write or Edit to record the hypothesis, exact change, baseline, review window, resu…

linktree-prod-checklist View full skill →

Review and gate a Linktree profile, campaign, audience, commerce, or partner-integration change before production.

ReadGlobGrepWebFetchWriteEdit

Linktree Production Change Checklist

Overview

Issue a fail-closed go/no-go decision across ownership, access, content, destinations, data handling, testing, service status, monitoring, and rollback.

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 features and availability vary by plan, region, and current product state.
Public UI workflows and private partner automation have different evidence and authorization requirements.
Audience and commerce changes add privacy, consent, payment, and support responsibilities beyond link publishing.

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

Freeze change ID, reviewed revision, target profile and Workspace, operator, approver, window, scope, and excluded changes.
Use Read, Glob, and Grep to verify acceptance evidence, destination approvals, access review, synthetic tests, data-impact review, monitoring, and rollback receipt.
Confirm required plan and region features on the target account and Linktree service status near the window.
Verify signed-out mobile and desktop behavior, accessibility, content approval, destination ownership, schedule timezone, and sharing preview.
For audience, commerce, or partner automation, verify consent, terms, data minimization, retention, deletion, private-contract revision, and support ownership.
Use Write or Edit to produce a signed checklist with explicit pass, fail, not applicable, and evidence for ev…

linktree-rate-limits View full skill →

Build backpressure and capacity controls from an approved Linktree partner contract without publishing guessed quotas.

ReadGlobGrepWebFetchWriteEdit

Linktree Contract-Grounded Capacity Control

Overview

Convert documented limits and observed behavior into conservative client controls, while treating every undocumented quota or reset rule as unknown.

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's public developer page does not state request quotas, concurrency limits, retry semantics, or headers.
Only current partner documentation and vendor-confirmed environment evidence can authorize numeric automation limits.
Public Admin workflows remain human-paced and are not a basis for deriving machine throughput.

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

Define the workload, environment, business deadline, maximum staleness, owner, and acceptable partial-progress behavior.
Use Read, Glob, and Grep to inspect the approved contract, workload model, adapter, telemetry fields, and synthetic tests.
Extract only documented limits, concurrency rules, response signals, retry guidance, and support escalation paths into an evidence table.
Design bounded queues, idempotent work units, jittered backoff only where the contract permits it, circuit breaking, and a manual pause control.
Use synthetic responses to test saturation, unknown limit signals, prolonged outage, cancellation, replay, and recovery without contacting Linktree.
Use Write or Edit to record configuration and tests; keep numeric production settings outside this public …

linktree-reference-architecture View full skill →

Define ownership and trust boundaries across Linktree Admin, public profiles, destinations, analytics exports, and private partner automation.

ReadGlobGrepWebFetchWriteEdit

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

Inventory actors, profiles, Workspaces, destinations, audience flows, analytics consumers, partner integrations, data classes, and business owners.
Use Read, Glob, and Grep to trace repository specifications, adapters, scheduled jobs, data stores, ownership files, and incident runbooks.
Label every edge as documented public UI, browser redirect, approved export, user-supplied partner contract, or unsupported assumption.
For each boundary, record authentication, authorization, data minimization, retention, deletion, availability, reconciliation, and rollback ownership.
Model signed-out visitor, editor, Workspace administrator, analytics operator, destination owner, and partner-service failure paths using synthetic identifiers.
Use Write or Edit to create the architecture re…

linktree-sdk-patterns View full skill →

Design a testable adapter around an approved Linktree partner contract without claiming a public SDK or endpoint schema.

ReadGlobGrepWebFetchWriteEdit

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

Verify the approved partner relationship, contract revision, environment, integration owner, data classification, and permitted use cases.
Use Read, Glob, and Grep to inspect only the supplied contract, existing adapter, redacted fixtures, and tests; do not read credential values.
Create a contract table for each authorized operation: input, output, authentication method, scope, idempotency, pagination, error model, and evidence citation.
Define a vendor-neutral internal port that exposes only required operations and keeps transport objects behind the adapter.
Build synthetic contract fixtures for success, authorization failure, validation failure, throttling behavior if documented, and unknown responses.
Use Write or Edit fo…

linktree-security-basics View full skill →

Establish a Linktree security baseline for account access, Workspaces, destinations, audience data, and incident response.

ReadGlobGrepWebFetchWriteEdit

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

Identify account and Workspace owners, editors, recovery contacts, connected services, destination owners, data exports, and incident responders.
Use Read, Glob, and Grep to inspect access policy, approved destination list, integration inventory, retention rules, and prior incidents without reading secret values.
Verify individual accounts, least privilege, MFA, recovery ownership, new-login alert routing, and a tested offboarding process.
Review every live destination for approved ownership, HTTPS, expected redirect behavior, and removal procedure; quarantine unexplained links.
Minimize audience exports and third-party integrations; document consent, purpose, storage, retention, deletion, and breach escalation.
Use Write or Edit to record a r…

linktree-upgrade-migration View full skill →

Plan and verify a Linktree plan, profile, Workspace, username, or integration migration with preserved evidence and rollback.

ReadGlobGrepWebFetchWriteEdit

Linktree Plan, Profile, and Workspace Migration

Overview

Inventory current state, classify plan-dependent and externally referenced assets, rehearse the change, and verify public and operator paths without assuming portability.

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

Plan capabilities, analytics history, profiles, and Workspace behavior must be verified against current official guidance and the target account.
Public profile URLs, QR codes, social bios, campaign materials, and external destinations can create dependencies outside Linktree.
Private partner integrations require contract-specific migration and credential 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

Define migration type, source and target state, profile and Workspace owners, billing owner, window, success criteria, freeze point, and rollback deadline.
Use Read, Glob, and Grep to inventory profiles, live links, schedules, QR assets, social placements, sharing previews, exports, users, integrations, and change history.
Use WebFetch to verify current official plan, Workspace, URL, QR, Insights export, and relevant feature behavior on the evidence date.
Classify every asset as preserved, recreated, redirected, exported, owner-notified, unsupported, or blocked; minimize personal-data movement.
Rehearse with synthetic fixtures and a written sequence, including access loss, stale social bio, broken QR, destination fail…

linktree-webhooks-events View full skill →

Review an approved Linktree partner event mechanism or choose a documented export and polling alternative without inventing webhooks.

ReadGlobGrepWebFetchWriteEdit

Linktree Partner Event Contract Review

Overview

Establish whether an authorized event contract actually exists, then design validation, replay, ordering, reconciliation, and fallback from evidence rather than generic webhook conventions.

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 developer page announces program-gated APIs and SDKs but publishes no general event catalog or verification scheme.
Linktree documents on-screen Insights and plan-dependent CSV exports as public data-access paths.
Event delivery details are private-contract facts and must not be inferred from another provider.

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

Name the synchronization objective, data owner, consumer, freshness requirement, data classification, and reconciliation authority.
Use Read, Glob, and Grep to inspect the supplied partner contract, event fixtures, consumer code, and export workflow without reading secrets.
If an approved event mechanism exists, build an evidence table for event names, schema revision, authentication, replay protection, ordering, retries, retention, and acknowledgment behavior.
If it does not exist, choose the least-privileged documented alternative: operator review, authorized Insights CSV, or a contract-approved polling operation.
Test synthetic duplicates, out-of-order delivery, unknown fields, stale exports, consumer failure, and reconciliation.
Use Write …

linktree-pack

Installation

What It Does

Skills (18) plugin-local skills

Linktree Content Change CI Gate

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Operator Troubleshooting Triage

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Governed Campaign Publish

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Insights Decision Loop

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Plan and Feature Value Review

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Redacted Operator Evidence Bundle

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Staged Profile Rollout

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree First-Publish Smoke Test

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Account and Access Readiness

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Synthetic Integration Rehearsal

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication

Instructions

Linktree Visitor-Path Performance Study

Overview

Prerequisites

Tool Discipline

Current Contract

Authentication