@integrity-labs/agt-cli 0.19.3 → 0.19.4

package/dist/bin/agt.js

@@ -50,7 +50,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-CZGII2KB.js";
+} from "../chunk-MC3SMG4A.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.3" : "dev";
+var cliVersion = true ? "0.19.4" : "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.3" : "dev";
+var cliVersion2 = true ? "0.19.4" : "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-CZGII2KB.js → chunk-MC3SMG4A.js}

@@ -2749,6 +2749,36 @@ ${lines.join("\n")}
 
 Check \`.claude/skills/\` for detailed usage instructions for each integration.
 
+`;
+}
+function buildSkillAuthoringSection() {
+  return `## Skill authoring
+
+When the user asks you to **create**, **update**, or **author** a skill,
+you MUST use the Augmented MCP tools \u2014 never write to
+\`.claude/skills/<name>/SKILL.md\` yourself with \`Write\`/\`Edit\`.
+
+- **\`mcp__augmented__skill_create\`** \u2014 author a brand-new skill
+- **\`mcp__augmented__skill_update\`** \u2014 modify an existing skill
+- **\`mcp__augmented__skill_read\`** \u2014 pull a skill's current contents
+  before editing
+- **\`mcp__augmented__skill_list\`** \u2014 discover what skills exist for
+  this team
+- **\`mcp__augmented__skill_improve\`** \u2014 propose targeted edits
+
+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.
+Files written to local \`.claude/skills/\` get wiped the next time the
+manager rebuilds the provision tree, never reach other agents, and
+bypass the operator-review workflow entirely.
+
+If your charter doesn't authorise team-scope skill writes
+(\`charter.tools.skills.write_team\` is false), the MCP call will be
+refused server-side \u2014 surface that error to the user rather than
+falling back to a local-disk write.
+
 `;
 }
 function buildPersonalitySection(seed) {
@@ -2835,6 +2865,7 @@ function generateClaudeMd(input) {
   const memorySection = buildMemorySection(hasQmd);
   const integrationsSection = buildIntegrationsSection(integrations);
   const knowledgeSection = buildKnowledgeSection2(knowledge);
+  const skillAuthoringSection = buildSkillAuthoringSection();
   const personalitySection = buildPersonalitySection(personalitySeed);
   const reportsToSection = buildReportsToSection2(reportsTo);
   const teamSection = buildTeamSection(teamMembers);
@@ -2982,7 +3013,7 @@ first to load your recent board state. This gives you context about completed an
 in-progress items so you can answer accurately.
 
 ${memorySection}
-${reportsToSection}${teamSection}${peopleSection}${integrationsSection}${knowledgeSection}## Dashboards
+${reportsToSection}${teamSection}${peopleSection}${integrationsSection}${knowledgeSection}${skillAuthoringSection}## Dashboards
 
 You can publish your own dashboards inside the Augmented console. They are
 **first-class platform artifacts** \u2014 KPI tiles, charts, refresh-on-demand \u2014
@@ -8150,4 +8181,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-CZGII2KB.js.map
+//# sourceMappingURL=chunk-MC3SMG4A.js.map