SuperAPI AI Directory

feishu-cli-data

Office & productivity

View repository

Updated 10-16 01:48

About this skill

Feishu Sheets and Bitable

After loading the workflow, resolve the references/、scripts/、templates/、examples/ relative paths according to the workflow.md directory they are in; when executing scripts, use the resolved actual paths and do not rely on the current shell directory.

Routing

Intent Read file
Sheet filter views and conditions, dropdown menus, floating images / cell images, batch styles, and the decision points for all sheet commands references/workflows/sheet/workflow.md
Sheet creation and metadata, read/write/append,table-get / table-put type fidelity, row/column and subtable management, find and replace, filtering, protection, Markdown conversion both ways references/workflows/sheet/workflow.md, then read references/workflows/sheet/references/basic-commands.md
Bitable/Base link parsing (resolve, block), tables, fields, records (including attachments, batch, pagination), views and view configuration, data-query references/workflows/bitable/workflow.md
Bitable roles and collaborators, advanced permissions, workflows, dashboards and chart blocks, forms and sharing references/workflows/bitable/workflow.md

Execution rules

  1. /wiki/ For links or tokens of unknown type, first use drive inspect --url to parse; for Bitable links use bitable resolve(?table= is not necessarily a data table, /record/, and form share links also cannot be split directly)./sheets/ is a Sheet,/base/ is a Bitable.
  2. Table parameters and --base-token can both be passed links directly (including /spreadsheets/, knowledge base /wiki/)。
  3. Identity: when Sheet does not pass --as , User is preferred; if unavailable, warn and fall back to Bot; Bitable defaults to --as auto. For cron / unattended, explicitly --as bot; --as bot reporting 91403 means the Bot is not a collaborator; add the Bot as a collaborator according to the workflow, and do not repeatedly switch tokens.
  4. The Sheet range prefix can be written as sheetId or subtable name (Sheet1!A1); with multiple subtables, the prefix or --sheet-id/--sheet-namemust be included. Row/column commands --range "3:5" are 1-based and inclusive on both ends,--start/--end is 0-based and excludes end; before deleting rows/columns/subtables, first --dry-run to verify the actual row numbers.
  5. Write long IDs and leading-zero encodings as JSON strings (numbers over about 15 digits will be rounded);table-put for numeric columns, dtype uses int64 / float64(number is invalid and will be written as text). sheet find/replace must include --range。
  6. Bitable writes use the base/v3 structure: field JSON top level type, do not wrap field / property;record batch-create use create_records or fields+rows, not v1's records. Before writing, first verify field types and options with a small number of records.
  7. Boolean flags are written as --flag or --flag=false, do not write --flag false(it will be treated as true). Deleting tables/fields/records/views has no confirmation gate, and takes effect immediately upon execution;form field delete by default deletes the field together with the entire column of data; to remove only the question, use --keep-field。
  8. Sheet cell images use sheet image write-image(single) / write-batch(batch), do not use =IMAGE() formulas or Markdown image syntax.

When delete or overwrite commands return exit code 10, confirm the target and impact with the user, then append the global --yes Rerun, do not add on your own. For identity or scope errors (such as 99991663/99991668/99991672/99991679), read ../feishu-cli-platform/references/workflows/auth/references/identity.md; to determine success or failure, write scripts, or handle confirmation gates, read ../feishu-cli-platform/references/workflows/auth/references/agent-contract.md。