mutate_data

Name: mutate_data
Availability: InStock
Author: Devforth

Create, update, or delete records with explicit user confirmation.

1|Updated Apr 13, 2026

Search Tags:#crud #data-integrity #auditable #records #confirmations #mutate #start_custom_action

Ready to run

npx skills add https://github.com/devforth/adminforth-agent --skill mutate-data

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mutate_data
Source: https://github.com/devforth/adminforth-agent/tree/main/custom/skills/mutate_data
Command: npx skills add https://github.com/devforth/adminforth-agent --skill mutate-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mutating data across resources can lead to unintended changes. This Skill provides a structured workflow that fetches the target record, presents key fields for validation, and requires explicit confirmation before performing create, update, or delete mutations or resource actions.

Core Features & Use Cases

Create, update, or delete records with explicit user confirmation before any mutation.
Use start_custom_action and start_custom_bulk_action to trigger resource actions when appropriate.
Fetch the target record and display key fields to ensure the correct row is mutated, preserving data integrity and traceability.

Quick Start

Ask me to update, create, or delete a specific record by first fetching it and confirming the exact changes before performing the mutation.

Frequently Asked Questions about mutate_data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely update or delete records without risking unintended data changes?▼

Safe record mutations require fetching the target data first to validate key fields, then enforcing explicit user confirmation before applying any create, update, or delete operations to preserve data integrity.

What is the best way to perform bulk data mutations across different resources?▼

Bulk data mutations across resources can be performed using start_custom_bulk_action, which applies action-based hooks to execute mass updates or deletes securely while maintaining an auditable trace of changes.

Can I trigger custom resource actions for both single and bulk record updates?▼

Yes, custom resource actions for single and bulk record updates can be triggered using start_custom_action and start_custom_bulk_action, allowing flexible CRUD workflows with required confirmations.

Does mutating data with confirmation flows prevent accidental record deletion?▼

Mutating data with confirmation flows prevents accidental record deletion by fetching the target row first, displaying its key fields for validation, and requiring explicit approval before executing the destructive operation.

Why does my CRUD workflow need fetch-before-mutation validation?▼

Fetch-before-mutation validation in CRUD workflows ensures the correct row is targeted by displaying key fields before changes are applied, preventing unintended modifications and preserving traceability for auditable records.

When should I not use built-in confirmation flows for CRUD operations?▼

Built-in confirmation flows for CRUD operations should be bypassed when executing automated, non-interactive background tasks where explicit user approval is unavailable and automated data mutations are required.