Debugging Mutations

Organization

serac-labs

debugging-mutations

Verify what changed on a ServiceNow instance after a tool call — sys_audit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.

Overview

Publisher	serac-labs
Repository	`serac`
Skill name	`debugging-mutations`
Stars	78
Forks	26
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by serac-labs on GitHub. Read the source before you install it.

Installation

Install the Debugging Mutations AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/serac-labs/serac.git /tmp/serac
mkdir -p .claude/skills
cp -r /tmp/serac/packages/skills/debugging-mutations .claude/skills/debugging-mutations

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Debugging Mutations in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Debugging Mutations on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Debugging Mutations is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Debugging & Mutation Inspection

When you've executed a tool against a ServiceNow instance and need to verify what actually happened — or diagnose why something didn't — these tools answer "what really changed and why". Use them after the fact, never as a substitute for picking the right tool in the first place.

Available debugging tools

Tool	Purpose
`snow_inspect_mutations`	Inspect record changes (INSERT/UPDATE/DELETE) since a timestamp via `sys_audit`
`snow_get_logs`	Query platform logs with a time filter. Pass `log_table` to switch source: `syslog` (default), `syslog_app_scope` (scoped-app log), `syslog_transaction` (HTTP transactions), `sys_script_execution_history` (background-script traces)
`snow_session_context`	Dump the authenticated user, roles, current update set, domain. Use before ACL-sensitive debugging — "is this failing because I lack a role?"
`snow_get_script_output`	Output of previously executed scripts
`snow_trace_execution`	Server-side script execution tracing
`snow_get_flow_execution_logs`	Flow Designer execution history
`snow_get_inbound_http_logs`	Inbound REST API call logs
`snow_get_outbound_http_logs`	Outbound REST API call logs
`snow_audit_trail_analysis`	Audit trail analysis with anomaly detection
`snow_manage_flow` (with `verify=true`)	Verify a Flow Designer mutation immediately after running it

Self-debugging workflows

Table API / REST changes (captured by sys_audit)

Note the current timestamp before the action — or use a relative window like "30s"
Execute the tool you want to verify
Call snow_inspect_mutations with since=<timestamp> or since="30s"
Review which records were INSERT/UPDATE/DELETE, which fields changed, old → new values
Compare expected vs. actual and adjust the calling code

Flow Designer (NOT captured by sys_audit)

Flow Designer uses GraphQL mutations against sys_hub_* tables, which sys_audit does not record. Use the Flow Designer tool's own verification path instead:

Pass verify=true to any snow_manage_flow mutation action — you get automatic post-mutation verification
After publishing, call snow_manage_flow action=check_execution flow_id=<id> to inspect execution contexts, runs, and outputs
check_execution returns state, status, timing, errors, and output values from sys_flow_context, sys_hub_flow_run, and sys_hub_flow_output

Picking the right tool

Symptom	Tool to reach for
Script error	`snow_get_logs` with `level="error"`
Scoped-app log output	`snow_get_logs` with `log_table="syslog_app_scope"`
`snow_execute_script` ran, output lost	`snow_get_script_output` with the `execution_id` — see `background-script-execution`
A human's Scripts - Background run, output lost	`snow_get_logs` with `log_table="sys_script_execution_history"` (only holds runs where "Record for rollback?" was ticked; never holds a Serac execution)
Permission-denied / unexpected 403	`snow_session_context` to verify caller's roles + update set
Did the flow mutation work?	`snow_manage_flow` with `verify=true`
What's the flow execution status?	`snow_manage_flow action=check_execution`
What did the Table API actually change?	`snow_inspect_mutations` with a time window
Operation FAILED — what happened?	`snow_inspect_mutations` with `include_syslog=true` and `include_transactions=true`
Flow never started?	`snow_get_flow_execution_logs`
Outbound REST call failed?	`snow_get_outbound_http_logs`
Who did what when?	`snow_audit_trail_analysis`

Important caveats

GraphQL mutations (Flow Designer) are NOT captured by sys_audit — never expect to see them via snow_inspect_mutations. Use verify=true and check_execution instead.
sys_audit only captures successful Table API / REST record changes. Failed operations leave no audit trail.
For failed operations, check syslog (errors) and sys_transaction_log (HTTP 4xx/5xx responses).
sys_audit field values are limited to 255 characters — snow_inspect_mutations warns when values appear truncated.
Use snapshot_record to fetch the current state of a record alongside the audit trail when you need the full picture.
Use the tables filter to focus on specific tables and reduce noise when there's a lot of activity on the instance.

Don't use these tools as a crutch

Debugging tools verify, they don't replace getting it right the first time. If you find yourself reaching for snow_inspect_mutations after every call, the underlying issue is usually:

Picking snow_execute_script with raw GlideRecord instead of a dedicated tool
Using placeholders ("pending", "TBD") where real sys_ids are required
Skipping the Update Set, so changes were tracked into the wrong place

Fix the upstream pattern, then use these tools sparingly for the genuinely unclear cases.

Frequently asked questions

What does the Debugging Mutations AI skill do?

Verify what changed on a ServiceNow instance after a tool call — sys_audit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.

Why use Debugging Mutations on TypingMind?

Because you install it once and use it with any model. Debugging Mutations is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Debugging Mutations in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/serac-labs/serac/tree/main/packages/skills/debugging-mutations. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Debugging Mutations?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Debugging Mutations?

As many as you like. As long as a model supports skills, you can use Debugging Mutations with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Debugging Mutations AI skill free?

Yes. It is published on GitHub by serac-labs under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Using Superpowers

obra

CommunityPopular

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Verification Before Completion

obra

CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

Writing Plans

Use when you have a spec or requirements for a multi-step task, before touching code

Ask Matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Debugging & Mutation Inspection

Available debugging tools

Self-debugging workflows

Table API / REST changes (captured by sys_audit)

Flow Designer (NOT captured by sys_audit)

Picking the right tool

Important caveats

Don't use these tools as a crutch

Frequently asked questions

Related AI Skills

Set up your own AI workspace now