fix(cli): harden init AI-tooling hand-off and report real skills install

Warn and continue when MCP install fails instead of aborting init, so an
already-installed skill and the project scaffold are not lost. installSkills
now reports whether anything was actually written, so the AI hand-off is only
offered and described when skills really landed (not when only an unsupported
target was chosen). The hand-off message now covers skills, MCP, or both.

Author: ericallam

packages/cli-v3/src/commands/init.ts

@@ -206,11 +206,12 @@ async function _initCommand(dir: string, options: InitCommandOptions) {
       );
 
       if (installError) {
-        outro(`Failed to install MCP server: ${installError.message}`);
-        return;
+        // Don't abort init if MCP fails: skills may already be installed and the user
+        // still needs the project scaffolded. Warn and carry on.
+        log.warn(`Skipped MCP server: ${installError.message}`);
+      } else {
+        installedMcp = true;
       }
-
-      installedMcp = true;
     }
 
     // Vibe path: once AI tooling is actually installed, the user can hand scaffolding to
@@ -235,9 +236,11 @@ async function _initCommand(dir: string, options: InitCommandOptions) {
 
       if (!isCancel(setupChoice) && setupChoice === "ai") {
         outro(
-          installedSkills
-            ? "Your AI tooling is ready. Ask your assistant to set up Trigger.dev and it will use the getting-started skill to add the SDK, config, and your first task."
-            : "The MCP server is installed. Ask your assistant to set up Trigger.dev using the MCP server."
+          installedSkills && installedMcp
+            ? "Your AI tooling is ready. Ask your assistant to set up Trigger.dev; it can use the getting-started skill and the MCP server to add the SDK, config, and your first task."
+            : installedSkills
+              ? "Your AI tooling is ready. Ask your assistant to set up Trigger.dev and it will use the getting-started skill to add the SDK, config, and your first task."
+              : "The MCP server is installed. Ask your assistant to set up Trigger.dev using the MCP server."
         );
         return;
       }

packages/cli-v3/src/commands/skills.ts

@@ -278,19 +278,20 @@ export async function installSkillsFromInit(opts: SkillsWizardOptions = {}): Pro
   writeConfigHasSeenRulesInstallPrompt(true);
   writeConfigLastRulesInstallPromptVersion(manifest.currentVersion);
 
-  await installSkills(manifest, opts);
-
-  return true;
+  // Returns true only if skills were actually written (false e.g. when the only target
+  // chosen is "unsupported"), so callers like `trigger init` don't claim skills are ready
+  // when nothing landed.
+  return await installSkills(manifest, opts);
 }
 
-async function installSkills(manifest: RulesManifest, opts: SkillsWizardOptions) {
+async function installSkills(manifest: RulesManifest, opts: SkillsWizardOptions): Promise<boolean> {
   const currentVersion = await manifest.getCurrentVersion();
 
   const targetNames = await resolveTargets(opts);
 
   if (targetNames.length === 1 && targetNames.includes("unsupported")) {
     handleUnsupportedTargetOnly();
-    return;
+    return false;
   }
 
   const results = [];
@@ -303,7 +304,9 @@ async function installSkills(manifest: RulesManifest, opts: SkillsWizardOptions)
     }
   }
 
-  if (results.some((r) => r.installations.length > 0 || r.pointer)) {
+  const installedAny = results.some((r) => r.installations.length > 0 || r.pointer);
+
+  if (installedAny) {
     log.step("Installed the following skills:");
 
     for (const r of results) {
@@ -319,6 +322,8 @@ async function installSkills(manifest: RulesManifest, opts: SkillsWizardOptions)
       `${cliLink("Learn how to use Trigger.dev skills", "https://trigger.dev/docs/agents/rules/overview")}`
     );
   }
+
+  return installedAny;
 }
 
 function handleUnsupportedTargetOnly() {