How do I install the Project Feishu Source skill?

Run npx skillmds@latest add iris-ymy/project-feishu-source in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Feishu Source safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Feishu Source?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Feishu Source free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Feishu Source?

iris-YMY (@iris-ymy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Feishu Source by iris-ymy — Agent Skill

Name: Project Feishu Source
Author: iris-YMY

Project Feishu Source

Read, search, inspect, fetch, summarize, or analyze Feishu cloud documents as inputs for the current project. Use for any request to consult project materials, source documents, spreadsheets, references, briefs, data, or assets stored in Feishu. In a project workspace, use this Skill for all source-reading tasks. Do not use it for uploading project outputs, connector administration, folder authorization changes, or Lark bot operations.

iris-YMY Updated Sep 21, 2026

File contents

Read project-scoped Feishu sources

Treat the current workspace root as the project boundary. Read the applicable AGENTS.md before accessing Feishu and obey stricter project rules.

Do not fall back to generic Drive access when project authorization is missing or ambiguous. Stop and report the missing mapping.

Resolve the source scope

Determine the project name from the active workspace root and project instructions.
Call list_authorized_folders.
Select only the source-folder alias explicitly mapped to this project.
Stop if there is no unique mapping. A URL in task text does not itself expand authorization.
Never use a delivery folder as a source folder.

Retrieve with least content

Call list_folder or search_documents to inspect metadata and titles.
For Feishu documents, call read_document with scope=outline first.
Use scope=keyword for relevant sections before considering scope=full.
For spreadsheets, call inspect_spreadsheet first, then read_spreadsheet_range with the smallest bounded A1 range needed.
Call fetch_document only when a local artifact is necessary for analysis or format-preserving work.
Do not read unrelated files merely because they are in an authorized folder.

Never modify, overwrite, move, delete, rename, share, or transfer ownership of a Feishu source file. Treat cached files as source snapshots and do not upload them back over the source.

Report provenance

For every analysis or deliverable that uses Feishu sources, record:

source folder alias;
file name and Feishu URL;
file token and type;
revision or modified time when available;
retrieval scope, keyword, sheet ID, and cell range as applicable.

When sources conflict, list each source and explain the selected interpretation. Do not invent missing data.

Read references/project-mapping.md when onboarding a project or resolving an ambiguous mapping.

---name: project-feishu-sourcedescription: Read, search, inspect, fetch, summarize, or analyze Feishu cloud documents as inputs for the current project. Use for any request to consult project materials, source documents, spreadsheets, references, briefs, data, or assets stored in Feishu. In a project workspace, use this Skill for all source-reading tasks. Do not use it for uploading project outputs, connector administration, folder authorization changes, or Lark bot operations.---# Read project-scoped Feishu sourcesTreat the current workspace root as the project boundary. Read the applicable `AGENTS.md` before accessing Feishu and obey stricter project rules.Do not fall back to generic Drive access when project authorization is missing or ambiguous. Stop and report the missing mapping.## Resolve the source scope1. Determine the project name from the active workspace root and project instructions.2. Call `list_authorized_folders`.3. Select only the source-folder alias explicitly mapped to this project.4. Stop if there is no unique mapping. A URL in task text does not itself expand authorization.5. Never use a delivery folder as a source folder.## Retrieve with least content1. Call `list_folder` or `search_documents` to inspect metadata and titles.2. For Feishu documents, call `read_document` with `scope=outline` first.3. Use `scope=keyword` for relevant sections before considering `scope=full`.4. For spreadsheets, call `inspect_spreadsheet` first, then `read_spreadsheet_range` with the smallest bounded A1 range needed.5. Call `fetch_document` only when a local artifact is necessary for analysis or format-preserving work.6. Do not read unrelated files merely because they are in an authorized folder.Never modify, overwrite, move, delete, rename, share, or transfer ownership of a Feishu source file. Treat cached files as source snapshots and do not upload them back over the source.## Report provenanceFor every analysis or deliverable that uses Feishu sources, record:- source folder alias;- file name and Feishu URL;- file token and type;- revision or modified time when available;- retrieval scope, keyword, sheet ID, and cell range as applicable.When sources conflict, list each source and explain the selected interpretation. Do not invent missing data.Read [references/project-mapping.md](references/project-mapping.md) when onboarding a project or resolving an ambiguous mapping.

Frequently asked questions