soft-skills 2.1.9 → 2.1.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "soft-skills",
-  "version": "2.1.9",
+  "version": "2.1.10",
   "description": "Communication toolkit for burnt-out humans and collaborative AI's",
   "author": "Gilad Barnea (https://github.com/giladbarnea)",
   "homepage": "https://github.com/giladbarnea/soft-skills",

package/plugins/soft-skills/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "soft-skills",
-  "version": "2.1.9",
+  "version": "2.1.10",
   "description": "Communication toolkit for burnt-out humans and collaborative AI's",
   "author": {
     "name": "Gilad Barnea",

package/plugins/soft-skills/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "soft-skills",
-  "version": "2.1.9",
+  "version": "2.1.10",
   "description": "Communication toolkit for burnt-out humans and collaborative AI's",
   "author": {
     "name": "Gilad Barnea",

package/plugins/soft-skills/skills/ai-to-delegated/SKILL.md

@@ -11,7 +11,7 @@ For relationship definitions, see the plugin's [roles map](../../roles.md).
 
 | Current situation | Read |
 | --- | --- |
-| Exchanging messages with another agent | [Token-economic communication](../../token-economic-communication.md) |
+| Your context window or another agent’s is tight or likely to run short | You and the affected agent’s team should apply [token-economic communication](../../token-economic-communication.md) |
 | Deciding whether delegation is worthwhile | [When to delegate](planning/when-to-delegate.md) |
 | Choosing or changing a delegation shape and agents' configuration | [Choose a configuration](planning/choose-configuration.md) |
 | The harness cannot set the model, thinking, or fork you chose | [Dispatch outside the harness](planning/dispatch-outside-the-harness.md) |

package/plugins/soft-skills/skills/ai-to-leader/SKILL.md

@@ -5,7 +5,7 @@ description: How to communicate with your leader — whoever gave you your missi
 
 # AI → Leader
 
-Your leader is whoever gave you the mission and receives your results. Load the [theory-of-mind skill](../theory-of-mind/SKILL.md) once. This skill is the upward projection of that theory: re-ground the reader, carry the delta, compress to what they need. For that compression, read [token-economic communication](../../token-economic-communication.md) once while it remains in context.
+Your leader is whoever gave you the mission and receives your results. Load the [theory-of-mind skill](../theory-of-mind/SKILL.md) once. This skill is the upward projection of that theory: re-ground the reader, carry the delta, compress to what they need.
 
 ## Every report is a cold entry
 
@@ -38,3 +38,4 @@ If you work alongside teammates, read [peer coordination](../ai-to-delegated/coo
 ---
 
 If your leader is a human, also load this skill’s `references/human.md`. Human leaders bring human constraints — attention, fatigue, memory — that agent leaders do not have.
+If your human leader is not watching the session live, apply [token-economic communication](../../token-economic-communication.md) to interim messages to them.

package/plugins/soft-skills/token-economic-communication.md

@@ -1,8 +1,10 @@
 ---
 description: A communication style that saves tokens and extends the context-window runway.
 ---
-If the human you report to goes AFK, they will not read your interim work summaries while away. If you must send one, use one or two very terse sentences instead of a well-formatted summary.
+Apply each matching rule while its condition holds.
 
-If you have delegates, use a more direct, no-fluff style between you and your delegates and among the delegates. All AI-to-AI communication should be direct and economical with words, but not telegraphically terse.
-
-When something meaningful is merged into main, write me a good summary.
+- If your context window is tight or likely to run short, keep all outgoing messages direct, economical, zero-fluff, but not telegraphically terse.
+- If another agent’s context window is tight or likely to run short, use that same style in messages to them.
+- Skip routine interim summaries. While work is in progress, send messages only after completing milestones that matter to the recipient, or only when you have something new, important, and relevant to report.
+- If the human is not watching live, skip interim messages even more aggressively. There is literally no one to read them, and they will just waste tokens.
+- If the work is complete or blocked, give your leader a proper summary. Any remaining context constraints still apply.