@standardagents/skill 0.21.1 → 0.22.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@standardagents/skill",
-  "version": "0.21.1",
+  "version": "0.22.0",
   "private": false,
   "publishConfig": {
     "access": "public",

package/skills/agentbuilder/SKILL.md

@@ -538,6 +538,10 @@ await state.setValue('invocation_count', count + 1);
 
 `setValue(key, null)` and `setValue(key, undefined)` delete the key. For larger payloads, binary data, user-visible artifacts, or content that should be shared as a file, use `state.writeFile()` / `state.readFile()` instead.
 
+### Agent Skills library
+
+`state.skills` is the instance-GLOBAL Agent Skills library (agentskills.io SKILL.md format) — the deliberate exception to per-thread scoping: skills install once and every thread sees them. `list()` returns metadata (name + description), `get(name)` loads a SKILL.md body on demand (progressive disclosure), `readFile(name, path)` opens bundled files, and `install(files)` / `setEnabled` / `remove` manage the library. Identity always comes from SKILL.md frontmatter (`name`, `description`), validated on install.
+
 ### Sandboxed code execution
 
 Use `state.runCode()` for model- or user-authored JavaScript/TypeScript instead of `eval` or `new Function`. The sandbox runs in Cloudflare Dynamic Workers, has no implicit thread state, filesystem, network, timers, or host globals, and only receives capabilities you explicitly bridge through `imports` or `globals`.
@@ -755,6 +759,16 @@ SubagentToolConfig — entry on a parent prompt's `tools` array
   initAttachmentsProperty    schema field name           tool arg holding /attachments/* paths to copy to child
   initAgentNameProperty      schema field name           tool arg used to tag the child thread (UI label)
   optional                   string (env name)           subagent disabled unless this env resolves truthy
+  parentCommunication        'implicit' | 'explicit'     top-level form for NON-resumable subagents; explicit
+                                                         means completion is not auto-queued to the parent
+                                                         (so the parent is not woken). Use for background
+                                                         children that deliver results via parent thread KV.
+                                                         resumable.parentCommunication takes precedence.
+  hidden                     boolean                     relationship stays declared and spawnable by runtime
+                                                         code (invokeTool/queueTool from hooks), but the tool
+                                                         is excluded from every LLM request — the model can
+                                                         never call it (infrastructure children, e.g. a
+                                                         background compaction agent)
 ```
 
 For resumable lifecycle creation, `subagent_create.arguments` is shaped by the prompt schema on the receiving child side (`resumable.receives_messages`). The runtime persists those values with the child thread and restores them as `ThreadState.arguments` for both child sides; top-level keys are also prompt variables during render, including included prompts.
@@ -770,7 +784,7 @@ These are correct as written in the spec — internalize them.
    - Implicitly via `immediate: { ... }` — the child spawns the moment the parent prompt activates, before any LLM step.
 2. **Children only communicate back to their parents.** Two flavors:
    - **Implicit**: the child auto-queues a message to the parent when the session ends (via `sessionStop`, `sessionFail`, or `maxSessionTurns`). Default for all subagents.
-   - **Explicit**: only when code calls `state.notifyParent()`, `state.setStatus()`, or `state.stopSession({ result, notifyParent, status })`. Set with `resumable.parentCommunication: 'explicit'`. Use for high-traffic resumables (e.g., a Slack monitor) where you want control over when the parent is interrupted.
+   - **Explicit**: only when code calls `state.notifyParent()`, `state.setStatus()`, or `state.stopSession({ result, notifyParent, status })`. Set with `resumable.parentCommunication: 'explicit'` (resumable) or top-level `parentCommunication: 'explicit'` (non-resumable). Use for high-traffic resumables (e.g., a Slack monitor) where you want control over when the parent is interrupted, or for non-resumable background workers (e.g., a compaction agent) whose completion should not wake the parent because results are delivered via the parent's thread KV.
 3. **Resumable subagents can receive messages from their parents.** `resumable.receives_messages` chooses which side hears them.
 4. **When a child sends back to the parent, it MUST indicate whether it needs a response** — in plain English, e.g. "After researching, you must respond so I can continue with the email." A research subagent providing FYI info doesn't need a response; a gmail subagent waiting on guidance does.
 5. **File attachments use path strings.** `/attachments/{filename}.{ext}`. Use this convention everywhere — the runtime copies attachments across thread filesystems automatically when listed in `initAttachmentsProperty`.