docs: add CRUD tools (create, update, delete) to forest-mcp skill

Author: alban bertolini

claude-skills/forest-mcp/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: forest-mcp
-description: Query Forest Admin data through MCP tools. Use when the user wants to search, filter, or explore data from their Forest Admin database. Triggers on questions like "find all users", "show orders from last week", "how many products", or any data exploration request.
+description: Query and manipulate Forest Admin data through MCP tools. Use when the user wants to search, filter, explore, create, update, or delete data from their Forest Admin database. Triggers on questions like "find all users", "create a new order", "update user 42", "delete inactive products", or any data operation request.
 ---
 
 # Forest Admin MCP
 
-Query Forest Admin data as if it were a database, with an abstraction layer that handles authentication, filtering, and relationships.
+Query and manipulate Forest Admin data as if it were a database, with an abstraction layer that handles authentication, filtering, and relationships.
 
 ## Available Tools
 
@@ -14,12 +14,16 @@ Query Forest Admin data as if it were a database, with an abstraction layer that
 | `describeCollection` | Get collection schema (fields, types, operators, relations) |
 | `list` | Query records from a collection |
 | `listRelated` | Query records from a one-to-many or many-to-many relation |
+| `create` | Create a new record in a collection |
+| `update` | Update an existing record by ID |
+| `delete` | Delete one or more records by IDs |
 
 ## Workflow
 
-1. **Always start with `describeCollection`** to understand the collection structure before querying
+1. **Always start with `describeCollection`** to understand the collection structure before querying or modifying data
 2. Use `list` for direct collection queries
 3. Use `listRelated` to traverse relationships (e.g., "orders of user 123")
+4. Use `create`, `update`, `delete` for data modifications
 
 ## Filter Syntax
 
@@ -96,9 +100,43 @@ list({
 })
 ```
 
+**"Create a new user"**
+```
+create({
+  collectionName: "users",
+  attributes: {
+    name: "John Doe",
+    email: "john@example.com",
+    status: "active"
+  }
+})
+```
+
+**"Update user 42's email"**
+```
+update({
+  collectionName: "users",
+  recordId: 42,
+  attributes: {
+    email: "newemail@example.com"
+  }
+})
+```
+
+**"Delete inactive users"**
+```
+1. list({ collectionName: "users", filters: { field: "status", operator: "Equal", value: "inactive" } })
+2. delete({
+     collectionName: "users",
+     recordIds: [1, 5, 12]  // IDs from the list result
+   })
+```
+
 ## Tips
 
 - Use `enableCount: true` when user asks "how many" or needs totals
 - Use `fields: ["id", "name"]` to reduce payload when only specific fields needed
 - Use `search` parameter for full-text search across searchable fields
 - Check `isSortable` from describeCollection before using sort
+- For `update`, only include attributes you want to change
+- For `delete`, always confirm with user before deleting multiple records