Individual skill
orchardcore-ai-file-sources
Skill for CrestApps AI File Sources in Orchard Core 4.0 (CrestApps.OrchardCore 3.0). Covers ingesting a folder of files on a schedule into a File AI data source, the per-tenant file-sources folder of the local connector, the FTP, FTPS and SFTP connectors, figure description with the vision slot and the utility slot, the File Source Ingestion background task and Read now, the CrestApps AI FileSources configuration section with FileSourceOptions, the AIFileSources admin list, the ManageFileSources permission, and custom ingestion connectors. Use it for CrestApps.OrchardCore.AI.FileSources, CrestApps.OrchardCore.AI.FileSources.Ftp, CrestApps.OrchardCore.AI.FileSources.Sftp, FileSource, FileSourceMetadata, FileSystemFileSourceMetadata, RemoteFileSourceMetadata, FtpConnectionMetadata, SftpConnectionMetadata, FigureProcessingMode, ITenantFileSourceRoot, IIngestionConnector, AddCoreIngestionConnector, IIngestionRunService, and FileSourceRunBackgroundTask.
plugins/crestapps-orchardcore/skills/orchardcore-ai-file-sources/SKILL.md
Source commit d86d04f234b1b2bd8145368a2544490f9d557596
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 13
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai Repository topic
- ai-agents-framework Repository topic
- dotnet Repository topic
- mcp Repository topic
- mcp-server Repository topic
- orchardcore Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytesSKILL.mdcore · 11,334 bytes
Read excerpt
# Orchard Core AI File Sources
## Ingest folders of files into the AI knowledge base
You are an Orchard Core expert. Generate configuration and code for CrestApps file sources: a **file source** reads a folder on a schedule and ingests every file into a **File** AI data source, storing each file's text, figures, charts, and tables as separately retrievable knowledge. AI profiles attached to that data source answer from the folder and can cite the figure they used.
### Guidelines
- Use file sources for files that already live somewhere (a server folder, an FTP drop, an SFTP export). Files users upload in a chat belong to AI Documents (see `orchardcore-ai-documents`).
- `CrestApps.OrchardCore.AI.FileSources` depends on `CrestApps.OrchardCore.AI.DataSources` and `CrestApps.OrchardCore.AI.Documents`, and ships the local file-system connector.
- The FTP and SFTP features only add ingestion connectors. They do not start an MCP server; the MCP FTP and SFTP resource features are separate (see `orchardcore-ai-mcp-resources`).
- A file source targets a **File** data source, which needs a knowledge base index with an embedding deployment (see `orchardcore-ai-data-sources`).
- The local connector can only read the tenant's own `App_Data/Sites/{TenantName}/file-sources` folder. That root is computed from the tenant identity and cannot be widened by configuration or by a request.
- Figures are described only when a deployment declaring `imageInput` fills the `vision` slot, or is named on the source.