← Kantata OX Expertise EngineCONTENT HISTORY
WHAT CHANGED
Update to Kantata OX Expertise Engine
Snapshot Nov 17, 2026 · 00:14 UTC · version 0.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Kantata OX Expertise Engine and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when working with Kantata OX projects, tasks, resource planning, time entries, timesheets, expenses, or project reporting through the connected Kantata OX App.",
"included_files": [],
"name": "kantata-workflows",
"skill_md_contents": "---\nname: kantata-workflows\ndescription: Use when working with Kantata OX projects, tasks, resource planning, time entries, timesheets, expenses, or project reporting through the connected Kantata OX App.\n---\n\n# Kantata workflows\n\nUse the connected Kantata OX App and its actual tool schemas. Discover available tools before choosing an action; do not assume a tool exists merely because a workflow is described here. Respect the authenticated user's permissions and the server's operating notes.\n\n## Dates and terminology\n\nA Kantata work week runs Sunday through Saturday. Interpret \"this week\" as the Sunday on or before today through the following Saturday, and \"last week\" as the preceding seven days. Use the user's timezone and state the date range in time-based reports.\n\nKantata API workspaces are projects; stories are tasks. Workspace allocations describe resource planning. Resolve named projects, tasks, and people to verified IDs through read tools before mutations. Ask when multiple plausible matches remain.\n\n## Retrieve and report\n\nChoose narrow filters and only the associations needed. Follow pagination until the requested scope is complete; if incomplete, state that limitation rather than presenting partial totals as complete. Kantata responses can index objects by ID in top-level collections and order references in a results array; resolve those references before summarizing. Distinguish actual time from planned hours and approved or submitted time from unsubmitted time. Preserve currency and billable status when aggregating financial values.\n\nFor project reviews, retrieve the relevant projects and tasks, then the time, allocations, status reports, or financial records needed for the user's question. Report the scope and source records, distinguish observed facts from inferred risks, and avoid treating missing or inaccessible values as zero.\n\n## Requested changes\n\nRead the target's current state and validate required fields before updating it. Carry out only the user's requested changes. Follow tool-specific confirmation requirements and report verified results, including per-item failures in bulk operations. Do not blindly retry a mutation after an uncertain response; check whether it succeeded first.\n\nFor timesheet approvals or rejections, retrieve submissions first and verify pending status and the intended submitters and projects. Do not attempt self-approval. Include a rejection reason when provided or required. Confirm cancellation with the user before calling a cancellation tool, as required by the Kantata tools. A cancelled submission returns entries to unsubmitted state and requires a new submission to resubmit. Creating a timesheet submission is scoped to one project; inspect the tool schema and eligible entries first.\n\n## Connection\n\nUse the Kantata App connection created by the submission portal for https://app.mavenlink.com/mcp. Use the host's App connection flow when sign-in is needed. Never request credentials in chat, embed tokens in files, or treat existing tools from another Kantata connection as proof that this plugin's connection is authenticated. If a connection or permission blocks a task, describe the missing step precisely and preserve any useful completed analysis.\n\n\n"
}SHA-256 of public snapshot: 394a606f67fafb6b3729b3c1132dc0cc45f62fd6d01e3d2070ff427a31e74b84