mindtickle-ci-integration
Ci Integration for MindTickle. Trigger: "mindtickle ci integration".
Best use case
mindtickle-ci-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Ci Integration for MindTickle. Trigger: "mindtickle ci integration".
Teams using mindtickle-ci-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/mindtickle-ci-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mindtickle-ci-integration Compares
| Feature / Agent | mindtickle-ci-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Ci Integration for MindTickle. Trigger: "mindtickle ci integration".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# MindTickle CI Integration
## Overview
Configure CI pipelines that validate MindTickle sales enablement API integrations using a two-tier testing strategy. Unit tests mock the MindTickle REST client to verify course enrollment, quiz scoring, and user progress logic without consuming API calls. Integration tests run on main-branch merges with a real Bearer token and company ID to confirm course listing, user search, and completion tracking against the live MindTickle API. The dual-header auth pattern (API key plus company ID) requires special CI secret management to avoid silent authentication failures.
## GitHub Actions Workflow
```yaml
# .github/workflows/mindtickle-tests.yml
name: MindTickle API Tests
on: [push, pull_request]
jobs:
unit-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm run lint && npm run typecheck
- run: npm test -- --testPathPattern=unit # No API key or company ID needed
integration-tests:
runs-on: ubuntu-latest
if: github.ref == 'refs/heads/main'
needs: unit-tests
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm test -- --testPathPattern=integration
env:
MINDTICKLE_API_KEY: ${{ secrets.MINDTICKLE_API_KEY }}
MINDTICKLE_COMPANY_ID: ${{ secrets.MINDTICKLE_COMPANY_ID }}
```
## Mock-Based Unit Tests
```typescript
// tests/unit/course-service.test.ts
import { describe, it, expect, vi } from 'vitest';
import { enrollUser } from '../../src/services/course-service';
import * as mtClient from '../../src/lib/mindtickle-client';
vi.mock('../../src/lib/mindtickle-client');
describe('CourseService', () => {
it('enrolls a user in a training course', async () => {
vi.mocked(mtClient.post).mockResolvedValue({
enrollment_id: 'enr-3390',
user_id: 'usr-512',
course_id: 'crs-77',
status: 'enrolled',
enrolled_at: '2026-04-01T10:00:00Z',
});
const result = await enrollUser('usr-512', 'crs-77');
expect(result.status).toBe('enrolled');
expect(mtClient.post).toHaveBeenCalledWith('/courses/crs-77/enrollments', {
user_id: 'usr-512',
});
});
});
```
## Integration Tests
```typescript
// tests/integration/user-progress.test.ts
import { describe, it, expect } from 'vitest';
import { MindTickleClient } from '../../src/lib/mindtickle-client';
const canRun = process.env.MINDTICKLE_API_KEY && process.env.MINDTICKLE_COMPANY_ID;
describe.skipIf(!canRun)('MindTickle User Progress (live API)', () => {
const client = new MindTickleClient({
apiKey: process.env.MINDTICKLE_API_KEY!,
companyId: process.env.MINDTICKLE_COMPANY_ID!,
});
it('retrieves course completion stats for a user', async () => {
const users = await client.get('/users', { limit: 1 });
expect(users.length).toBeGreaterThan(0);
const progress = await client.get(`/users/${users[0].id}/progress`);
expect(progress).toHaveProperty('courses_completed');
expect(typeof progress.courses_completed).toBe('number');
});
});
```
## CI Cost Management
```typescript
// tests/helpers/api-budget.ts
let callCount = 0;
const MAX_CALLS_PER_RUN = 30; // MindTickle API has per-company rate limits
export function trackApiCall(): void {
callCount++;
if (callCount > MAX_CALLS_PER_RUN) {
throw new Error(
`CI API budget exceeded: ${callCount}/${MAX_CALLS_PER_RUN} calls. ` +
'MindTickle enforces per-company rate limits — reduce test scope or paginate less.'
);
}
}
export function getCallCount(): number { return callCount; }
```
## Error Handling
| CI Issue | Cause | Fix |
|----------|-------|-----|
| 401 Unauthorized | Missing or invalid Bearer token | Regenerate `MINDTICKLE_API_KEY` in MindTickle admin and update GitHub Secrets |
| 403 Forbidden | Company ID mismatch or insufficient permissions | Verify `MINDTICKLE_COMPANY_ID` matches the API key's org; check API scope |
| Empty user list | Company has no users in sandbox instance | Provision test users via `POST /users` in a `beforeAll` setup hook |
| Quiz scores return null | Course has no quizzes configured | Use a known test course ID with at least one quiz module |
| Integration tests silently pass | Both env vars undefined so `skipIf` triggers | Add a CI step that asserts secrets are set: `test -n "$MINDTICKLE_API_KEY"` |
## Resources
- [MindTickle Platform Integrations](https://www.mindtickle.com/platform/integrations/)
- [GitHub Actions Encrypted Secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets)
## Next Steps
See `mindtickle-deploy-integration`.Related Skills
running-integration-tests
Execute integration tests validating component interactions and system integration. Use when performing specialized testing. Trigger with phrases like "run integration tests", "test integration", or "validate component interactions".
workhuman-deploy-integration
Workhuman deploy integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman deploy integration".
workhuman-ci-integration
Workhuman ci integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman ci integration".
wispr-deploy-integration
Wispr Flow deploy integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr deploy integration".
wispr-ci-integration
Wispr Flow ci integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr ci integration".
windsurf-ci-integration
Integrate Windsurf Cascade workflows into CI/CD pipelines and team automation. Use when automating Cascade tasks in GitHub Actions, enforcing AI code quality gates, or setting up Windsurf config validation in CI. Trigger with phrases like "windsurf CI", "windsurf GitHub Actions", "windsurf automation", "cascade CI", "windsurf pipeline".
webflow-deploy-integration
Deploy Webflow-powered applications to Vercel, Fly.io, and Google Cloud Run with proper secrets management and Webflow-specific health checks. Trigger with phrases like "deploy webflow", "webflow Vercel", "webflow production deploy", "webflow Cloud Run", "webflow Fly.io".
webflow-ci-integration
Configure Webflow CI/CD with GitHub Actions — automated CMS validation, integration tests with test tokens, and publish-on-merge workflows. Use when setting up automated testing or CI pipelines for Webflow integrations. Trigger with phrases like "webflow CI", "webflow GitHub Actions", "webflow automated tests", "CI webflow", "webflow pipeline".
vercel-deploy-integration
Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies. Use when deploying to production, configuring deployment regions, or setting up blue-green deployment patterns on Vercel. Trigger with phrases like "deploy vercel", "vercel production deploy", "vercel promote", "vercel rollback", "vercel regions".
veeva-deploy-integration
Veeva Vault deploy integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva deploy integration".
veeva-ci-integration
Veeva Vault ci integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva ci integration".
vastai-deploy-integration
Deploy ML training jobs and inference services on Vast.ai GPU cloud. Use when deploying GPU workloads, configuring Docker images, or setting up automated deployment scripts. Trigger with phrases like "deploy vastai", "vastai deployment", "vastai docker", "vastai production deploy".