mindtickle-security-basics
Security Basics for MindTickle. Trigger: "mindtickle security basics".
Best use case
mindtickle-security-basics is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Security Basics for MindTickle. Trigger: "mindtickle security basics".
Teams using mindtickle-security-basics 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-security-basics/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mindtickle-security-basics Compares
| Feature / Agent | mindtickle-security-basics | 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?
Security Basics for MindTickle. Trigger: "mindtickle security basics".
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
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 Security Basics
## Overview
MindTickle integrations process employee PII through SCIM provisioning (names, emails, job titles, manager chains) and HR-sensitive data like course completion scores, certification status, and coaching assessments. The API uses bearer token authentication combined with a `Company-Id` header for multi-tenant isolation — omitting or spoofing this header can leak data across tenants. Webhook payloads carrying training completion events must be HMAC-verified to prevent injection of fraudulent compliance records.
## Prerequisites
- Secrets manager (AWS SSM, GCP Secret Manager, or Vault) for API tokens
- HTTPS enforced on all SCIM and webhook endpoints
- `Company-Id` validated against an allowlist of known tenant identifiers
- `.env` files in `.gitignore` — never committed to version control
- Data retention policy for employee training records (GDPR/SOC2)
## API Key Management
```typescript
// MindTickle requires both bearer token and company ID for multi-tenant isolation
const MT_API_TOKEN = process.env.MINDTICKLE_API_KEY;
const MT_COMPANY_ID = process.env.MINDTICKLE_COMPANY_ID;
function validateMindTickleConfig(): void {
if (!MT_API_TOKEN) throw new Error('Missing MINDTICKLE_API_KEY');
if (!MT_COMPANY_ID) throw new Error('Missing MINDTICKLE_COMPANY_ID');
}
function mindtickleHeaders(): Record<string, string> {
return {
Authorization: `Bearer ${MT_API_TOKEN}`,
'Company-Id': MT_COMPANY_ID!,
'Content-Type': 'application/json',
};
}
// Call validateMindTickleConfig() at startup — both values are required for every request
```
## Webhook Signature Verification
```typescript
import crypto from 'node:crypto';
const MT_WEBHOOK_SECRET = process.env.MINDTICKLE_WEBHOOK_SECRET!;
function verifyMindTickleWebhook(payload: string, signature: string, timestamp: string): boolean {
// Reject stale webhooks (>5 min) to prevent replay attacks
const age = Date.now() - parseInt(timestamp, 10) * 1000;
if (age > 300_000) return false;
const signedPayload = `${timestamp}.${payload}`;
const expected = crypto
.createHmac('sha256', MT_WEBHOOK_SECRET)
.update(signedPayload, 'utf8')
.digest('hex');
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}
app.post('/webhooks/mindtickle', (req, res) => {
const sig = req.headers['x-mindtickle-signature'] as string;
const ts = req.headers['x-mindtickle-timestamp'] as string;
if (!sig || !ts || !verifyMindTickleWebhook(JSON.stringify(req.body), sig, ts)) {
return res.status(401).json({ error: 'Invalid signature or stale timestamp' });
}
// Process verified training completion event
});
```
## Input Validation
```typescript
// Validate SCIM user payloads — employee PII requires strict schema enforcement
interface ScimUser {
userName: string;
name: { givenName: string; familyName: string };
emails: { value: string; primary: boolean }[];
}
function validateScimUser(user: unknown): user is ScimUser {
const u = user as Record<string, unknown>;
if (typeof u.userName !== 'string' || u.userName.length > 254) return false;
const emails = u.emails as { value: string }[] | undefined;
if (!emails?.every(e => /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(e.value))) return false;
return true;
}
```
## Data Protection
```typescript
function redactEmployeeData(record: Record<string, unknown>): Record<string, unknown> {
const piiFields = ['email', 'userName', 'phone', 'manager_email', 'employee_id'];
const hrFields = ['score', 'certification_status', 'coaching_notes'];
const redacted = { ...record };
for (const field of [...piiFields, ...hrFields]) {
if (redacted[field]) redacted[field] = '[REDACTED]';
}
return redacted;
}
// Redact before logging — course scores and coaching data are HR-confidential
```
## Access Control
```typescript
// Enforce tenant isolation — Company-Id must match the authenticated context
const ALLOWED_COMPANY_IDS = new Set(process.env.MT_ALLOWED_COMPANIES?.split(',') ?? []);
function assertTenantAccess(companyId: string): void {
if (!ALLOWED_COMPANY_IDS.has(companyId)) {
throw new Error(`Unauthorized tenant: ${companyId}`);
}
}
function assertScimWriteAccess(operation: string, hasScimScope: boolean): void {
const writeOps = ['createUser', 'updateUser', 'deactivateUser'];
if (writeOps.includes(operation) && !hasScimScope) {
throw new Error(`SCIM write operation "${operation}" requires scim:write scope`);
}
}
```
## Security Checklist
- [ ] Bearer token and Company-Id stored in secrets manager
- [ ] Company-Id validated against tenant allowlist on every request
- [ ] Webhook HMAC-SHA256 verified with timestamp replay protection
- [ ] SCIM payloads validated against strict schema before processing
- [ ] Employee PII (email, name, phone) redacted in all logs
- [ ] Course scores and coaching data classified as HR-confidential
- [ ] SCIM write operations gated behind explicit scope checks
- [ ] Data retention policy enforced for training completion records
- [ ] Token rotation scheduled quarterly with zero-downtime swap
## Error Handling
| Vulnerability | Risk | Mitigation |
|---|---|---|
| Missing Company-Id header | Cross-tenant data leakage | Reject requests without validated Company-Id |
| Unverified webhooks | Fraudulent training completion records | HMAC-SHA256 + timestamp validation on every webhook |
| SCIM PII in logs | Employee data breach (GDPR/SOC2) | Redact all PII fields before logging |
| Stale webhook replay | Duplicate or backdated compliance events | Reject webhooks older than 5 minutes |
| Over-permissioned SCIM token | Unauthorized user provisioning | Enforce scim:write scope check for mutations |
## Resources
- [MindTickle Developer Platform](https://www.mindtickle.com/platform/integrations/)
- [OWASP API Security Top 10](https://owasp.org/www-project-api-security/)
## Next Steps
See `mindtickle-prod-checklist`.Related Skills
performing-security-testing
Test automate security vulnerability testing covering OWASP Top 10, SQL injection, XSS, CSRF, and authentication issues. Use when performing security assessments, penetration tests, or vulnerability scans. Trigger with phrases like "scan for vulnerabilities", "test security", or "run penetration test".
checking-session-security
Analyze session management implementations to identify security vulnerabilities in web applications. Use when you need to audit session handling, check for session fixation risks, review session timeout configurations, or validate session ID generation security. Trigger with phrases like "check session security", "audit session management", "review session handling", or "session fixation vulnerability".
finding-security-misconfigurations
Configure identify security misconfigurations in infrastructure-as-code, application settings, and system configurations. Use when you need to audit Terraform/CloudFormation templates, check application config files, validate system security settings, or ensure compliance with security best practices. Trigger with phrases like "find security misconfigurations", "audit infrastructure security", "check config security", or "scan for misconfigured settings".
responding-to-security-incidents
Analyze and guide security incident response, investigation, and remediation processes. Use when you need to handle security breaches, classify incidents, develop response playbooks, gather forensic evidence, or coordinate remediation efforts. Trigger with phrases like "security incident response", "ransomware attack response", "data breach investigation", "incident playbook", or "security forensics".
analyzing-security-headers
Analyze HTTP security headers of web domains to identify vulnerabilities and misconfigurations. Use when you need to audit website security headers, assess header compliance, or get security recommendations for web applications. Trigger with phrases like "analyze security headers", "check HTTP headers", "audit website security headers", or "evaluate CSP and HSTS configuration".
generating-security-audit-reports
Generate comprehensive security audit reports for applications and systems. Use when you need to assess security posture, identify vulnerabilities, evaluate compliance status, or create formal security documentation. Trigger with phrases like "create security audit report", "generate security assessment", "audit security posture", or "PCI-DSS compliance report".
workhuman-security-basics
Workhuman security basics for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman security basics".
wispr-security-basics
Wispr Flow security basics for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr security basics".
windsurf-security-basics
Apply Windsurf security best practices for workspace isolation, data privacy, and secret protection. Use when securing sensitive code from AI indexing, configuring telemetry, or auditing Windsurf security posture. Trigger with phrases like "windsurf security", "windsurf secrets", "windsurf privacy", "windsurf data protection", "codeiumignore".
webflow-security-basics
Apply Webflow API security best practices — token management, scope least privilege, OAuth 2.0 secret rotation, webhook signature verification, and audit logging. Use when securing API tokens, implementing least privilege access, or auditing Webflow security configuration. Trigger with phrases like "webflow security", "webflow secrets", "secure webflow", "webflow API key security", "webflow token rotation".
vercel-security-basics
Apply Vercel security best practices for secrets, headers, and access control. Use when securing API keys, configuring security headers, or auditing Vercel security configuration. Trigger with phrases like "vercel security", "vercel secrets", "secure vercel", "vercel headers", "vercel CSP".
veeva-security-basics
Veeva Vault security basics for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva security basics".