soft-skills 2.1.17 → 2.1.19

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 CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "soft-skills",
3
- "version": "2.1.17",
3
+ "version": "2.1.19",
4
4
  "description": "Communication toolkit for burnt-out humans and collaborative AI's",
5
5
  "author": "Gilad Barnea (https://github.com/giladbarnea)",
6
6
  "homepage": "https://github.com/giladbarnea/soft-skills",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "soft-skills",
3
- "version": "2.1.17",
3
+ "version": "2.1.19",
4
4
  "description": "Communication toolkit for burnt-out humans and collaborative AI's",
5
5
  "author": {
6
6
  "name": "Gilad Barnea",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "soft-skills",
3
- "version": "2.1.17",
3
+ "version": "2.1.19",
4
4
  "description": "Communication toolkit for burnt-out humans and collaborative AI's",
5
5
  "author": {
6
6
  "name": "Gilad Barnea",
@@ -16,6 +16,7 @@ For relationship definitions, see the plugin's [roles map](../../roles.md).
16
16
  | The harness cannot set the model, thinking, or fork you chose | [Dispatch outside the harness](planning/dispatch-outside-the-harness.md) |
17
17
  | About to dispatch, or currently supervising delegates | [Delegate coordination](coordination/delegates.md) |
18
18
  | The session appears to span multiple hours or more | Also [Many-hours supervision](coordination/many-hours-supervision.md) |
19
+ | Balancing quotas or spend | [Budget balancing](coordination/budget-balancing.md) |
19
20
  | Requesting work from an agent without shared context | [Fresh-context briefing](briefing/fresh-context.md) |
20
21
  | Briefing an agent with inherited context window | [Forked-context briefing](briefing/forked-context.md) |
21
22
  | Examples of briefing delegates | [Briefing examples](briefing/examples.md) |
@@ -0,0 +1,7 @@
1
+ After having tried to overcome a setback multiple times without a major breakthrough, spawn Claude Fable 5.1 on max, with fresh context. Tell it only in product and behavior terms:
2
+
3
+ ```text
4
+ We are working on <planfile>. We are at step X. We have encountered the following unexpected challenges: … We expected behavior Y but seem to have some difficulty getting there. We might be carrying a blind spot or be too invested in the work to think of an effective solution. Take a look at what we have done so far. Can you think of an outside-the-box solution that we might have overlooked that bypasses the problem?
5
+ ```
6
+
7
+ Then, after its response, use judgment. It might propose a good direction worth pursuing. It is not like you have a lot to lose, since at that hypothetical moment you have already been trying for a while without success.
@@ -0,0 +1,20 @@
1
+ ---
2
+ name: budget-balancing
3
+ description: Agree on usage checks and limits, preserve work at a limit, and switch between pre-approved models.
4
+ ---
5
+
6
+ # Budget Balancing
7
+
8
+ ## Agree on usage checks and limits
9
+
10
+ Ask the human whether to monitor usage. If so, agree on which budgets to monitor, including subscriptions and API keys, and how to check each one. Ask which metrics to watch and what actions to take at each threshold. Suggest pausing and boomeranging yourself an amount of hours later to check if within resume range then.
11
+
12
+ For subscriptions, calculate burn rate against remaining capacity w.r.t. time until the next reset. For API usage, track total spend, remaining budget, and spending rate over time.
13
+
14
+ ## Pause and preserve work
15
+
16
+ If a provider is over budget, move work to a pre-approved equivalent model on another provider within budget. Preserve the role.
17
+
18
+ At the agreed resource limit, pause delegates at the nearest safe checkpoint. Save work in a versioned handoff commit.
19
+
20
+ For handoff guidance, read [the handoff skill](../../handoff/SKILL.md).
@@ -30,7 +30,7 @@ The chain processes at every rung: each agent surfaces to its leader only what n
30
30
 
31
31
  **Batch approvals.** When you expect several approvals to arrive close together, hold them and bring one grouped request. One decision session beats three interruptions. A lone question does not wait for company.
32
32
 
33
- **Suggest, then get approval.** If you intend to dispatch delegates of your own, you may propose a delegation shape, but your leader must approve it before you dispatch anyone.
33
+ **Suggest, then get approval**, unless your leader has already approved this kind of delegation.
34
34
 
35
35
  ## Understand an Escalation Before Passing It Up
36
36
 
@@ -9,11 +9,7 @@ Read this when the session appears to span multiple hours or more. You remain re
9
9
 
10
10
  Detect rabbit holes and stalls, and keep useful work moving within authorization. Activity alone does not prove progress.
11
11
 
12
- ## Agree on usage checks and limits
13
-
14
- Ask the human whether to monitor usage. If so, agree on which budgets to monitor, including subscriptions and API keys, and how to check each one. Ask which metrics to watch and what actions to take at each threshold. Suggest pausing and boomeranging yourself an amount of hours later to check if within resume range then.
15
-
16
- For subscriptions, calculate burn rate against remaining capacity w.r.t. time until the next reset. For API usage, track total spend, remaining budget, and spending rate over time.
12
+ For subscription quotas, API spend, and provider switching, read [Budget balancing](budget-balancing.md).
17
13
 
18
14
  ## Check progress and resources
19
15
 
@@ -22,8 +18,7 @@ For subscriptions, calculate burn rate against remaining capacity w.r.t. time un
22
18
 
23
19
  ## Pause and preserve work
24
20
 
25
- 1. At the agreed resource limit, pause delegates at the nearest safe checkpoint. Save work in a versioned handoff commit.
26
- 2. When delegates report a slow down, pause them and ask the human for direction. Schedule a 30m reminder to check for a reply. In absence of a reply, and if budget allows, proceed to seek independent advice.
21
+ When delegates report a slow down, pause them and ask the human for direction. Schedule a 30m reminder to check for a reply. In absence of a reply, and if budget allows, proceed to seek independent advice.
27
22
 
28
23
  For handoff guidance, read [the handoff skill](../../handoff/SKILL.md).
29
24
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: ai-to-leader
3
- description: How to communicate with your leader — whoever gave you your mission and receives your results. Your leader is either the human or the agent that spawned you, so load this skill once at the beginning of the interaction.
3
+ description: "Instructions how to effectively communicate with your leader. You have one: either the human or the agent to whom you report your results. Load this skill first skill in every session."
4
4
  ---
5
5
 
6
6
  # AI → Leader