Agent skill · software engineering · jeremylongshore
mindtickle-debug-bundle
Assemble a privacy-safe Mindtickle support evidence bundle with configuration fingerprints, timelines, representative failures, and ownership context. Use when preparing a vendor escalation. Trigger with "build Mindtickle debug bundle".
Why this skill is useful
Adds an executable script that automates the collection of diagnostic data from the MindTickle API, which is not commonly available in public documentation.
What it needs
Requires curl, jq, tar installed locally. 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
Privacy-Safe Mindtickle Support Bundle Overview Create a deterministic evidence manifest that helps customer and Mindtickle support diagnose a problem without exporting secrets or unnecessary learner data. Prerequisites A tracked incident, disclosure audience, retention deadline, and support severity An approved redaction policy and secure transfer destination Read-only access to relevant customer-side configuration, logs, and receipts Tool Discipline Use Read, Glob, and Grep to locate evidence, WebFetch to confirm current support requirements, and Write or Edit only inside the approved bundle path and manifest. Current Contract Mindtickle Support may request business context, logs, files, and appropriate remote access. Official support guidance defines severity and response paths; the customer remains responsible for minimizing and sanitizing what is disclosed. Authentication Do not collect passwords, tokens, cookies, authorization headers, private keys, raw identity-provider assertions, or unrestricted tenant exports. Replace user identifiers with stable incident-local aliases where individual evidence is necessary. Instructions 1. Define the incident window, symptom, affected workflow, audience, severity, and questions the bundle must answer. 2. Create an evidence allowlist and explicit denylist before reading files. 3. Collect configuration names and digests, adapter version, contract digest, deployment receipt, timestamps, safe request IDs, and representative sanitized errors. 4. Add expected-versus-actual behavior, one known-good comparison, reproduction limits, recent changes, and attempted mitigations. 5. Scan every artifact for secrets, cookies, personal data, assessment data, content URLs, and internal infrastructure details. 6. Produce a manifest with artifact digests, provenance, redactions, collector, collection time, and expiry. 7. Obtain disclosure approval, transfer through the contracted secure channel, and record the support receipt. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-debug-bundle