@actionway/cli 0.4.0-staging.17d7a5a → 0.4.0-staging.de9c9b2
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/actionway.mjs +1 -1
- package/package.json +1 -1
- package/skills/actionway/SKILL.md +6 -4
package/package.json
CHANGED
|
@@ -9,10 +9,12 @@ Use the installed `actionway` CLI as the capability source of truth. Do not memo
|
|
|
9
9
|
|
|
10
10
|
## Discover and prepare
|
|
11
11
|
|
|
12
|
-
1.
|
|
13
|
-
2.
|
|
14
|
-
3.
|
|
15
|
-
4.
|
|
12
|
+
1. If the user supplied an existing pending `job_ref`, skip updating and continue its polling protocol below.
|
|
13
|
+
2. Otherwise, once per Agent session, run `actionway update --check`. The CLI caches this registry check for 24 hours. If the check fails, continue with the installed CLI and do not block the user's task. If `update_available` is true, run `actionway update`, then use the new CLI starting with the next command.
|
|
14
|
+
3. Run `actionway whoami`. If no Actionway login exists, run `actionway init --agent=codex` from Codex or `actionway init --agent=claude` from Claude. Tell the user that browser authorization will open and ask them only to approve access there. Never ask them to paste credentials into chat.
|
|
15
|
+
4. Run `actionway --help` to find an appropriate capability.
|
|
16
|
+
5. Before the first use of a command, run `actionway <command> --help` and, when offered, `actionway <command> --print-schema`.
|
|
17
|
+
6. Validate required local files and ask for user approval before an operation that incurs a charge.
|
|
16
18
|
|
|
17
19
|
## Execute
|
|
18
20
|
|