@link.me/cli-darwin-x64 0.4.3 → 0.7.4

package/linkme

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/linkme
-size: 76591376 bytes
-sha256: 2f94773192a0cf7ccf6aa4b54a23fe96ed6eb317f477472cb5b11fe081b008e8
+size: 105573856 bytes
+sha256: f3b12465008c65a0275f8358ef0a0de6618d42d6ee3a249766b021a059e1b71e

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@link.me/cli-darwin-x64",
-	"version": "0.4.3",
+	"version": "0.7.4",
 	"description": "Platform binary for @link.me/cli (darwin-x64)",
 	"license": "UNLICENSED",
 	"os": [

package/skills/linkme-getting-started/SKILL.md

@@ -0,0 +1,15 @@
+---
+name: linkme-getting-started
+description: First-run setup for the Linkme plugin. Use right after installation, or when a user asks how to get started, to confirm sign-in, connect social platforms, and draft a first cross-platform post.
+---
+
+# Getting Started
+
+Goal: within a few turns the user is signed in, has at least one social platform connected, and knows how to publish everywhere from the conversation.
+
+1. **Confirm the account.** Call `whoami`. On an authentication error, ask the user to reconnect Linkme from the plugin's settings and stop.
+2. **Connect platforms.** Call `linkme_show_accounts`. The card connects and reconnects platforms directly, so do not restate its contents; ask which platforms they post to most.
+3. **Draft a first post.** Offer to prepare one. When the user attaches media or describes a text post, call `linkme_compose_post` with a suggested caption and their connected platforms. The composer publishes only after the user confirms, so never call `ap_post_create` during onboarding.
+4. **Point to what's next.** Mention the Publishing Studio (`linkme_studio`, also in the sidebar) for the content calendar and insights, and suggest one prompt to try, such as "What's scheduled this week?" or "How are my accounts doing this month?".
+
+Keep replies short; the interactive views carry the details. Without an MCP Apps host, the same tools return text summaries, so relay those briefly.

package/skills/linkme-manage-commerce/SKILL.md

@@ -65,12 +65,11 @@ linkme shop products add \
   --image ./poster.jpg
 ```
 
-Use `$linkme-manage-media` whenever a product needs a file, thumbnail, or image. Hosted MCP may omit file-backed product creation; check `linkme_capabilities` and use the local CLI when required.
+Use `$linkme-manage-media` whenever a product needs a file, thumbnail, or image. On hosted MCP, supply product files only through the staged file fields the tool schema declares; check `linkme_capabilities` when unsure.
 
-`commerce products create` is available only through the local CLI or local
-stdio MCP because it reads a local product file. Hosted MCP can use only file
-objects explicitly declared by an available tool; never pass it a local or
-sandbox path.
+`commerce products create` reads a local product file and thumbnail in the
+CLI. On hosted MCP both are staged file inputs declared by the tool schema;
+never pass hosted MCP a local or sandbox path.
 
 ## Purchased content
 

package/skills/linkme-manage-media/SKILL.md

@@ -45,8 +45,7 @@ Prefer a reusable Linkme or AP object reference when the same asset will be used
 - Provide exactly one source for a media input.
 - Treat local paths, `file:` URLs, `data:` URLs, and arbitrary public URLs as unsupported unless capabilities and the tool schema explicitly allow them.
 - For hosted video workflows with proxy uploads disabled, ask for an existing Linkme/AP reference or switch to the local CLI.
-- Course cover, attachment, and lesson-video upload commands are local-only. Do not offer them through hosted MCP.
-- File-backed digital-product creation is local-only. AI merch mockup generation is hosted-capable only through its declared JPEG, PNG, or WebP file field and 8 MiB limit.
+- Course cover, attachment, and lesson-video uploads (`courses assets upload`, `courses videos upload`) and file-backed digital-product creation take staged files on hosted MCP through the file fields their schemas declare. AI merch mockup generation is hosted-capable only through its declared JPEG, PNG, or WebP file field and 8 MiB limit.
 
 ## Validate and verify
 

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

@@ -9,6 +9,8 @@ Use Linkme AP to publish video, image, carousel, or text posts to connected soci
 
 Prefer connected Linkme MCP tools. Their names mirror CLI paths with underscores; use the shell commands below as fallback and discovery examples.
 
+When the MCP host renders interactive views (ChatGPT, Claude), open `linkme_compose_post` with the same inputs you would pass to `ap_post_create`. The user reviews the media, caption, platforms, per-platform limits, and timing, then publishes from the composer, which counts as their approval. After publishing, show `linkme_show_post` for live per-platform status instead of polling and narrating it.
+
 ## 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.
@@ -29,6 +31,8 @@ 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.
 
+For a business page, `ap accounts` lists only the accounts assigned to that page, and `ap post create` posts from those accounts. If a requested network has no account there, the post is refused with `MISSING_PROVIDER_ACCOUNT`: tell the user which network is missing and that it must be connected to the page or assigned by an owner. Don't retry with other accounts.
+
 Confirm:
 
 - target providers and account availability

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

@@ -9,6 +9,8 @@ Turn Linkme analytics into an evidence-based summary. Use explicit date ranges f
 
 Prefer connected Linkme MCP tools. Their names mirror CLI paths with underscores; use the shell commands below as fallback and discovery examples.
 
+For a quick visual check-in on an interactive host, call `linkme_show_insights` with `days` of 7, 30, or 90. It shows social account growth and link-in-bio traffic together. Add one or two observations rather than restating its numbers, and use the detailed tools below for deeper or custom-range analysis.
+
 ## Collect the relevant views
 
 ```bash