Feishu Literature Manager

Before installing, ask the author or publisher how Feishu credentials (app_token, app secret, or OAuth) are provided and stored — the registry metadata claims no required env vars but the README/examples clearly need an app_token and the ability to set table permissions. Confirm whether the skill will ask you to paste a writable table URL (and whether that URL actually contains a usable token) or whether you must supply credentials manually. Insist on least-privilege: prefer a Feishu app token limited to only the target table and write scope, not an org-wide admin token. Verify where 'saved state' (PMIDs, batches) will be stored and ensure it won't persist credentials or sensitive data. If you care about data exposure, review the code paths that build feishu_bitable_create_record calls and where tokens/URLs are logged or stored; you may also want the skill to avoid setting 'full_access' automatically and instead request explicit permission for any permission changes. Finally, confirm expected translation service and quota/parallel-call behavior to avoid accidental rate-limits or heavy concurrency that could cause failures or unintended writes.