Agent skill · software engineering · jeremylongshore
mindtickle-hello-world
Discover a Mindtickle tenant''s licensed capabilities and produce a safe first integration proof without assuming public API details. Use when starting a Mindtickle exercise or tenant handoff. Trigger with "start with Mindtickle".
Why this skill is useful
Adds executable scripts for creating training modules, assigning them to sales reps, and tracking completion using the MindTickle API that aren't in public docs.
What it needs
Requires npm 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
Mindtickle Capability Discovery and First Proof Overview Turn a business outcome into an entitlement-aware, read-only proof that establishes the real tenant contract before implementation begins. Prerequisites A named tenant site owner and one measurable business outcome The purchased package or order summary and an approved non-production audience Access to current tenant documentation without copying confidential content into the repository Tool Discipline Use Read, Glob, and Grep for existing assumptions and fixtures, WebFetch for current official sources, and Write or Edit for a redacted capability matrix and proof plan. Current Contract Package contents differ. Public descriptions identify learning modules, assessments, certifications, coaching, Readiness Index, Asset Hub, Digital Sales Rooms, analytics, and Call AI in different combinations. Availability in one tenant is evidence, not a universal product contract. Authentication Use the onboarding decision from mindtickle-install-auth. Discovery must use a named least-privilege principal; never use shared administrator credentials or scrape authenticated UI pages as an API substitute. Instructions 1. Define the outcome, audience, data sensitivity, success metric, and maximum proof scope. 2. Compare the purchased package, visible tenant modules, managed integration catalogue, and tenant API documentation. 3. Mark each needed capability confirmed, absent, restricted, or vendor clarification required. 4. Choose the smallest reversible proof: a local fixture exercise, a tenant read, or a site-owner-led UI walkthrough. 5. Define acceptance before execution, including expected fields, freshness, authorization, and zero unintended mutations. 6. Obtain approval for any tenant access, then run the proof once and capture redacted evidence. 7. Convert confirmed observations into a contract fixture; label every tenant-specific inference and expiry date. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-hello-world