@agentled/cli 0.7.1 → 0.7.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/agentled/SKILL.md +14 -0
package/package.json
CHANGED
package/skills/agentled/SKILL.md
CHANGED
|
@@ -184,6 +184,20 @@ The workspace inspection directly informs:
|
|
|
184
184
|
|
|
185
185
|
> **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.
|
|
186
186
|
|
|
187
|
+
## MCP-connected but no local scaffold: expected behavior
|
|
188
|
+
|
|
189
|
+
If MCP tools are already connected and working, **do not block** on missing local folders.
|
|
190
|
+
|
|
191
|
+
- Continue with MCP operations immediately.
|
|
192
|
+
- Add a brief, non-blocking hint once per session:
|
|
193
|
+
- `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).`
|
|
194
|
+
- Do **not** imply setup is required for read/write API operations through MCP.
|
|
195
|
+
|
|
196
|
+
Use this when users ask "did anything get created locally?" or "why is there no workspace folder?"
|
|
197
|
+
|
|
198
|
+
- `agentled setup` is the full first-run path (auth, workspace folder scaffold, MCP config, skill install, knowledge probe, restart prompt).
|
|
199
|
+
- `agentled init` is the targeted local scaffold command when they only want the local workspace folder and cache.
|
|
200
|
+
|
|
187
201
|
## Incremental Authoring (recommended)
|
|
188
202
|
|
|
189
203
|
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.
|