fix: align skill id guidance

Author: ysyneu

internal/cli/incident.go

@@ -361,7 +361,7 @@ func newIncidentCreateCmd() *cobra.Command {
 	cmd.Flags().Int64Var(&channelID, "channel", 0, "Channel ID")
 	registerEnumFlag(cmd, "severity", severityEnum...)
 	cmd.Flags().StringVar(&description, "description", "", "Description (max 6144 chars)")
-	cmd.Flags().IntSliceVar(&assign, "assign", nil, "Person IDs to assign (use 'flashduty member list' to look up IDs)")
+	cmd.Flags().IntSliceVar(&assign, "assign", nil, "Member IDs to assign directly (use 'flashduty member list' to look up member IDs)")
 
 	return cmd
 }

skills/flashduty/reference/incident.md

@@ -82,12 +82,12 @@ If you fetch the pieces by hand instead, run **all six** — they are cheap read
 
 ```bash
 ID=<incident-id>                                          # 24-char id from `incident list`
-fduty incident detail   "$ID" --output-format toon        # ① 详情 + AI summary + alert counts + channel_id
-fduty incident alerts   "$ID" --output-format toon        # ② contributing alerts (detail's embedded alerts are empty here)
-fduty incident timeline "$ID" --output-format toon        # ④ timeline  (or `incident feed "$ID"` for the paginated view)
-fduty incident similar  "$ID" --limit 5 --output-format toon          # ⑤ similar past incidents (channel-backed; see Gotchas)
-fduty incident post-mortem-list --channel-ids <channel-id> --output-format toon   # ⑥ post-mortems for this incident's channel
-fduty change list --since 24h --output-format toon        # ③ correlated changes — by shared labels + time; see reference/change.md
+fduty incident detail   "$ID"                             # ① 详情 + AI summary + alert counts + channel_id
+fduty incident alerts   "$ID"                             # ② contributing alerts (detail's embedded alerts are empty here)
+fduty incident timeline "$ID"                             # ④ timeline  (or `incident feed "$ID"` for the paginated view)
+fduty incident similar  "$ID" --limit 5                   # ⑤ similar past incidents (channel-backed; see Gotchas)
+fduty incident post-mortem-list --channel-ids <channel-id> # ⑥ post-mortems for this incident's channel
+fduty change list --since 24h                              # ③ correlated changes — by shared labels + time; see reference/change.md
 ```
 
 > **Never report a result you didn't fetch.** Do not write "返回空" / "无" / a count for any aspect whose command is **absent from your tool-call history this turn** — write `未查询 — 可运行 <command>` instead. "Empty" is a claim only a command you actually ran can make; inventing it is the worst failure mode of a fault summary.

skills/flashduty/reference/team.md

@@ -6,7 +6,7 @@ Prereq: `SKILL.md` read. **SKILL.md + this card = full competence on teams — n
 
 "团队 / 成员管理 / 创建团队 / 查找团队 / HR同步 / team ID / person ID归属" → **team**. Key IDs:
 - **`team_id` (int64)** — from `fduty team list` or `team get --name`.
-- **`person_id` (int64)** — look up via `fduty member list --query <name-or-email>` (member card, not here).
+- **`--person-ids` inputs are member IDs** — look up via `fduty member list --query <name-or-email>` (member card, not here). The API field is named `person_ids`, but team membership expects member IDs.
 
 NOT this card: on-call schedules (oncall), incidents (incident), channels (channel).
 
@@ -28,7 +28,7 @@ NOT this card: on-call schedules (oncall), incidents (incident), channels (chann
 ```bash
 # 1. Check name doesn't already exist
 fduty team list --name "SRE Platform" --output-format toon
-# 2. Create with initial members (person IDs from member list)
+# 2. Create with initial members (member IDs from member list)
 fduty team create --name "SRE Platform" --description "Site Reliability" \
   --person-ids 1001,1002,1003
 # 3. Verify — note the returned team_id