add-data-source

Name: add-data-source
Availability: InStock
Author: IntelliTect

Create custom Coalesce data sources by overriding GetQuery and TransformResults.

Updated Apr 27, 2026

Search Tags:#scoping #security #entity #filter #data-source #coalesce

Ready to run

npx skills add https://github.com/IntelliTect/IntelliPlugins --skill add-data-source-intellitect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-data-source
Source: https://github.com/IntelliTect/IntelliPlugins/tree/main/plugins/coalesce-accelerator/skills/add-data-source
Command: npx skills add https://github.com/IntelliTect/IntelliPlugins --skill add-data-source-intellitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create data sources that filter, shape, or scope entity data beyond the default API, enabling secure, domain-specific access.

Core Features & Use Cases

Custom data source: Implement Coalesce IDataSource<T> to apply project-specific filtering and projections.
Context-aware scoping: Bind to the current user or tenant to enforce access rules.
Extend and compose: Integrate with base data sources to preserve default behavior while adding new behavior.

Quick Start

Create a new class with Coalesce that overrides GetQuery and, optionally, TransformResults to expose a custom data source.

Frequently Asked Questions about add-data-source

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a custom data source in Coalesce to filter entity data?▼

Create a custom Coalesce data source by implementing a class that overrides GetQuery in a StandardDataSource<T> to apply project-specific filtering, and optionally add TransformResults to shape the projected entity data.

How do I enforce tenant-scoped or user-scoped access controls on my API data?▼

Enforce tenant-scoped or user-scoped access controls by binding a custom Coalesce data source to the current context, overriding GetQuery to filter entity records based on the current user or tenant authorization rules.

Can I extend the default Coalesce data source without losing the original query behavior?▼

You can extend the default Coalesce data source by integrating with base data sources, preserving the original query behavior while composing new custom filtering and projection logic for your specific domain requirements.

What is the best way to organize custom Coalesce data source classes for maintainability?▼

The best way to organize custom Coalesce data source classes for maintainability is to place them within a dedicated DataSources/ folder, keeping your entity filtering and scoping logic separated from the main domain models.

Does Coalesce support projection-based access controls for entity data?▼

Coalesce supports projection-based access controls by utilizing the TransformResults method within a custom data source, allowing you to shape and restrict the specific entity data fields returned beyond the default API.

Why do I need a custom data source instead of using the default API query?▼

You need a custom data source instead of the default API query when your software project requires precise domain-specific filtering, secure tenant-scoping, or custom projections that the default Coalesce entity API cannot enforce.