Menu
Native Microsoft Dynamics 365 Dataverse operations (tables and rows) with read/write support.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | dynamics |
| description | Native Microsoft Dynamics 365 Dataverse operations (tables and rows) with read/write support. |
Native Dataverse API operations for environments, tables, and rows.
DYNAMICS_ACCESS_TOKEN - OAuth access tokenDYNAMICS_INSTANCE_URL - Selected Dataverse instance URL (for example: https://contoso.crm.dynamics.com)# Inspect schema
dynamics tables list [--top 50]
dynamics tables get <logicalName>
# Read rows
dynamics rows list <tableLogicalName> [--select col1,col2] [--filter "statecode eq 0"] [--orderby "modifiedon desc"] [--top 25]
dynamics rows get <tableLogicalName> <rowId> [--select col1,col2]
# Write rows
dynamics rows create <tableLogicalName> '{"name":"Acme"}'
dynamics rows update <tableLogicalName> <rowId> '{"name":"Acme Updated"}'
dynamics rows delete <tableLogicalName> <rowId>
# Identity helper
dynamics whoami
Guides agents through isolated Git worktree setup, lifecycle commands, process cleanup, and per-worktree local development state. Use when creating, starting, stopping, inspecting, cleaning up, or troubleshooting Git worktree development environments or when a repository includes a worktree lifecycle CLI.
Continuously watch and fix release main CI until the branch is fully green and verified working. Use when asked to babysit CI, babysit CI release, monitor release main, run /loop for CI, run /goal until checks pass, or keep iterating until release main is green.
Fix flaky tests by repeatedly running the suite, collecting intermittent failures, and proving stability. Use when asked to fix flaky tests or require repeated/consecutive green test runs.
Manage LinkedIn messaging, profiles, posts, connections, and company pages via Unipile. Use for networking, content publishing, and lead engagement.
Scoped commit workflow with a bundled committer script that prevents accidental broad staging. Use when the user asks to commit, commit all, create a git commit, or handle commit-time staging in this repository.
Systematically QA a web application like a real user, triage issues by severity, fix scoped bugs when asked, verify fixes with evidence, and report ship readiness. Use when asked to QA, test a site or app, find bugs, test and fix, or check whether a feature works.