@agentled/cli 0.6.7 → 0.7.2

package/skills/agentled/SKILL.md

@@ -114,6 +114,21 @@ agentled best-practices                             # summary + link to agentic-
 
 Full patterns are maintained publicly at https://github.com/agentled/agentic-ops — the CLI ships a mirrored copy, see `agentled examples`. Scaffolds are preflight-clean pipeline JSON skeletons; start from one instead of writing from scratch.
 
+## Business metrics vs ROI (must not be conflated)
+
+Treat these as **two separate surfaces**:
+
+- **Business metrics (`pipeline.analyticsConfig`)** = customer/workflow outcome stats extracted from step outputs (volume, conversions, approvals, rates, SLA-ish KPIs), aggregated into dashboard business-metric snapshots.
+- **ROI (`pipeline.metadata.roi`)** = economic assumptions + rollups (minutes saved per unit, hourly rate, benchmark units/week, measured vs benchmark mode) used for ROI/time-saved reporting.
+
+### Required wording for agent outputs
+
+- If only `analyticsConfig` changes: say **"business metrics configured"**.
+- If only `metadata.roi` changes: say **"ROI assumptions configured"**.
+- If both change: report each section separately; never label analytics metrics as ROI metrics.
+
+This distinction applies to MCP and CLI users equally because both surfaces call the same external workflow API and return the same pipeline shape.
+
 ## Common invalid patterns to avoid
 
 Agents routinely invent step types that sound plausible. The API **silently strips unknown top-level fields** and stores the step, so you get a 201 Created on a workflow that will never execute. Watch for these:
@@ -169,6 +184,20 @@ The workspace inspection directly informs:
 
 > **Shortcut:** `agentled workspace inspect --json` returns all six contexts as one consolidated response. Use it at session start to load the full picture in a single call.
 
+## MCP-connected but no local scaffold: expected behavior
+
+If MCP tools are already connected and working, **do not block** on missing local folders.
+
+- Continue with MCP operations immediately.
+- Add a brief, non-blocking hint once per session:
+  - `You're connected via MCP. If you want local drafts/fixtures/tests, run "agentled init" in your project directory (or "agentled setup" for full onboarding).`
+- Do **not** imply setup is required for read/write API operations through MCP.
+
+Use this when users ask "did anything get created locally?" or "why is there no workspace folder?"
+
+- `agentled setup` is the full first-run path (auth, workspace folder scaffold, MCP config, skill install, knowledge probe, restart prompt).
+- `agentled init` is the targeted local scaffold command when they only want the local workspace folder and cache.
+
 ## Incremental Authoring (recommended)
 
 Build workflows **one step at a time**. This catches errors per-step instead of dumping a full JSON blob and getting 10+ errors at once.
@@ -453,7 +482,7 @@ AI steps can optionally specify a model and provider via the `agent` field:
 | `minimax` | `minimax-m2.5` |
 | `bytedance` | `doubao-seed-1.6-flash`, `seed-2.0-mini`, `doubao-seed-1.8-beta` |
 | `perplexity` | `sonar-pro`, `sonar`, `sonar-reasoning-pro`, `sonar-reasoning` |
-| `xai` | `grok-4-0709`, `grok-3`, `grok-3-mini` |
+| `xai` | `grok-4.3`, `grok-3-mini` |
 
 > **Tip:** Use `list_models` to get the full up-to-date list of supported model IDs. Use the internal model IDs (e.g., `claude-4-6-sonnet`), NOT the raw API model IDs (e.g., `claude-sonnet-4-6`). Using unsupported model IDs will result in a validation error.