Skip to main content
The quiva-config skill teaches a local agent to read and change your QuivaWorks configuration safely. It wraps a small Node script (Node 18 or later, no dependencies) so the agent works through reviewable files and dry runs instead of raw requests.

What it does

It works on record sets, records, spaces, task templates and flows, in any account you have a profile for.

Install it

Install the QuivaWorks plugin, which includes the skill and the MCP connection. See Claude Code.
The script runs against production. Pulled files go to ./.quiva in the directory you run it from. Then add a profile in your own terminal, and check it with profile list and check <name>.

Example prompts

  • “Pull the flow onboarding.welcome from my production profile and show me what it sends.”
  • “Change the subject of the welcome email in that flow, then show me the dry run before applying it.”
  • “Copy the Intake record set from production to sandbox and tell me what is still pointing at the source.”
  • “Which secrets does the renewals flow need that sandbox is missing? Give me the command to set them.”

Safety

Writes are dry runs until you say yes, secrets never pass through the conversation, and the agent is told to ask you to run profile add yourself if a profile is missing. Writing shared secrets needs an admin’s key.