Skip to main content
skill CX Codex

ae-data-integration — Claude Code skill: import files and sheets into AE

Moves a local file or a Feishu sheet into AE along one pipeline: reads the source's business meaning, drafts a tracking plan for confirmation, turns rows into UE records and uploads.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-data-integration -a claude-code
Open on GitHub

What ae-data-integration does

The skill runs four submodules in order: Source, Tracking plan, Transform, Sink. It profiles the whole file first and infers what the data means for the business. A tracking plan comes next, and a human has to confirm it before anything is ingested. Only then do rows become UE records headed for the receiver. A file sitting on disk is not a reason to upload it.

Accepted inputs are CSV, TSV, TXT, JSON, JSONL (NDJSON), XLS and XLSX, plus Feishu sheet and Bitable (多维表格) URLs. For those URLs the skill checks the lark-cli environment itself — installed, logged in, access granted — and snapshots the document locally: XLSX for sheets, JSONL for Bitable. Tencent Docs, DingTalk, WPS, Google Sheets and Notion have no CLI read path, so you export those yourself.

Local analysis is available too, with nothing sent anywhere. Handing a file to AE Agent is a separate branch and caps at 50 MB per file. Uploads are not idempotent: every data-integration upload run submits to the receiver again, so do not re-run it just to look at a response — read the saved JSON from the first run. A batch that times out or drops the network counts as unknown, and resuming it automatically is off the table.

What it helps with

  • load a local CSV or Excel file into AE without hand-building requests
  • work out what a file means for the business before ingesting it
  • snapshot a Feishu sheet or Bitable into a local file
  • turn rows into UE records against a confirmed tracking plan
  • inspect a dataset locally without uploading it

Example prompts for the agent

  • Import orders.csv into AE and show me the tracking plan first
  • Analyze events.jsonl locally, do not upload anything
  • Pull the sheet from this Feishu link and get it ready for AE

How to install ae-data-integration

1Skills CLI (Vercel)

npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-data-integration -a claude-code

2Manually: put the files in place

~/.claude/skills/ae-data-integration/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ae-data-integration/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ae-data-integration

How do I install ae-data-integration in Claude Code?

Run npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-data-integration -a claude-code. The skill lands at ~/.claude/skills/ae-data-integration/SKILL.md.

What does ae-data-integration do?

It takes a local file or a Feishu sheet through four stages: source meaning, tracking plan, row-to-UE-record conversion and upload. It can also analyze a file locally without sending it.

Which file formats does it accept?

CSV, TSV, TXT, JSON, JSONL (NDJSON), XLS and XLSX, plus Feishu sheet and Bitable URLs. The URL paths need a working lark-cli with access to the document.

Similar skills

All skills for Data and databases →

From the same set17

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor