docs: clarify bitable import routing to drive +import

[liujinkun2025]

Summary

Clarify the agent guidance for Base import scenarios so local file imports to Base/bitable are routed to lark-cli drive +import --type bitable instead of lark-base. This reduces a recurring misread where agents jump into Base table operations
before completing the Drive import step.

Changes

• Strengthen lark-drive skill and drive +import docs to explicitly state that local Excel/CSV -> Base/bitable imports belong to drive +import --type bitable
• Add reverse guidance in lark-base docs and templates so Base skills redirect local file import requests back to drive +import
• Remove misleading "导入" wording from Base examples metadata and clarify that Base examples start after import is already complete

Test Plan

• Unit tests pass
• Manual local verification confirms the lark xxx command works as expected
• Docs-only change; verified the updated routing guidance is present in lark-drive, lark-base, and the corresponding skill templates

Related Issues

• None

Summary by CodeRabbit

• Documentation
  • Enhanced guidance for importing local Excel/CSV files into Base/multi-dimensional tables with clarified command sequences.
  • Improved workflow documentation specifying which tools to use before and after import completion.
  • Updated decision trees and intent-to-command mappings to prevent confusion and ensure accurate tool routing.
  • Added important notes and examples clarifying the proper import workflow.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e8982aaf-59f3-4e41-b0a5-fc1de2e1fb5c

📥 Commits

Reviewing files that changed from the base of the PR and between e64d245 and d1926f1.

📒 Files selected for processing (5)

• skill-template/domains/base.md
• skill-template/domains/drive.md
• skills/lark-base/SKILL.md
• skills/lark-drive/SKILL.md
• skills/lark-drive/references/lark-drive-import.md

---

📝 Walkthrough

Walkthrough

This PR clarifies routing rules for importing local files into Base/multi-dimensional tables (bitable) across multiple skill and domain documentation files. The core change enforces that local-file imports must initiate with lark-cli drive +import --type bitable before any Base operations, rather than starting with Base commands.

Changes

Cohort / File(s)	Summary
Base skill domain skill-template/domains/base.md, skills/lark-base/SKILL.md	Added explicit routing rules and forbidden behaviors to prevent misclassification of local-file imports as in-Base operations (+base-create, +table-create, +record-upsert). Updated intent→command index mapping to clarify the import stage belongs to drive, not base.
Drive skill domain skill-template/domains/drive.md, skills/lark-drive/SKILL.md	Expanded skill scope to cover local file imports into Feishu formats (docx/sheet/bitable). Added "快速决策" guidance section clarifying that lark-cli drive +import --type bitable is the entry point for Base/bitable imports, with subsequent operations deferred to lark-base.
Drive import reference skills/lark-drive/references/lark-drive-import.md	Added IMPORTANT guidance blocks and example commands (e.g., Excel to bitable with --type bitable). Clarified that CLI term mapping "Base/多维表格/bitable" translates to --type bitable during command execution.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

Possibly related PRs

• feat: support importing documents larger than 20MB #220: Related PR that implements/updates drive import behavior and documentation for the local-file→Base/bitable import flow that this PR documents and enforces through routing rules.

Suggested labels

domain/base, domain/ccm

Suggested reviewers

• fangshuyu-768
• zhouyue-bytedance

Poem

🐰 A rabbit hops through the routing maze,
"Drive first!" it cheers with eager gaze,
Import those files to bitable land,
Then base commands close at hand,
No confusion now—the path is clear! 📋✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main objective: clarifying bitable import routing to drive +import, which aligns with the core changes across all modified files.
Description check	✅ Passed	The description follows the template structure with Summary, Changes, and Test Plan sections. All major changes are documented, and testing approach is clearly outlined.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/route-bitable-import-to-drive-import

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This docs-only PR adds explicit routing guidance so agent models know to use lark-cli drive +import --type bitable for local file → Base/bitable imports, rather than jumping straight into lark-base table operations. Changes span the lark-drive and lark-base SKILL.md files, the shared skill-template domain partials, and the lark-drive-import.md reference document. The updates are consistent and well-placed across all five files.

Confidence Score: 5/5

Safe to merge — docs-only change with consistent, well-placed routing guidance across all five files.

All remaining findings are P2 or lower (one suggestion to also update the lark-base description metadata). The routing guidance is correctly stated and consistent across every changed file, and no code or schema changes are involved.

skills/lark-base/SKILL.md — consider updating the description metadata field to also exclude local-import routing at the skill-selection layer.

Vulnerabilities

No security concerns identified. This is a documentation-only change with no code execution, authentication, or data handling modifications.

Important Files Changed

Filename	Overview
skills/lark-drive/SKILL.md	Updated description metadata to claim bitable imports; added a new "快速决策" section that lists import routing rules before any other content.
skills/lark-base/SKILL.md	Added routing redirect at the top-level preconditions block, first item of quick-execution order, "禁止行为" list, command index, and updated examples.md link text to drop "导入"; description metadata not changed.
skills/lark-drive/references/lark-drive-import.md	Added [!IMPORTANT] callout at the top and below the file-type table; added concrete bitable import example; clarified that "Base/多维表格/bitable" all map to --type bitable.
skill-template/domains/base.md	Added routing rule #9 to core rules, a new row in the intent→command index, and a header-level routing callout; removed "导入" from examples link.
skill-template/domains/drive.md	Added a routing-note blockquote at the top of "核心概念" directing bitable imports to drive +import.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User request: import local file to Base/bitable] --> B{File type?}
    B -->|.xlsx / .csv| C[lark-cli drive +import --type bitable]
    B -->|.xlsx / .xls / .csv| D[lark-cli drive +import --type sheet]
    B -->|.md / .docx / .doc / .txt / .html| E[lark-cli drive +import --type docx]
    C --> F[Import complete → get token/url]
    F --> G[lark-cli base +... for table operations]
    D --> H[Sheet ready]
    E --> I[Doc ready]

    style C fill:#d4edda,stroke:#28a745
    style G fill:#cce5ff,stroke:#004085
    style B fill:#fff3cd,stroke:#856404

Loading

Comments Outside Diff (1)

1. skills/lark-base/SKILL.md, line 4 (link)

   Description metadata doesn't exclude local-import routing

   The description field is typically what a skill-router reads to decide which skill to activate before opening the SKILL.md body. Because it still lists "建表" without noting that local-file → bitable imports belong to lark-drive, an agent that scores skills by description alone could still pick lark-base for an import request and only encounter the redirect once it reads the body.

   Adding a short exclusion to the description (e.g. "不含本地文件导入到 Base — 该场景请使用 lark-drive") would close this gap at the selection layer, complementing the body-level routing guidance already added.

_{Reviews (1): Last reviewed commit: "route base import guidance to drive +imp..." | Re-trigger Greptile}

[github-actions]

🚀 PR Preview Install Guide

🧰 CLI update

npm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@d1926f119f8b0b8be6caa727fd1611616a52db77

🧩 Skill update

npx skills add larksuite/cli#docs/route-bitable-import-to-drive-import -y -g