Agent skill · software engineering · jeremylongshore
linktree-ci-integration
Gate repository-managed Linktree campaign specifications with deterministic static and synthetic checks. Use when adding CI around profile content or an approved partner adapter. Trigger with "add Linktree CI".
Why this skill is useful
Adds a complete CI pipeline with executable scripts for testing Linktree API integrations, including mock and integration tests that aren't in public docs.
What it needs
Requires node 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 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 1. Define the protected specification format, owners, required reviews, destination policy, schedule format, and evidence retained by CI. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linktree-ci-integration