@link.me/cli-darwin-x64 0.3.1 → 0.4.2

package/skills/linkme-polish-profile/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: linkme-polish-profile
+description: Audit and improve a Linkme public profile. Use when a user wants stronger positioning, featured or social links, gallery, theme or custom fonts, link style, sections, contact details, vCard, age gate, forms, events, video, or conversion-focused profile changes.
+---
+
+# Polish a Profile
+
+Improve the public profile as a coherent visitor journey. Preserve identity fields unless the user explicitly wants a rename or rebrand.
+
+Prefer connected Linkme MCP tools. Their names mirror CLI paths with underscores; use the shell commands below as fallback and discovery examples.
+
+## Audit before editing
+
+Read the current surface with structured output:
+
+```bash
+linkme profile --json
+linkme featured list --json
+linkme links list --json
+linkme gallery list --json
+linkme profile sections list --json
+linkme profile contact list --json
+linkme profile link-style --json
+linkme profile age-gate --json
+```
+
+Identify the intended audience and primary conversion goal. Then propose a short, prioritized change set instead of changing every available setting.
+
+## Apply high-impact changes
+
+Work in this order:
+
+1. Clarify the bio and profile image with `linkme profile edit`.
+2. Put the primary calls to action in `linkme featured`.
+3. Correct supporting links and social links in `linkme links`.
+4. Add visual proof through `linkme gallery`.
+5. Align `linkme profile theme` and `linkme profile link-style` with the existing brand.
+6. Add a conversion module only when it serves the goal: contact info, vCard, form, event, shop, or profile video.
+7. Configure `linkme profile age-gate` only when the user has an actual age-restriction requirement.
+8. Enable and reorder sections after their content exists.
+
+Discover exact mutation flags with the narrowest help command, for example:
+
+```bash
+linkme featured add --help
+linkme links set --help
+linkme profile forms create --help
+linkme profile events add --help
+linkme profile sections move --help
+linkme profile theme --help
+linkme profile vcard --help
+```
+
+## Useful patterns
+
+Update positioning without renaming:
+
+```bash
+linkme profile edit \
+  --bio "Tour dates, music drops, merch, and fan links in one place." \
+  --image ./avatar.jpg \
+  --public-search
+```
+
+Set direct contact paths:
+
+```bash
+linkme profile contact set email bookings@example.com
+linkme profile contact set website https://example.com
+```
+
+Structure the public page:
+
+```bash
+linkme profile sections enable featured_links
+linkme profile sections enable contact_info
+linkme profile sections move featured_links 1
+linkme profile sections move contact_info 2
+```
+
+## Verify
+
+Re-read every area changed and compare it with the proposed outcome. Report:
+
+- what changed
+- the resulting order or visibility
+- anything skipped because content, media, plan access, or approval was missing
+
+## Guardrails
+
+- Do not change username, display name, email, tracking pixels, public-search visibility, or age-gate policy without a clear user request.
+- Read before deleting, reordering, or replacing media.
+- Do not fill forms, events, or contact fields with invented business details.
+- Chat, shouts, and notifications are outside this skill. A visible section key is not authorization to create or manage its content.
+- Use `$linkme-manage-media` for upload constraints and `$linkme-review-analytics` to measure impact.

package/skills/linkme-polish-profile/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Polish Linkme Profile"
+  short_description: "Audit and improve a Linkme profile"
+  default_prompt: "Use $linkme-polish-profile to audit my profile and propose the highest-impact improvements."

package/skills/linkme-publish-content/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: linkme-publish-content
+description: Draft, schedule, publish, and monitor video, image, carousel, or text posts across Linkme AP social accounts. Use when a user wants to post media or text, reuse an uploaded media key, inspect target status, retry, reschedule, or cancel a post.
+---
+
+# Publish Content
+
+Use Linkme AP to publish video, image, carousel, or text posts to connected social accounts. Treat `ap post create` as an external side effect because an unscheduled post can be queued immediately. Prepare and show the intended parameters first; invoke it only when the user requested publication or approved the exact targets and timing.
+
+Prefer connected Linkme MCP tools. Their names mirror CLI paths with underscores; use the shell commands below as fallback and discovery examples.
+
+## Choose the media path
+
+- Local CLI video: pass a local video to `linkme ap post create --video ./clip.mp4`, or upload once with `linkme ap upload ./clip.mp4` and reuse the returned AP key.
+- Image: use `--image ./photo.jpg` or `--format image --upload-asset-id <id>`. AP accepts JPEG, PNG, WebP, GIF, AVIF, HEIC, and HEIF up to 8 MiB and normalizes to still JPEG. Images need finalized asset IDs, not bare R2 keys.
+- Carousel: repeat `--media` in order, using files or `asset:<id>` references. It requires distinct assets: 2–10 on Instagram/Facebook, 2–20 on Threads/LinkedIn, 2–35 on TikTok, 2–4 on X. Only Instagram and Threads accept video items.
+- Text: use `--format text --caption "..." --platforms threads,x`, with no media. Facebook, X, Threads, and LinkedIn support text. Images/carousels additionally support Instagram and TikTok; YouTube remains video-only.
+- Media captions are optional; text needs a nonblank caption.
+- Hosted MCP: call `linkme_capabilities` and inspect the tool schema. Use `video`, `image`, or ordered `media` file inputs, their allowlisted URL alternatives, or platform references. `imageReference` takes `asset:<id>`; `mediaReference` takes an ordered array of those references. `uploadAssetId` plus `format: "image"` also works. For mixed sources, upload each new file with `ap_upload`, then create using all asset IDs. Do not send local paths.
+- Do not infer that an HTTPS URL is uploadable. Use only the file/reference fields exposed by the selected tool schema.
+
+## Prepare
+
+Inspect connected accounts:
+
+```bash
+linkme ap accounts --json
+```
+
+If the requested provider is missing, start its connection flow with `linkme ap connect <provider>` and return the authorization step to the user.
+
+Confirm:
+
+- target providers and account availability
+- caption and provider-specific title/privacy fields
+- immediate versus scheduled publication
+- schedule timestamp and timezone
+- post format and ordered media sources (none for text)
+
+## Create and verify
+
+Create from a local file:
+
+```bash
+linkme ap post create \
+  --video ./clip.mp4 \
+  --caption "New drop. Out now." \
+  --platforms youtube,tiktok,instagram
+```
+
+Create from an existing AP key:
+
+```bash
+linkme ap post create \
+  --video u/42/my-video \
+  --caption "Tonight at 8." \
+  --platforms youtube,tiktok \
+  --schedule 2026-04-23T20:00:00Z
+```
+
+Use `--json` for structured handoff and retain the returned post id. Immediately inspect it:
+
+```bash
+linkme ap post status <post-id> --json
+```
+
+Report per-target state and errors. A created post is not proof that every provider published it.
+
+## Operate an existing post
+
+- Wait through processing: `linkme ap post watch <post-id>`
+- Publish now: `linkme ap post publish <post-id>`
+- Cancel: `linkme ap post cancel <post-id>`
+- Retry failed targets: `linkme ap post retry <post-id>`
+- Change schedule: `linkme ap post reschedule <post-id> --help`
+- Review one target's results: `linkme ap post insights <post-id> <target-id>`
+- Review one target's comments: `linkme ap post comments <post-id> <target-id>`
+
+Re-read status after every publish, retry, cancel, or schedule change.
+
+## Guardrails
+
+- Never invent an AP object key or platform id.
+- Never report success from a zero exit code alone; verify target states.
+- Surface platform-specific failures instead of flattening them into a single post status.
+- If the user did not authorize publication, stop before `ap post create` and present the exact command or tool inputs that would be used.

package/skills/linkme-publish-content/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Publish Linkme Content"
+  short_description: "Publish and monitor social posts"
+  default_prompt: "Use $linkme-publish-content to prepare this post for my connected social accounts."

package/skills/linkme-recover-auth/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: linkme-recover-auth
+description: Establish or recover Linkme authentication for an agent, local CLI, or hosted MCP connection. Use for login, expired sessions, wrong-profile problems, manual browser auth, session revocation, connector reconnection, or missing credentials.
+---
+
+# Recover Authentication
+
+Diagnose the runtime before changing credentials. Keep tokens and passwords out of prompts, command output, logs, and committed files.
+
+Use the host connection for hosted MCP and the `linkme` commands below only for a local CLI installation.
+
+## Verify identity
+
+For the local CLI:
+
+```bash
+linkme whoami --json
+```
+
+If the identity is correct, do not reauthenticate. If the wrong local profile is active, inspect and switch:
+
+```bash
+linkme auth switch
+linkme whoami --json
+```
+
+## Local CLI login
+
+Prefer the manual browser flow for agents:
+
+```bash
+linkme auth login --manual
+```
+
+Give the printed authorization URL to the user. After they approve it:
+
+```bash
+linkme auth resume
+linkme whoami --json
+```
+
+If pending state is missing or expired, start a new manual flow. Do not guess or reconstruct its state.
+
+For CI, accept `LINKME_TOKEN` through the environment. Do not persist, print, or pass the token as a command-line argument.
+
+## Hosted MCP login
+
+Hosted MCP authenticates through the host's Linkme connector. Local-only tools such as login, logout, resume, config mutation, and profile switching are intentionally unavailable.
+
+If hosted authentication expires or points at the wrong account:
+
+1. stop the mutation
+2. ask the user to reconnect or change the Linkme connection in the host
+3. retry a read-only identity or resource call
+4. continue only after the expected account is confirmed
+
+## Session safety
+
+Inspect active local sessions with:
+
+```bash
+linkme auth sessions --json
+```
+
+Revoke only the session id the user identified:
+
+```bash
+linkme auth sessions revoke <session-id>
+```
+
+Re-run the session list and verify the target disappeared.
+
+## Boundaries
+
+- The CLI does not provide password-reset or account-recovery administration. Route those cases to Linkme's supported account recovery flow.
+- Never ask the user to paste a bearer or refresh token into chat.
+- Never log signed connector URLs or authorization codes.
+- Do not log out, revoke a session, or switch profiles merely to test authentication.

package/skills/linkme-recover-auth/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Recover Linkme Authentication"
+  short_description: "Recover Linkme agent authentication"
+  default_prompt: "Use $linkme-recover-auth to diagnose why this Linkme connection is not authenticated."

package/skills/linkme-review-analytics/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: linkme-review-analytics
+description: Analyze Linkme profile traffic, link performance, and audience demographics. Use for date-range reports, visits, clicks, CTR, referrers, devices, geography, age or gender breakdowns, realtime activity, local exports, period comparisons, or deciding what profile content to improve.
+---
+
+# Review Analytics
+
+Turn Linkme analytics into an evidence-based summary. Use explicit date ranges for repeatable reports.
+
+Prefer connected Linkme MCP tools. Their names mirror CLI paths with underscores; use the shell commands below as fallback and discovery examples.
+
+## Collect the relevant views
+
+```bash
+linkme analytics overview --from YYYY-MM-DD --to YYYY-MM-DD --json
+linkme analytics visits --from YYYY-MM-DD --to YYYY-MM-DD --json
+linkme analytics links --from YYYY-MM-DD --to YYYY-MM-DD --sort clicks --json
+linkme analytics geo --from YYYY-MM-DD --to YYYY-MM-DD --json
+linkme analytics audience --from YYYY-MM-DD --to YYYY-MM-DD --json
+```
+
+Use `linkme analytics realtime --json` only for current activity; do not mix it into a historical period total.
+
+Select the smallest useful set:
+
+- overview for visits, unique visitors, clicks, and CTR
+- visits for sources, devices, and referrers
+- links for destination performance and click share
+- geo for countries and cities
+- audience for historical age and gender distributions
+- realtime for current active visitors
+
+Use `analytics export` only when the user wants a local JSON artifact:
+
+```bash
+linkme analytics export \
+  --dataset audience \
+  --output ./audience.json \
+  --from YYYY-MM-DD \
+  --to YYYY-MM-DD
+```
+
+`analytics export` writes to the local filesystem, asks before create or
+overwrite, and is not available on hosted MCP. In a hosted session, return the
+structured result from `analytics audience` or another read instead.
+
+## Compare periods
+
+Run each required command twice with equal-length, non-overlapping date windows. Label both windows explicitly. Calculate:
+
+```text
+absolute change = current - previous
+percent change = (current - previous) / previous * 100
+```
+
+When the previous value is zero, report the absolute change and mark percentage change as undefined instead of dividing by zero.
+
+## Interpret carefully
+
+- Report totals and rates with their denominators.
+- Separate observations from hypotheses.
+- Do not infer causation from a traffic or click correlation.
+- Call out incomplete ranges, low counts, missing values, and timezone ambiguity.
+- Treat demographic buckets as aggregate estimates; do not identify or infer traits about an individual visitor.
+- Connect findings to a concrete profile action only when the data supports it.
+
+## Deliver
+
+Summarize:
+
+1. date range and comparison range
+2. visits, unique visitors, clicks, and CTR
+3. strongest and weakest links
+4. meaningful source, device, or geographic changes
+5. up to three recommended actions
+
+Keep raw JSON available for handoff, but present the user-facing result in plain language.

package/skills/linkme-review-analytics/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Review Linkme Analytics"
+  short_description: "Analyze Linkme traffic and audiences"
+  default_prompt: "Use $linkme-review-analytics to compare my Linkme performance across these date ranges."

package/skills/agents/codex/SKILL.md

@@ -1,14 +0,0 @@
----
-name: linkme_cli_codex
-description: Use the Linkme CLI from Codex to manage profile content, links, AP publishing, analytics, automations, email, forms, gallery, and commerce workflows.
----
-
-# Linkme CLI for Codex
-
-See the canonical **`agents/cli`** skill (`linkme_cli`) for install, authentication, output contracts (`--json`/`--quiet`/human), and the full command-area reference. This file only covers what's specific to running the CLI from Codex.
-
-## Codex Specifics
-
-- Codex sandboxes commonly restrict network access by default. Installing `@link.me/cli` via `npm install -g` and any `linkme` command that talks to the Linkme API requires network approval — request it explicitly rather than assuming it is already granted.
-- Prefer non-interactive flags over prompts: use `linkme auth login --manual` + `linkme auth resume` instead of the default interactive browser flow, and use `--json`/`--quiet` instead of relying on TTY-formatted human output.
-- Codex does not have a bundled MCP integration for this CLI — always invoke `linkme` as a subprocess.

package/skills/ap/create-post/SKILL.md

@@ -1,134 +0,0 @@
----
-name: linkme_ap_create_post
-description: Create and publish a Post on All (AP) post with the Linkme CLI. Use when the user wants to upload one short-form video, target connected social platforms, check processing or publish status, or wait until publishing completes.
----
-
-# AP Create Post
-
-## When To Use
-
-Use this skill when the user wants to publish one video across AP-connected platforms such as YouTube, TikTok, Instagram, Facebook, X, Threads, LinkedIn, or Snapchat.
-
-## Preconditions
-
-- The user must already be authenticated with `linkme`.
-- At least one AP provider account must be connected.
-
-Check connected accounts first:
-
-```bash
-linkme ap accounts
-```
-
-If no account is connected, connect one provider at a time:
-
-```bash
-linkme ap connect youtube
-linkme ap connect instagram
-linkme ap connect tiktok
-```
-
-## Core Workflow
-
-### 1. Upload the video if needed
-
-If the user has a local file, upload it and capture the returned R2 key:
-
-```bash
-linkme ap upload ./clip.mp4
-```
-
-The upload command prints a reusable AP video key like `u/42/my-video`.
-
-Skip this step if the user already has an AP R2 key.
-
-### 2. Create the AP post
-
-Create the post with either a local file path or an existing AP R2 key:
-
-```bash
-linkme ap post create \
-  --video ./clip.mp4 \
-  --caption "New drop. Out now." \
-  --platforms youtube,tiktok,instagram
-```
-
-Or with an uploaded key:
-
-```bash
-linkme ap post create \
-  --video u/42/my-video \
-  --caption "New drop. Out now." \
-  --platforms youtube,tiktok,instagram
-```
-
-Optional scheduling:
-
-```bash
-linkme ap post create \
-  --video u/42/my-video \
-  --caption "Tonight at 8." \
-  --platforms youtube,tiktok \
-  --schedule 2026-04-23T20:00:00Z
-```
-
-Optional TikTok privacy:
-
-```bash
-linkme ap post create \
-  --video u/42/my-video \
-  --caption "Behind the scenes" \
-  --platforms tiktok \
-  --tiktok-privacy PUBLIC_TO_EVERYONE
-```
-
-### 3. Inspect the post snapshot
-
-After creation, check the current state:
-
-```bash
-linkme ap post status <post-id>
-```
-
-Use this for a one-shot summary of media processing, per-platform target state, published URLs, and errors.
-
-### 4. Watch live progress
-
-To stream live updates until the post is fully published:
-
-```bash
-linkme ap post watch <post-id>
-```
-
-`watch` is the live command. It exits automatically once the post reaches fully published state.
-
-### 5. Publish immediately if needed
-
-If the post exists but still needs to be pushed now:
-
-```bash
-linkme ap post publish <post-id>
-```
-
-Then re-check with:
-
-```bash
-linkme ap post status <post-id>
-linkme ap post watch <post-id>
-```
-
-## Operating Rules
-
-- Prefer `linkme ap accounts` before creating a post if provider connectivity is unclear.
-- Prefer `linkme ap upload <file>` first when the same video may be reused.
-- Prefer `linkme ap post status <id>` for a one-shot answer.
-- Prefer `linkme ap post watch <id>` when the user wants to wait through processing and publishing.
-- Use `--json` when another tool needs structured output.
-
-## Minimal Happy Path
-
-```bash
-linkme ap upload ./launch.mp4
-linkme ap post create --video u/42/launch --caption "Shipping today" --platforms youtube,tiktok,instagram
-linkme ap post watch <post-id>
-```

package/skills/commerce/merch/SKILL.md

@@ -1,34 +0,0 @@
----
-name: linkme_commerce_merch
-description: Use when you need to inspect merch templates or manage merch categories from the Linkme CLI.
----
-
-# Merch
-
-Use `linkme commerce merch` for merch templates and category housekeeping.
-
-## Quick checks
-
-- `linkme whoami`
-- `linkme commerce --help`
-- `linkme commerce merch --help`
-
-## Merch templates
-
-- List templates: `linkme commerce merch list`
-- Structured output: `linkme commerce merch list --json`
-- The current CLI surface is inspect-only for merch templates; create or edit flows are not exposed here
-
-## Merch categories
-
-- List categories: `linkme commerce merch categories`
-- Create a category: `linkme commerce merch categories --create "Apparel"`
-- Delete a category with confirmation bypass: `linkme commerce merch categories --delete 8 --force`
-- Without `--force`, deletion prompts for confirmation
-- Add `--json` when another tool needs the raw category payload
-
-## Discovery
-
-- If the user wants broader commerce features, inspect `linkme commerce products --help`
-- If the user wants actual storefront products or categories, inspect `linkme shop products --help` and `linkme shop categories --help`
-- If the exact flag shape is unclear, run `linkme commerce merch <subcommand> --help` first