--- name: linktree-core-workflow-a-e5b35ba4de33 description: 'Manage the planning, staging, publication, verification, and rollback of a Linktree campaign link using documented Admin controls. Use when shipping a time-bound campaign or content launch. Trigger with "publish Linktree campaign".' argument-hint: "[profile] [campaign-id]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.8.0 author: Jeremy Longshore license: MIT tags: - saas - linktree - campaign - change-control - publishing 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 --- # 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 1. Capture campaign owner, audience, approved copy, destination, link type, start and end time, timezone, placement, and rollback trigger. 2. Use Read, Glob, and Grep to compare the campaign brief with the local destination registry and prior change receipts. 3. Validate the destination for HTTPS, expected host, consent and checkout behavior, accessibility, and mobile layout before changing Linktree. 4. Stage the link disabled or scheduled when the account supports it; obtain content and profile-owner approval on the exact preview. 5. Publish in the approved window, confirm order and public rendering, and test the destination without submitting real personal or payment data. 6. Use Write or Edit to record timestamps, operator, approval, evidence, and the exact rollback action. 7. Use WebFetch only for current official instructions on links, ordering, scheduling, or sharing. ## Approval Boundaries Do not publish early, silently replace a destination, or use a production checkout during verification. A schedule is not a substitute for human approval. ## Output Return campaign, profile, link type, schedule and timezone, placement, destination checks, approvals, public verification, rollback trigger, and final state. ## Error Handling | Condition | Response | |---|---| | Schedule timezone is ambiguous | Hold publication until the owner confirms an absolute time and timezone. | | Destination changes after approval | Invalidate the approval and repeat destination review. | | Rollback cannot be demonstrated | Do not publish until disable or removal is tested safely. | ## Example The example is a synthetic, redacted operator receipt, not proof of Linktree access or a live account change. ```text campaign=fall-launch; type=classic; window=approved-UTC; placement=2; mobile=pass; owner-approval=recorded; rollback=disable-link; state=live ``` ## Resources - [Official documentation map](references/official-docs.md) — dated evidence and limits for this workflow. 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 attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/linktree-pack/skills/linktree-core-workflow-a/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/linktree-pack/skills/linktree-core-workflow-a/SKILL.md Attribution basis: Source repository record Fields of work: Marketing Roles: Content Marketer, Influencer Marketer, Social Media Manager Specialties: API, Backend, Design, Excel, Frontend Tools: Linktree Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: fc14041f6ee97d9652c739c0f0f5fa403fe69d19cca6890c7789c50ffebaf420