Agent skill · software engineering · jeremylongshore
mindtickle-install-auth
Select and document the correct Mindtickle access path for a tenant, including browser SSO, user provisioning, managed connectors, or customer-issued API credentials. Use when onboarding or repairing an integration. Trigger with "configure Mindtickle access".
Why this skill is useful
Adds specific commands and configuration steps for integrating with the MindTickle API that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python 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 Tenant Access and Integration Onboarding Overview Choose the supported access model, establish ownership, and verify the smallest safe capability without inventing a universal endpoint or credential format. Prerequisites The customer's tenant URL, subscription package, site owner, and integration purpose An identity, security, and data owner for the affected users and records Customer-authorized tenant documentation or a Mindtickle Technical Solutions contact Tool Discipline Use Read, Glob, and Grep to inspect local configuration, WebFetch to re-check official public and tenant-authorized contracts, and Write or Edit only for secretless configuration and redacted evidence. Current Contract Mindtickle documents tenant-specific web URLs, role-based administration, managed integrations, REST-based Content/User/Reporting APIs, and standards including SCIM, SAML, and OpenID. Exact API hosts, routes, schemas, credentials, and entitlements are tenant-controlled and must be obtained from authorized documentation. Authentication Separate interactive SSO, automated provisioning, managed connector authorization, and API credentials. Do not treat an SSO session as API authorization, guess headers, reuse administrator cookies, or place secrets in files, logs, prompts, or receipts. Instructions 1. Record the tenant, package, data classes, systems of record, intended reads and writes, and accountable owners. 2. Classify the path as browser SSO, SCIM/user sync, a catalogued managed integration, or a customer-issued API contract. 3. Re-fetch the applicable public product description and the customer's current tenant documentation. 4. Build an access matrix covering principal, roles, scopes, environments, expiration, rotation, revocation, and break-glass ownership. 5. Inspect the repository for guessed hosts, hard-coded secrets, browser-session reuse, and mixed tenant configuration. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-install-auth