linktree-deploy-integration
Deploy Integration for Linktree. Trigger: "linktree deploy integration".
Best use case
linktree-deploy-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deploy Integration for Linktree. Trigger: "linktree deploy integration".
Teams using linktree-deploy-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/linktree-deploy-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How linktree-deploy-integration Compares
| Feature / Agent | linktree-deploy-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deploy Integration for Linktree. Trigger: "linktree deploy integration".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Linktree Deploy Integration
## Overview
Deploy a containerized Linktree integration service that synchronizes profile data, manages link collections, and handles appearance customizations through the Linktree API. This skill covers Docker multi-stage builds optimized for the Linktree SDK, environment configuration for API authentication, health checks that verify Linktree API connectivity, and rolling deployment strategies with zero-downtime link management updates.
## Prerequisites
- Docker 24+ and Docker Compose v2 installed
- Valid `LINKTREE_API_KEY` from the Linktree developer portal
- Node.js 20 LTS (build stage)
- Network access to `api.linktr.ee` on port 443
- Target deployment host with at least 256MB available memory
## Docker Configuration
```dockerfile
FROM node:20-slim AS builder
WORKDIR /build
COPY package*.json tsconfig.json ./
RUN npm ci
COPY src/ ./src/
RUN npm run build
FROM node:20-slim
RUN groupadd -r linktree && useradd -r -g linktree -m appuser
WORKDIR /app
COPY --from=builder /build/dist ./dist/
COPY --from=builder /build/node_modules ./node_modules/
COPY package*.json ./
RUN npm prune --production
USER appuser
EXPOSE 3000
HEALTHCHECK --interval=30s --timeout=5s --retries=3 \
CMD curl -f http://localhost:3000/health || exit 1
CMD ["node", "dist/index.js"]
```
## Environment Variables
```bash
LINKTREE_API_KEY="lt_live_xxxxxxxxxxxxx" # Linktree API key from developer portal
LINKTREE_BASE_URL="https://api.linktr.ee" # API base URL
LINKTREE_PROFILE_ID="" # Target profile identifier
LOG_LEVEL="info" # debug | info | warn | error
NODE_ENV="production"
PORT="3000"
```
## Health Check Endpoint
```typescript
import express from "express";
const app = express();
app.get("/health", async (_req, res) => {
try {
const response = await fetch(`${process.env.LINKTREE_BASE_URL}/v1/profile`, {
headers: { Authorization: `Bearer ${process.env.LINKTREE_API_KEY}` },
});
if (!response.ok) throw new Error(`Linktree API returned ${response.status}`);
const profile = await response.json();
res.json({ status: "healthy", profile: profile.username, links: profile.links?.length ?? 0 });
} catch (err) {
res.status(503).json({ status: "unhealthy", error: (err as Error).message });
}
});
```
## Deployment Steps
### Step 1: Build Image
```bash
docker build -t linktree-integration:$(git rev-parse --short HEAD) .
```
### Step 2: Run Container
```bash
docker run -d --name linktree-svc \
--env-file .env.production \
-p 3000:3000 \
--restart unless-stopped \
linktree-integration:$(git rev-parse --short HEAD)
```
### Step 3: Verify Health
```bash
curl -s http://localhost:3000/health | jq .
# Expect: { "status": "healthy", "profile": "your-username", "links": 12 }
```
### Step 4: Rolling Update
```bash
docker pull linktree-integration:latest
docker stop linktree-svc && docker rm linktree-svc
docker run -d --name linktree-svc --env-file .env.production -p 3000:3000 linktree-integration:latest
```
## Rollback Procedure
```bash
# List recent images
docker images linktree-integration --format "{{.Tag}} {{.CreatedAt}}" | head -5
# Roll back to previous tag
docker stop linktree-svc && docker rm linktree-svc
docker run -d --name linktree-svc --env-file .env.production -p 3000:3000 linktree-integration:<previous-tag>
```
## Error Handling
| Issue | Cause | Fix |
|-------|-------|-----|
| 401 on health check | Expired or invalid `LINKTREE_API_KEY` | Rotate key in Linktree developer portal and update `.env` |
| Container OOM killed | Link sync processing large profile trees | Increase memory limit to 512MB with `--memory=512m` |
| ECONNREFUSED to API | DNS or firewall blocking `api.linktr.ee` | Verify outbound HTTPS access and DNS resolution |
| Health check timeout | Slow API response under rate limiting | Increase `HEALTHCHECK --timeout` to 10s and add retry backoff |
| Profile not found | Invalid `LINKTREE_PROFILE_ID` | Verify profile ID exists via `GET /v1/profile` manually |
## Resources
- [Linktree Developer Docs](https://linktr.ee/marketplace/developer)
## Next Steps
See `linktree-webhooks-events`.Related Skills
running-integration-tests
Execute integration tests validating component interactions and system integration. Use when performing specialized testing. Trigger with phrases like "run integration tests", "test integration", or "validate component interactions".
research-to-deploy
Researches infrastructure best practices and generates deployment-ready configurations, Terraform modules, Dockerfiles, and CI/CD pipelines. Use when the user needs to deploy services, set up infrastructure, or create cloud configurations based on current best practices. Trigger with phrases like "research and deploy", "set up Cloud Run", "create Terraform for", "deploy this to AWS", or "generate infrastructure configs".
workhuman-deploy-integration
Workhuman deploy integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman deploy integration".
workhuman-ci-integration
Workhuman ci integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman ci integration".
wispr-deploy-integration
Wispr Flow deploy integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr deploy integration".
wispr-ci-integration
Wispr Flow ci integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr ci integration".
windsurf-ci-integration
Integrate Windsurf Cascade workflows into CI/CD pipelines and team automation. Use when automating Cascade tasks in GitHub Actions, enforcing AI code quality gates, or setting up Windsurf config validation in CI. Trigger with phrases like "windsurf CI", "windsurf GitHub Actions", "windsurf automation", "cascade CI", "windsurf pipeline".
webflow-deploy-integration
Deploy Webflow-powered applications to Vercel, Fly.io, and Google Cloud Run with proper secrets management and Webflow-specific health checks. Trigger with phrases like "deploy webflow", "webflow Vercel", "webflow production deploy", "webflow Cloud Run", "webflow Fly.io".
webflow-ci-integration
Configure Webflow CI/CD with GitHub Actions — automated CMS validation, integration tests with test tokens, and publish-on-merge workflows. Use when setting up automated testing or CI pipelines for Webflow integrations. Trigger with phrases like "webflow CI", "webflow GitHub Actions", "webflow automated tests", "CI webflow", "webflow pipeline".
vercel-deploy-preview
Create and manage Vercel preview deployments for branches and pull requests. Use when deploying a preview for a pull request, testing changes before production, or sharing preview URLs with stakeholders. Trigger with phrases like "vercel deploy preview", "vercel preview URL", "create preview deployment", "vercel PR preview".
vercel-deploy-integration
Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies. Use when deploying to production, configuring deployment regions, or setting up blue-green deployment patterns on Vercel. Trigger with phrases like "deploy vercel", "vercel production deploy", "vercel promote", "vercel rollback", "vercel regions".
veeva-deploy-integration
Veeva Vault deploy integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva deploy integration".