agent-afk 3.8.6 → 3.8.9
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/dist/cli.mjs +122 -119
- package/dist/index.mjs +3 -0
- package/dist/telegram.mjs +3 -0
- package/package.json +1 -1
package/dist/index.mjs
CHANGED
|
@@ -1168,6 +1168,9 @@ Apply in order \u2014 first match wins:
|
|
|
1168
1168
|
3. Any rejection check = Yes \u2192 **REJECT** (SALVAGE only if the sole Yes is "better folded into another skill")
|
|
1169
1169
|
4. Any single Stage 1 rubric dimension \u22642 \u2192 downgrade one tier from the rubric-total result (APPROVE\u2192SALVAGE, SALVAGE\u2192REJECT)
|
|
1170
1170
|
5. Workflow Impact \u22643 \u2192 downgrade one tier (session shape must materially change for this plugin)
|
|
1171
|
+
|
|
1172
|
+
_Why rule 5 fires often:_ Skills in the gate/guard/check category \u2014 those that add an advisory step rather than reshape session flow \u2014 systematically score WI \u22643 by design. Examples that have hit this rule: \`thesis-lock\`, \`checkpoint\`, \`read-before-explain\`, \`premise-check\`, \`drift-watch\`. This is intentional: a one-line check that mutates Claude's behavior on a specific signal is rarely transformative enough to clear WI \u22654. If the candidate is borderline, prefer folding it into an incumbent skill (or accepting the SALVAGE downgrade) over forcing an APPROVE.
|
|
1173
|
+
|
|
1171
1174
|
6. Stage 2 failure-resilience total \u22648 (Fragile band) \u2192 downgrade one tier (a fragile force multiplier is still dangerous). Note which dimensions scored 0\u20131 in the Rewrite target so the skill can be hardened.
|
|
1172
1175
|
- Rules 4, 5, and 6 do not stack \u2014 apply at most one downgrade per candidate. If multiple fire, prefer rule 6 (failure behavior is the most costly to miss).
|
|
1173
1176
|
7. Stage 1 total \u226524/30 \u2192 **APPROVE**
|
package/dist/telegram.mjs
CHANGED
|
@@ -1325,6 +1325,9 @@ Apply in order \u2014 first match wins:
|
|
|
1325
1325
|
3. Any rejection check = Yes \u2192 **REJECT** (SALVAGE only if the sole Yes is "better folded into another skill")
|
|
1326
1326
|
4. Any single Stage 1 rubric dimension \u22642 \u2192 downgrade one tier from the rubric-total result (APPROVE\u2192SALVAGE, SALVAGE\u2192REJECT)
|
|
1327
1327
|
5. Workflow Impact \u22643 \u2192 downgrade one tier (session shape must materially change for this plugin)
|
|
1328
|
+
|
|
1329
|
+
_Why rule 5 fires often:_ Skills in the gate/guard/check category \u2014 those that add an advisory step rather than reshape session flow \u2014 systematically score WI \u22643 by design. Examples that have hit this rule: \`thesis-lock\`, \`checkpoint\`, \`read-before-explain\`, \`premise-check\`, \`drift-watch\`. This is intentional: a one-line check that mutates Claude's behavior on a specific signal is rarely transformative enough to clear WI \u22654. If the candidate is borderline, prefer folding it into an incumbent skill (or accepting the SALVAGE downgrade) over forcing an APPROVE.
|
|
1330
|
+
|
|
1328
1331
|
6. Stage 2 failure-resilience total \u22648 (Fragile band) \u2192 downgrade one tier (a fragile force multiplier is still dangerous). Note which dimensions scored 0\u20131 in the Rewrite target so the skill can be hardened.
|
|
1329
1332
|
- Rules 4, 5, and 6 do not stack \u2014 apply at most one downgrade per candidate. If multiple fire, prefer rule 6 (failure behavior is the most costly to miss).
|
|
1330
1333
|
7. Stage 1 total \u226524/30 \u2192 **APPROVE**
|