Agent skill · software engineering · jeremylongshore
mindtickle-sdk-patterns
Build a typed, tenant-scoped Mindtickle adapter from customer-authorized API artifacts without assuming a public SDK. Use when implementing Content, User, or Reporting API access. Trigger with "design a Mindtickle adapter".
Why this skill is useful
Provides a structured SDK client for MindTickle's API with executable code for authentication, error handling, and query building.
What it needs
Requires axios, node 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
Contract-First Mindtickle Adapter Patterns Overview Turn an authorized tenant API contract into a narrow adapter with explicit operations, validation, retries, tenancy, and evidence—without fabricating an SDK or route. Prerequisites A versioned tenant API artifact with provenance, permitted operations, and data classification Confirmed authentication, environment, capacity, support, and change-notification contracts Test fixtures that contain no production secrets or learner PII Tool Discipline Use Read, Glob, and Grep to inspect contract artifacts and code, WebFetch only for authorized current documentation, and Write or Edit for adapter code, fixtures, and redacted receipts. Current Contract Public Mindtickle material confirms REST-based Content, User, and Reporting APIs but does not define a universal public SDK, base URL, route set, or credential header. Treat the tenant artifact as the executable authority and record its digest and expiry. Authentication Inject credentials through the approved runtime secret provider. Bind configuration to one tenant and environment, redact request logs, and reject startup when tenant, host, or credential provenance is ambiguous. Instructions 1. Inventory only documented operations needed for the business workflow and classify each read, write, idempotency, and privacy property. 2. Freeze the source artifact digest, tenant, environment, auth scheme, schemas, pagination, errors, and capacity signals. 3. Generate or handwrite internal transport types behind a product-specific interface; never leak vendor payloads into domain logic. 4. Validate requests and responses at the boundary and reject undocumented fields or status assumptions. 5. Implement bounded retries only for documented transient conditions, with idempotency or reconciliation for writes. 6. Add fixtures for success, authorization failure, validation failure, pagination, throttling signals, timeout ambiguity, and schema drift. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-sdk-patterns