docs: clarify cluster reporting format in skill

Author: huntharo

skills/ghcrawl/SKILL.md

@@ -145,11 +145,15 @@ ghcrawl neighbors owner/repo --number 42 --limit 10
 - Report the repo name and whether you refreshed data in this run.
 - When listing clusters, include:
   - cluster id
+  - representative number and kind
   - display title
   - total size
   - PR count
   - issue count
   - latest updated time
+- When naming a cluster in prose, use this shape:
+  - `Cluster <clusterId> (#<representativeNumber> representative <issue|pr>)`
+  - example: `Cluster 23945 (#42035 representative issue)`
 - When drilling into a cluster, include clickable GitHub links for each issue/PR if you mention them.
 - Prefer concise summaries over dumping raw JSON.
 - If freshness is stale, say that explicitly:

skills/ghcrawl/references/protocol.md

@@ -72,6 +72,15 @@ Each cluster includes:
 - `representativeNumber`
 - `representativeKind`
 
+When reporting a cluster to the user, do not mention only the cluster id. Use:
+
+- `Cluster <clusterId> (#<representativeNumber> representative <issue|pr>)`
+
+Examples:
+
+- `Cluster 23945 (#42035 representative issue)`
+- `Cluster 104 (#38112 representative pr)`
+
 This is the normal read-only exploration command for existing local data.
 
 ### `ghcrawl cluster-detail owner/repo --id <cluster-id>`