mindtickle-deploy-integration
Deploy Integration for MindTickle. Trigger: "mindtickle deploy integration".
What this skill does
# MindTickle Deploy Integration
## Overview
Deploy a containerized MindTickle integration service that manages sales readiness courses, tracks learner progress across quizzes and certifications, and synchronizes enablement data through the MindTickle API. This skill covers Docker multi-stage builds for the MindTickle SDK, API token configuration, health checks that verify course catalog access, and rolling deployments with zero disruption to active training sessions and learner progress tracking.
## Prerequisites
- Docker 24+ and Docker Compose v2 installed
- Valid `MINDTICKLE_API_KEY` from the MindTickle admin console (Settings > API)
- Node.js 20 LTS (build stage)
- Network access to `api.mindtickle.com` on port 443
- Target deployment host with at least 256MB available memory
## Docker Configuration
```dockerfile
FROM node:20-slim AS builder
WORKDIR /build
COPY package*.json tsconfig.json ./
RUN npm ci
COPY src/ ./src/
RUN npm run build
FROM node:20-slim
RUN groupadd -r mindtickle && useradd -r -g mindtickle -m appuser
WORKDIR /app
COPY --from=builder /build/dist ./dist/
COPY --from=builder /build/node_modules ./node_modules/
COPY package*.json ./
RUN npm prune --production
USER appuser
EXPOSE 3000
HEALTHCHECK --interval=30s --timeout=5s --retries=3 \
CMD curl -f http://localhost:3000/health || exit 1
CMD ["node", "dist/index.js"]
```
## Environment Variables
```bash
MINDTICKLE_API_KEY="mt_xxxxxxxxxxxxxxxx" # API key from admin console
MINDTICKLE_BASE_URL="https://api.mindtickle.com" # API base URL
MINDTICKLE_COMPANY_ID="" # Company identifier for multi-tenant access
MINDTICKLE_WEBHOOK_SECRET="" # HMAC secret for inbound webhook verification
LOG_LEVEL="info" # debug | info | warn | error
NODE_ENV="production"
PORT="3000"
```
## Health Check Endpoint
```typescript
import express from "express";
const app = express();
app.get("/health", async (_req, res) => {
try {
const response = await fetch(`${process.env.MINDTICKLE_BASE_URL}/v2/courses`, {
headers: {
Authorization: `Bearer ${process.env.MINDTICKLE_API_KEY}`,
"X-Company-Id": process.env.MINDTICKLE_COMPANY_ID ?? "",
},
});
if (!response.ok) throw new Error(`MindTickle API returned ${response.status}`);
const data = await response.json();
res.json({ status: "healthy", activeCourses: data.courses?.length ?? 0 });
} catch (err) {
res.status(503).json({ status: "unhealthy", error: (err as Error).message });
}
});
```
## Deployment Steps
### Step 1: Build Image
```bash
docker build -t mindtickle-integration:$(git rev-parse --short HEAD) .
```
### Step 2: Run Container
```bash
docker run -d --name mindtickle-svc \
--env-file .env.production \
-p 3000:3000 \
--restart unless-stopped \
mindtickle-integration:$(git rev-parse --short HEAD)
```
### Step 3: Verify Health
```bash
curl -s http://localhost:3000/health | jq .
# Expect: { "status": "healthy", "activeCourses": 24 }
```
### Step 4: Rolling Update
```bash
docker pull mindtickle-integration:latest
docker stop mindtickle-svc && docker rm mindtickle-svc
docker run -d --name mindtickle-svc --env-file .env.production -p 3000:3000 mindtickle-integration:latest
```
## Rollback Procedure
```text
# List recent images
docker images mindtickle-integration --format "{{.Tag}} {{.CreatedAt}}" | head -5
# Roll back to previous tag
docker stop mindtickle-svc && docker rm mindtickle-svc
docker run -d --name mindtickle-svc --env-file .env.production -p 3000:3000 mindtickle-integration:<previous-tag>
```
## Error Handling
| Issue | Cause | Fix |
|-------|-------|-----|
| 401 on course listing | Expired or revoked `MINDTICKLE_API_KEY` | Regenerate key in MindTickle admin console under Settings > API |
| 403 company access denied | Invalid `MINDTICKLE_COMPANY_ID` or key lacks tenant scope | Verify company ID and ensure API key has multi-tenant permissions |
| Learner sync timeouts | Large user base exceeding pagination limits | Implement cursor-based pagination with `page_size=100` and retry logic |
| Webhook HMAC mismatch | Incorrect `MINDTICKLE_WEBHOOK_SECRET` or payload tampering | Re-copy webhook secret from admin console; verify raw body is used for HMAC |
| Quiz progress 404 | Course or module was archived during sync | Add pre-check with `GET /v2/courses/{id}` to confirm course is active before progress writes |
## Resources
- [MindTickle Platform Integrations](https://www.mindtickle.com/platform/integrations/)
## Next Steps
See `mindtickle-webhooks-events`.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.