Feishu Bitable Data Sync
v1.0.0Feishu Bitable Data Sync - Sync data between multiple bitables or external sources. **Features**: - Sync data between two bitables - Import data from externa...
⭐ 0· 106·0 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the runtime instructions (list, query, batch_create/update/delete, conflict resolution, CSV import). All referenced capabilities are Feishu Bitable operations; there are no unrelated environment variables or binaries requested.
Instruction Scope
SKILL.md stays focused on Feishu Bitable actions and sync patterns. It assumes the presence of platform connector tools (feishu_bitable_app, feishu_bitable_app_table, feishu_bitable_app_table_record) and that the agent will be given app_token and table_id inputs; it does not instruct reading arbitrary local files or unrelated env vars. The doc shows CSV import examples but does not include explicit instructions for securely obtaining or storing tokens.
Install Mechanism
No install spec and no code files — this is instruction-only, which minimizes risk from downloads or executed installers.
Credentials
The skill does not declare required environment variables, but the instructions require Feishu app_token values and table/record identifiers to operate. That is proportional to its purpose, but the SKILL.md does not describe how tokens are supplied to the agent or stored, so operators should confirm token handling and scope.
Persistence & Privilege
always:false (default) and user-invocable:true — the skill does not request forced or persistent inclusion. It also does not attempt to modify other skills or system-wide settings.
Assessment
This skill is a descriptive guide for syncing Feishu Bitable data and appears coherent. Before using it: (1) Confirm your agent environment provides the Feishu connector tools referenced (feishu_bitable_app*). (2) Provide app_token and table_id only when needed and ensure tokens have least-privilege scopes (read/write limited to the relevant tables). (3) Test syncs on a sample/staging table first and back up data before running batch updates/deletes. (4) Verify how tokens will be stored or passed to the agent (avoid embedding long-lived credentials in chat history). (5) Check the conflict-resolution logic and mappings (field types and person IDs) to avoid accidental data corruption. If you need the skill to run autonomously, restrict the token permissions and set clear safeguards (dry-run, limits, confirmation prompts).Like a lobster shell, security has layers — review code before you run it.
bitablevk9797cmxfyqy3nqagr1801xnp983z7j8datavk9797cmxfyqy3nqagr1801xnp983z7j8feishuvk9797cmxfyqy3nqagr1801xnp983z7j8latestvk9797cmxfyqy3nqagr1801xnp983z7j8syncvk9797cmxfyqy3nqagr1801xnp983z7j8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.