chore(core): prefer subagents for bounded non-interactive actions

Adds behavior rule to always prefer subagents (clean or with session context)
for well-bounded actions that require no human interaction, keeping the parent
context lean and enabling parallel execution.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

core/AGENTS.md

@@ -15,6 +15,7 @@
 - Reads, searches, exploration: proceed without asking.
 - Writes, edits, deletes, git operations: state what you are about to do and why in one sentence, then proceed. Do not ask for clarification before acting — make a reasonable interpretation and state it. Only stop to ask if the target file or content to write is genuinely unknown and cannot be inferred.
 - Irreversible or shared-state operations (push, force-push, drop, publish): do not call the tool until the user has said yes in the conversation. State what you are about to do, then wait for explicit approval. Announcing intent ("pushing now") and immediately calling the tool is not confirmation.
+- always prefer using subagents (clean or with session context) to execute well bounded actions that require no human interaction
 
 # Content index
 

plugins/kyberforge/skills/skill-audit/SKILL.md

@@ -83,6 +83,7 @@ Check each pattern is appropriate and correctly formed:
 - Optional directories contain real content — not just unfilled placeholder READMEs
 - `README.md` present and accurately describes the skill and its files
 - No cross-plugin path references in SKILL.md, scripts/, references/, or assets/ — paths using `../`, `../../`, or absolute repo paths (e.g. `plugins/<plugin>/skills/<other-skill>/`) break when the plugin is installed to a cache; flag any found
+- `references/sources.md` is exempt from the cross-plugin path check — `Research doc:` fields are development-only provenance pointers, not runtime references; they intentionally reference paths outside the skill directory and are expected to be non-resolvable after plugin install; `validate-provenance.sh` handles this gracefully by silently skipping upstream checks when those paths don't resolve
 - `tests/` is exempt from the cross-plugin path check — test files are dev-only and may reference repo-level test infrastructure (e.g. a shared `tests/test_helper/`). This dependency must be declared in `tests/README.md`; flag if tests exist but `tests/README.md` is absent or does not document the dependency
 
 ### Formatting

plugins/kyberforge/skills/skill-author/SKILL.md

@@ -7,8 +7,7 @@ description: >
   audit findings", "update based on grill output"). Also use when the user
   provides inline feedback about a skill's behavior and wants it applied, or
   when a grill session, eval run, or audit has produced findings the user wants
-  acted on — even if they don't say "improve" explicitly. Authors and refines
-  skills following the agentskills.io specification. Do not use for read-only review — use
+  acted on — even if they don't say "improve" explicitly. Do not use for read-only review — use
   /skill-audit instead. Do not use to author agent definition files.
 allowed-tools: Bash Read Write Edit
 metadata:

plugins/kyberforge/skills/skill-author/assets/templates/SKILL.md

@@ -28,14 +28,11 @@ description: >
 #   author: your-name
 #   version: "1.0"
 #   category: general
+#   source_keys:
+#     - source-slug-one
+#     - source-slug-two
 # Optional. Arbitrary key-value map. Common keys: author, version, category.
-# No restrictions on keys or values.
-
-# source_keys:
-#   - source-slug-one
-#   - source-slug-two
-# Optional. Populated when this skill was built from /research output.
-# Lists slugs from references/sources.md that informed this file.
+# source_keys: populated when built from /research output. Lists slugs from references/sources.md.
 # Also add source_keys to each references/*.md file that was informed by research.
 
 # allowed-tools: Bash Read Write

plugins/kyberforge/skills/skill-author/scripts/new-skill.sh

@@ -85,4 +85,5 @@ echo "  2. Add scripts to scripts/ if needed (or delete the directory)" >&2
 echo "  3. Add docs to references/ if needed (or delete the directory)" >&2
 echo "  4. Add resources to assets/ if needed (or delete the directory)" >&2
 echo "  5. Add tests to tests/ if the skill has scripts (or delete the directory)" >&2
-echo "  6. Validate: run /skill-audit on $TARGET" >&2
+echo "  6. Populate references/sources.md with research sources, or delete it" >&2
+echo "  7. Validate: run /skill-audit on $TARGET" >&2