SKILL.md
How It Works
- NoSQL vs Data Store — If the user is undecided, apply this matrix:
|
Catalyst Data Store |
Catalyst NoSQL |
| Schema |
Fixed, defined upfront |
Flexible, per-item (no uniform structure required) |
| Query |
ZCQL (SQL-like joins and filters) |
Partition key + optional sort key |
| Data type |
Structured, relational rows |
Unstructured/semi-structured, JSON-format |
| Priority |
ACID compliance, complex queries |
High scalability, high write throughput |
Rule: If the user says "ZCQL", "join", "relational", or "fixed schema" — stop and load catalyst-datastore instead.
- Load
references/nosql-basics.md — for SDK operations (insertItems, fetchItem, updateItems, deleteItems, queryTable) and the NoSQLItem builder.
- Answer — Provide the SDK method call with the correct table name, partition-key attribute, and
NoSQLItem construction.
Triggers
Use this skill for: "NoSQL", "document storage", nosql.table, insertItems, fetchItem, updateItems, deleteItems, queryTable, NoSQLItem, "NoSQL vs Data Store", "flexible schema", "Catalyst document database", "schemaless data on Catalyst", or "nested objects in Catalyst".
References
| Reference |
Load when the query is about… |
references/nosql-basics.md |
SDK operations (insertItems, fetchItem, updateItems, deleteItems, queryTable), NoSQLItem builder, partition-key model, NoSQL vs Data Store decision table |