Delete single or bulk records from BKND entities via SDK or REST API.
npx skills add https://github.com/cameronapak/melos --skill bknd-crud-delete
Please help me install this Agent Skill. Skill: bknd-crud-delete Source: https://github.com/cameronapak/melos/tree/main/.agents/skills/bknd-crud-delete Command: npx skills add https://github.com/cameronapak/melos --skill bknd-crud-delete
This Skill enables safe deletion of records from BKND-backed entities using the SDK or REST API, covering single-record deletions, bulk deletions, soft-delete workflows, and safeguards.
Authenticate, then delete a record with the BKND SDK or REST, and finally verify the record is removed.
High-intent search queries and answers about installing and using this skill.
To delete BKND records, use the deleteOne or deleteMany methods via the SDK or REST API, applying precise filters to target specific records and verifying removal after the request completes.
Yes, bulk deletion is supported through deleteMany, but it requires strict safeguards like applying precise filters to prevent accidental mass removals of unintended BKND records.
Yes, BKND supports soft-delete patterns that mark records as deleted rather than permanently removing them, providing options to restore the records later if needed.
Cascade management handles child records to satisfy foreign key constraints before deleting a parent record, ensuring referential integrity is maintained during the deletion process.
The best way to handle single-record deletion is to use deleteOne with proper validation and error handling, then verify the record is fully removed to confirm a successful response.
You should avoid permanent deletion when future recovery is needed or foreign key constraints require child records to remain intact, opting instead for soft-delete patterns.
cameronapakCreate single or bulk records in Bknd datastores via SDK or REST API.
liuridaDefine one-to-many GORM relationships with foreign keys and association operations.
cameronapakAutomate BKND row-level security configuration with filter policies and ownership rules.
jovermierAnalyze database migrations for referential integrity and transaction boundary issues.
