diff --git a/claude-plugins/plugins/base/skills/forge-issue-filing/SKILL.md b/claude-plugins/plugins/base/skills/forge-issue-filing/SKILL.md
index 580a813e..deef37d5 100644
--- a/claude-plugins/plugins/base/skills/forge-issue-filing/SKILL.md
+++ b/claude-plugins/plugins/base/skills/forge-issue-filing/SKILL.md
@@ -84,10 +84,13 @@ hive-forge repo-labels
 ```
 
 Attach whatever scope labels the repo actually uses (commonly a `type/*`
-and an `area/*`, but check - taxonomies differ per repo). Skipping labels
-entirely is worse than a slightly-off guess: an unlabeled issue is what
-`hive-forge lint unlabeled --scope <scope>` exists to catch, so an
-unlabeled issue you filed becomes someone else's triage cleanup.
+and an `area/*`, but check - taxonomies differ per repo) when you
+already know them - it saves a round trip. But don't stress over an
+unlabeled issue: labeling what's already filed is what triage coverage
+(`hive-forge lint unlabeled --scope <scope>`, and whatever agent/process
+this hive runs to sweep it) exists for. Guessing at a label you're not
+sure of just to avoid leaving it blank can do more harm than leaving it
+for triage to get right.
 
 ## 5. Assignee: leave it to triage unless you know who owns it