Agent skill · data analytics · jeremylongshore
mindtickle-common-errors
Triage Mindtickle access, provisioning, content, assignment, reporting, and managed-integration failures using evidence and ownership boundaries. Use when an incident or rollout fails. Trigger with "triage Mindtickle failure".
Why this skill is useful
Provides specific troubleshooting steps and error handling patterns for MindTickle API integration that the AI wouldn't reliably generate on its own.
What it needs
Requires mindtickle account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Evidence-First Mindtickle Failure Triage Overview Classify a failure by boundary, protect learner data, and produce the smallest reversible diagnosis before changing tenant state. Prerequisites An incident owner, affected tenant, time window, population, and business impact The last known-good state and recent changes across identity, content, data, and integrations Approved access to redacted application and tenant evidence Tool Discipline Use Read, Glob, and Grep to inspect local logs and configuration, WebFetch for current official and authorized tenant guidance, and Write or Edit for a sanitized timeline and support packet. Current Contract Failures can cross customer identity providers, user sync, tenant roles, subscribed modules, managed connectors, customer adapters, and Mindtickle service boundaries. HTTP status alone does not prove root cause, and public material does not define universal error payloads. Authentication Use the least-privilege diagnostic principal. Redact tokens, cookies, personal data, assessment results, content URLs, and confidential tenant artifacts before sharing evidence. Instructions 1. Freeze the symptom, first occurrence, blast radius, expected behavior, request or job identifiers, and recent changes. 2. Determine whether the failure is interactive access, provisioning, entitlement, content, assignment, reporting, connector, adapter, or platform availability. 3. Compare one failing case with one known-good case while changing only one variable at a time. 4. Validate tenant, principal, role, environment, contract digest, input identity, timestamps, and source-system state. 5. Check official service and support information, then distinguish customer-controlled remediation from vendor escalation. 6. Propose the smallest reversible repair with preview, approver, rollback, and post-change verification. 7. Reconcile the full affected set after repair; do not close on one successful sample. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-common-errors--924f5c