Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/linktree-install-auth

@820dfc8
Run it yourself

Establish Linktree account, workspace, role, MFA, and recovery readiness without fabricating developer credentials. Use when onboarding an operator or integration owner. Trigger with "set up Linktree access".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/linktree-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈58 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈474 more on demand in 1 file.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈232 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

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

Approval Boundaries

Do not invite a user, change ownership, weaken MFA, or issue partner credentials until the named account or Workspace owner approves the role and recovery plan.

Output

Return account class, Workspace, role, MFA state, recovery owner, partner-contract state, revocation test, unresolved access gaps, and approval decision.

Error Handling

Condition Response
MFA cannot be enabled Do not treat password-only access as production-ready; escalate with the account owner.
Requested role is broader than duties Reduce the role or document an explicit, time-bounded exception.
API access is assumed from an Admin login Reject the assumption and obtain partner-program evidence.

Example

The example is a synthetic, redacted operator receipt, not proof of Linktree access or a live account change.

workspace=brand-main; role=editor; mfa=authenticator-verified; recovery=security-owner; partner-contract=none; revocation=tested; decision=ready

Resources

Read the map before acting. Recheck current account and partner-specific evidence for plan-dependent or private behavior.

Next Steps

Revalidate source dates, owner approval, target profile, and rollback readiness before repeating the workflow in another account, Workspace, campaign, region, plan, or integration.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill facilitates the installation and authentication setup for the Linktree SDK. It uses standard package managers and follows best practices for secret management using environment variables.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[workspace] [operator-role]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "linktree",
  "access",
  "mfa",
  "workspaces"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code; live work requires an authorized Linktree account and approval from the profile, Workspace, data, or partner-integration owner

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/linktree-install-auth