EverTask

Interactive playbook for integrating the EverTask .NET background-task library into an application: install the right packages, wire up `AddEverTask(...)` with the correct storage/resilience/scheduling/rate-limiting/monitoring options, and scaffold task records + handlers that satisfy the System.Text.Json payload contract (analyzers ET0001–ET0007). Use when the user asks to "add/integrate/set up EverTask", "create a background task / recurring task / scheduled job with EverTask", "configure EverTask storage/retry/rate-limiting/monitoring", or to pick between the SQL Server / PostgreSQL / SQLite / In-Memory storage providers. The skill ASKS the user the decisions it cannot infer (via the AskUserQuestion tool) and reads the matching references/*.md only for the features actually chosen. Do NOT use it to ADD A NEW storage provider package (that is the `new-relational-storage-provider` skill) or to author EverTask's own internals.

Playbook for adding a new EF Core RELATIONAL storage provider to EverTask (MySQL, MariaDB, Oracle, CockroachDB, …) by inheriting EverTask.Storage.EfCore. Use when the user asks to add/scaffold/implement a new database storage provider, port the storage layer to another relational DB, or create an EverTask.Storage.X package. It encodes the repeatable scaffold AND — critically — the MANDATORY per-database verification matrix so the agent never assumes "it just inherits the base": each provider differs on DateTimeOffset/uuid/ExecuteDelete translation, schema concept, identifier casing, and the Phase-2 hot-write mechanism. Do NOT use for the in-memory or a non-EF/NoSQL store (that is the custom-storage path).