@a5c-ai/babysitter-codex 0.1.6-staging.05b1f6af

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.
@@ -0,0 +1,17 @@
1
+ ---
2
+ name: call
3
+ description: Start a new Babysitter orchestration run from Codex.
4
+ ---
5
+
6
+ # call
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `call` mode:
11
+
12
+ - treat everything after `$call` as the initial Babysitter request for a new
13
+ orchestration run
14
+ - create the process, create the run, and enter the Babysitter loop
15
+ - using this always means the user meant an interactive run.
16
+ - do not create a separate command surface here; this skill only forwards into
17
+ `babysit`
@@ -0,0 +1,16 @@
1
+ ---
2
+ name: doctor
3
+ description: Diagnose Babysitter run health, integration issues, or orchestration failures.
4
+ ---
5
+
6
+ # doctor
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `doctor` mode:
11
+
12
+ - treat everything after `$doctor` as the run selector, subsystem, or problem
13
+ statement to diagnose
14
+ - focus on run health, orchestration correctness, and recovery guidance
15
+ - do not create a separate command surface here; this skill only forwards into
16
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: forever
3
+ description: Run Babysitter in recurring or continuous workflow mode.
4
+ ---
5
+
6
+ # forever
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `forever` mode:
11
+
12
+ - treat everything after `$forever` as the recurring workflow request
13
+ - follow the `babysit` skill contract while optimizing for repeated execution
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: help
3
+ description: Explain Babysitter Codex usage, modes, setup, or operational behavior.
4
+ ---
5
+
6
+ # help
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `help` mode:
11
+
12
+ - treat everything after `$help` as the help target or question
13
+ - focus on explaining the right Babysitter flow or integration surface
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,16 @@
1
+ ---
2
+ name: issue
3
+ description: Run an issue-centric Babysitter workflow.
4
+ ---
5
+
6
+ # issue
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `issue` mode:
11
+
12
+ - treat everything after `$issue` as the issue selector and any extra issue-mode
13
+ instructions
14
+ - focus on the issue-driven orchestration flow
15
+ - do not create a separate command surface here; this skill only forwards into
16
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: model
3
+ description: Inspect or change Babysitter model-routing policy by phase.
4
+ ---
5
+
6
+ # model
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `model` mode:
11
+
12
+ - treat everything after `$model` as the model-routing request
13
+ - focus on showing, clearing, or setting model-routing policy by phase
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: observe
3
+ description: Observe, inspect, or monitor a Babysitter run.
4
+ ---
5
+
6
+ # observe
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `observe` mode:
11
+
12
+ - treat everything after `$observe` as the run selector or observation target
13
+ - focus on inspection, monitoring, and state visibility
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,16 @@
1
+ ---
2
+ name: plan
3
+ description: Plan a Babysitter workflow without executing the run.
4
+ ---
5
+
6
+ # plan
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `plan` mode:
11
+
12
+ - treat everything after `$plan` as the planning request
13
+ - focus on building the best process possible without creating and running the
14
+ actual run unless the user explicitly changes mode
15
+ - do not create a separate command surface here; this skill only forwards into
16
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: project-install
3
+ description: Install the Babysitter Codex workspace integration into the current project.
4
+ ---
5
+
6
+ # project-install
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `project-install` mode:
11
+
12
+ - treat everything after `$project-install` as the workspace-onboarding request
13
+ - focus on project-local setup, hooks/config, and shared process-library usage
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: resume
3
+ description: Resume an existing Babysitter run from Codex.
4
+ ---
5
+
6
+ # resume
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `resume` mode:
11
+
12
+ - treat everything after `$resume` as the run selector or run id
13
+ - focus on restoring the orchestration context and continuing the run honestly
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: retrospect
3
+ description: Summarize or retrospect on a completed Babysitter run.
4
+ ---
5
+
6
+ # retrospect
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `retrospect` mode:
11
+
12
+ - treat everything after `$retrospect` as the run selector to summarize
13
+ - focus on the run history, outcomes, lessons, and gaps
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: team-install
3
+ description: Install the team-pinned Babysitter Codex workspace setup.
4
+ ---
5
+
6
+ # team-install
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `team-install` mode:
11
+
12
+ - treat everything after `$team-install` as team-install arguments or intent
13
+ - focus on shared workspace setup and team-pinned configuration
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: user-install
3
+ description: Install the user-level Babysitter Codex setup.
4
+ ---
5
+
6
+ # user-install
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `user-install` mode:
11
+
12
+ - treat everything after `$user-install` as the user-setup request
13
+ - focus on user profile, user-level install, and personal defaults
14
+ - do not create a separate command surface here; this skill only forwards into
15
+ `babysit`
@@ -0,0 +1,19 @@
1
+ ---
2
+ name: yolo
3
+ description: Run Babysitter autonomously with minimal manual interruption.
4
+ ---
5
+
6
+ # yolo
7
+
8
+ Load and use the installed `babysit` skill.
9
+
10
+ Resolve the request in `yolo` mode:
11
+
12
+ - treat everything after `$yolo` as the autonomous execution request
13
+ - follow the `babysit` skill contract while optimizing for minimal manual
14
+ interruption
15
+ - using this means the user wants to run autonomously with minimal manual
16
+ interruption, so optimize for that by skipping or minimizing any steps that
17
+ would require user input or decision-making during the run
18
+ - do not create a separate command surface here; this skill only forwards into
19
+ `babysit`