@integrity-labs/agt-cli 0.19.8 → 0.19.9

package/dist/bin/agt.js

@@ -50,7 +50,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-E4TNET3D.js";
+} from "../chunk-GLZKMKZM.js";
 
 // src/bin/agt.ts
 import { join as join10 } from "path";
@@ -3734,7 +3734,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync5, realpathSync } from "fs";
 import chalk17 from "chalk";
 import ora15 from "ora";
-var cliVersion = true ? "0.19.8" : "dev";
+var cliVersion = true ? "0.19.9" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -4192,7 +4192,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.19.8" : "dev";
+var cliVersion2 = true ? "0.19.9" : "dev";
 var program = new Command();
 program.name("agt").description("Augmented CLI \u2014 agent provisioning and management").version(cliVersion2).option("--json", "Emit machine-readable JSON output (suppress spinners and colors)").option("--skip-update-check", "Skip the automatic update check on startup");
 program.hook("preAction", (thisCommand) => {

package/dist/{chunk-E4TNET3D.js → chunk-GLZKMKZM.js}

@@ -2766,7 +2766,27 @@ you MUST use the Augmented MCP tools \u2014 never write to
   this team
 - **\`mcp__augmented__skill_improve\`** \u2014 propose targeted edits
 
-Why this matters: skills authored via the MCP land in the team-scoped
+### Always confirm scope before creating
+
+Before invoking \`skill_create\`, ask the user: **"Should this skill be
+agent-scoped (only this agent uses it) or team-scoped (every agent on
+the team can install it)?"** Default to agent scope when the user
+just says "create a skill" without specifying. Confirming up-front
+avoids the two-call dance where you try team scope, get refused by
+\`charter.tools.skills.write_team\`, and then fall back to agent \u2014
+once the user has answered, you make a single deliberate call.
+
+### Quote the review link in your reply
+
+\`skill_create\` returns a \`review_url\` field when the skill lands as
+a draft awaiting operator review. Quote that URL back to the user in
+your reply (e.g. \`"Created \u2014 review here: <url>"\`) so the operator
+can one-click navigate to the Pending Skills card and publish or
+reject without hunting through the queue.
+
+### Why this matters
+
+Skills authored via the MCP land in the team-scoped
 \`skill_definitions\` registry, so every agent on the team picks them
 up on next refresh, the manager re-provisions them on the agent's host,
 and operators see them in the webapp's pending-skills queue for review.
@@ -8181,4 +8201,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-E4TNET3D.js.map
+//# sourceMappingURL=chunk-GLZKMKZM.js.map