Individual skill
crestapps-core-data-storage
Skill for choosing and registering CrestApps.Core 2.0 persistence. Covers picking Entity Framework Core (CrestApps.Core.Data.EntityCore) or YesSql (CrestApps.Core.Data.YesSql), registering the backing data store on the root builder, per-feature AddEntityCoreStores and AddYesSqlStores calls on the AI suite, personas, chat interactions, document processing, memory, tool instances, A2A, MCP and indexing builders, the service-collection store calls for web crawlers, file sources, knowledge objects and ingestion item state, what the null fallback stores mean, commit boundaries through IStoreCommitter, how configuration and database deployments merge, and writing a custom backend. Use it when a host needs durable profiles, sessions, documents, connections, deployments, or crawler and file-source state.
plugins/crestapps-core/skills/crestapps-core-data-storage/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
- writing Derived category
- data-databases 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
Read excerpt
# CrestApps.Core Data Storage
You are a CrestApps.Core expert. Help the host choose a backend and register exactly the stores each enabled feature needs.
## Guidelines
- Choose Entity Framework Core when the host already uses EF Core or wants any EF relational provider. Choose YesSql when the host wants a document store with collections and map indexes (as Orchard Core does).
- Register the backing store once on the root builder: `.AddEntityCoreSqliteDataStore(...)` / `.AddEntityCoreDataStore(...)`, or `.AddYesSqlDataStore(...)`. The per-feature `Add*Stores()` calls only select stores; they never create the `DbContext` or `IStore`.
- Call the store method on every feature builder you enable. One call does not cover other features.
- Without a store package, connections and deployments come only from configuration and `ISearchIndexProfileStore` falls back to a null store, but nothing registers `IAIProfileStore`, the chat session stores, or the `ChatInteraction` catalog. Register a store before resolving `IAIProfileManager`, chat sessions, or Chat Interactions.
- Every write path needs a commit boundary (`IStoreCommitter`); see `crestapps-core-foundations`.
- Create the schema before serving requests: `InitializeEntityCoreSchemaAsync()` for EF Core, or the `Create*IndexSchemaAsync` extensions for YesSql.
## Entity Framework Core