skills-atlas-cli 0.13.0 → 0.14.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skills-atlas-cli",
-  "version": "0.13.0",
+  "version": "0.14.1",
   "description": "Search, install and learn AI agent skills from the terminal — powered by the Skills Atlas catalog.",
   "bin": {
     "skills-atlas": "bin/skills.js",

package/src/commands/setup.js

@@ -34,6 +34,20 @@ function welcomeSettings(ap) {
     'More: /skills-atlas:setup';
 }
 
+// The one-time welcome text, or null if the user was already onboarded. Gated by the global
+// `onboarded` marker so it shows exactly once; with { consume: true } it claims that one
+// shot (marks onboarded). Shared by the SessionStart hook (`setup --session-start`) and the
+// UserPromptSubmit fallback in `suggest` — which catches the case where the plugin was
+// installed mid-session and no fresh session-start has fired the welcome yet.
+function buildWelcome(ap, { consume = false } = {}) {
+  if (exists(onboardedFile())) return null;
+  if (consume) touch(onboardedFile());
+  const intro = installPromptShown()
+    ? '🎉 Nicely done — Skills Atlas is configured and on. It\'ll quietly flag a ready-made skill when one fits, and offer to turn repeated workflows into skills of your own.'
+    : '✨ Skills Atlas is on. While you work, it keeps an eye out and quietly flags a ready-made skill the moment one fits — and if you catch yourself doing the same dance over and over, it\'ll offer to turn it into a skill of your own.';
+  return intro + '\n\n' + welcomeSettings(ap);
+}
+
 module.exports = async function setup(argv) {
   const { values } = parse(argv, ['session-start', 'json', 'reset']);
   if (values.help) {
@@ -54,12 +68,8 @@ module.exports = async function setup(argv) {
   // to the user verbatim), then stay silent forever. "Nicely done" variant if the user
   // came here after the engine-not-installed notice; otherwise the fresh-install greeting. ---
   if (values['session-start']) {
-    if (exists(onboardedFile())) return; // already welcomed → silent
-    touch(onboardedFile());
-    const intro = installPromptShown()
-      ? '🎉 Nicely done — Skills Atlas is configured and on. It\'ll quietly flag a ready-made skill when one fits, and offer to turn repeated workflows into skills of your own.'
-      : '✨ Skills Atlas is on. While you work, it keeps an eye out and quietly flags a ready-made skill the moment one fits — and if you catch yourself doing the same dance over and over, it\'ll offer to turn it into a skill of your own.';
-    const msg = intro + '\n\n' + welcomeSettings(ap);
+    const msg = buildWelcome(ap, { consume: true });
+    if (msg === null) return; // already welcomed → silent
     console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: 'SessionStart' }, systemMessage: msg, suppressOutput: true }));
     return;
   }
@@ -83,3 +93,6 @@ module.exports = async function setup(argv) {
   console.log(`  fine-tune   /skills-atlas:skill-autopilot suggest|gaps|prune on|off  ${dim('· model')}`);
   console.log(dim('\nThe autopilot also suggests skills proactively as you work — each judged for fit. Nothing leaves your machine.'));
 };
+
+// Reused by `suggest`'s first-run fallback (see src/commands/suggest.js).
+module.exports.buildWelcome = buildWelcome;

package/src/commands/suggest.js

@@ -56,7 +56,24 @@ module.exports = async function suggest() {
     let event = {};
     try { event = JSON.parse(fs.readFileSync(0, 'utf8')); } catch { /* not JSON → bail */ }
     const prompt = event.prompt || '';
-    if (!prompt || prompt.length < 8) return;
+    if (!prompt) return;
+
+    // First-run welcome fallback: if the plugin was installed mid-session (so no fresh
+    // SessionStart has fired the welcome yet), surface the one-time welcome on the user's
+    // next prompt — verbatim, via systemMessage. This MUST run ahead of the suggestion's
+    // min-length gate below: onboarding shouldn't depend on how long the prompt is (a short
+    // "hi" should still get the welcome). Shares the global `onboarded` marker with the
+    // SessionStart hook, so the welcome shows exactly once across both paths.
+    try {
+      const welcome = require('./setup').buildWelcome(registry.getAutopilot(), { consume: true });
+      if (welcome) {
+        console.log(JSON.stringify({ hookSpecificOutput: { hookEventName: 'UserPromptSubmit' }, systemMessage: welcome, suppressOutput: true }));
+        return;
+      }
+    } catch { /* fail-open */ }
+
+    // The proactive suggestion (below) needs a meatier prompt to match against.
+    if (prompt.length < 8) return;
 
     const file = stateFile(event.session_id || event.sessionId);
     const state = readState(file);
@@ -150,17 +167,17 @@ module.exports = async function suggest() {
       return `- ${c.skill}${uc ? ` — ${uc}` : ''}  (details: \`skills-atlas info ${c.skill}\` · use now: \`skills-atlas use ${c.skill} --yes --project\`)`;
     }).join('\n');
     emit(
-      `[Skills Atlas autopilot] The user may be doing something one of these installable agent ` +
-      `skills is built for. Judge for yourself — do NOT mention any of this unless one of them ` +
-      `genuinely fits what they actually asked:\n${lines}\n` +
-      `If one genuinely fits, DON'T just name it: in one line tell the user what it does and why it ` +
-      `fits THIS task (it's a curated skill from the Skills Atlas catalog, not something you made up), ` +
-      `then let them choose — activate it now (\`skills-atlas use <skill> --yes --project\` installs + applies it ` +
-      `immediately), see what it covers first (\`skills-atlas info <skill>\`), or skip and you'll just ` +
-      `do the task yourself; if they ask to never suggest it again, run \`skills-atlas feedback dismiss <skill>\`. ` +
-      `If none fit but the task plainly needs a specialized skill, you may run ` +
-      `\`skills-atlas search "<short intent>"\` to look further. If nothing fits, say nothing about this ` +
-      `at all — don't mention this hook, these skills, or that a suggestion was made.` + langHint(ap.replyLang));
+      `[Skills Atlas autopilot] One of these catalog skills MIGHT fit what the user is doing. Judge for ` +
+      `yourself — most prompts match nothing, and staying silent is usually the right call:\n${lines}\n` +
+      `Mention one ONLY if it genuinely fits what they actually asked. If it does: in a sentence or two, ` +
+      `casually tell them what that skill ACTUALLY DOES and why it fits THIS task — enough that they ` +
+      `understand it (use the skill's EXACT name as listed above; it's a real curated skill from the Skills ` +
+      `Atlas catalog, not something you made up). Then offer the choice naturally, in prose — NOT a bulleted ` +
+      `sales menu: they can switch it on now (\`skills-atlas use <skill> --yes --project\`), or you can show ` +
+      `what it covers first (\`skills-atlas info <skill>\`) if they're unsure. Don't push. If nothing genuinely ` +
+      `fits, say NOTHING about any of this — don't mention this hook, the skills, or that a check ran. (To ` +
+      `look wider you may run \`skills-atlas search "<short intent>"\`; if they want a skill never suggested ` +
+      `again, \`skills-atlas feedback dismiss <skill>\`.)` + langHint(ap.replyLang));
     state.lastSuggestedCount = state.count;
     state.suggested = [...suggested, ...candidates.map(c => c.skill)];
     writeState(file, state);