Skip to content
Skills Library
Security · Review & audit

mindtickle-security-basics

/mindtickle-security-basics

Threat-model and harden a Mindtickle tenant and its identity, connector, API, content, and reporting integrations. Use when conducting security review or control remediation. Trigger with "secure Mindtickle integration".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Threat-model and harden a Mindtickle tenant and its identity, connector, API, content, and reporting integrations. Use when conducting security review or control remediation. Trigger with "secure Mindtickle integration".

Triggers from the description

secure Mindtickle integration

Arguments

/mindtickle-security-basics [scope] [evidence-period]
Original author description

Threat-model and harden a Mindtickle tenant and its identity, connector, API, content, and reporting integrations. Use when conducting security review or control remediation. Trigger with "secure Mindtickle integration".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Example
Original SKILL.md headings · 67 lines, 447 words
SKILL.md preview
---
name: mindtickle-security-basics
description: 'Threat-model and harden a Mindtickle tenant and its identity, connector, API, content, and reporting integrations. Use when conducting security review or control remediation. Trigger with "secure Mindtickle integration".'
argument-hint: "[scope] [evidence-period]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags: [saas, mindtickle, security, privacy, threat-modeling]
model: inherit
effort: high
compatibility: Designed for Claude Code; tenant, identity, data, credential, and security-control changes require their respective owners
---
# Mindtickle Security and Privacy Control Review

## Overview

Translate shared responsibility into testable controls for identities, tenant boundaries, employee data, content, integrations, evidence, and incident response.

## Prerequisites

- A scoped architecture, data inventory, identity model, contract registry, and accountable owners
- Current customer policy, threat model, retention schedule, and incident process
- Authorized access to Mindtickle trust artifacts and tenant-specific security documentation

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect configuration and evidence, `WebFetch` for current official security material, and `Write` or `Edit` for the threat model, control matrix, and sanitized findings.

## Current Contract

Mindtickle describes role-based access, customer responsibility for SSO, roles, provisioning, and data lifecycle, plus independent compliance and security assessments. Certifications inform assurance but do not replace customer control validation.

## Authentication

Separate users, administrators, provisioning identities, managed connectors, API principals, and support access. Require least privilege, phishing-resistant identity controls where available, rotation, revocation, access review, and no shared credentials.

## Instructions

1. Inventory tenants, environments, principals, roles, integrations, data classes, content audiences, exports, caches, logs, and support paths.
2. Map threats across account takeover, overprivilege, tenant misrouting, lifecycle drift, data leakage, malicious content, replay, schema injection, and compromised dependencies.
3. Verify SSO enforcement, identity-provider MFA, provisioning ownership, disabled-user handling, administrator separation, and periodic access review.
4. Test tenant binding, input and output validation, secret handling, egress restrictions, encryption, logging redaction, and evidence integrity.
5. Review data minimization, retention, deletion, exports, residency commitments, learner transparency, and restricted assessment or coaching data.
6. Validate connector and adapter scopes, contract provenance, dependency controls, incident contacts, support disclosure, and credential compromise response.
7. Rank findings by exploitable path and business impact; assign owner, remediation, verification, and due date.
8. Re-test changed controls and preserve redacted evidence rather than closing on configuration screenshots alone.

## Approval Boundaries

Do not weaken SSO, grant roles, rotate production credentials, access learner records, change retention, or conduct intrusive testing without explicit authorization.

## Output

Return the asset and data inventory, trust boundaries, threat model, control evidence, findings, owners, remediation dates, residual risks, and re-test results.

## Error Handling

| Condition | Response |
|---|---|
| A secret appears in evidence | Restrict access, remove it, rotate as required, and regenerate the artifact. |
| Tenant-specific assurance is unavailable | Record the gap and request it through the authorized trust or commercial channel. |
| A critical control fails | Stop affected integration activity and invoke the incident process. |

## Example

```text
scope=reporting-adapter; principals=3-owned; tenant-binding=pass; pii-logs=none; findings=1-high,2-medium; retest=scheduled
```

## Resources

- [Mindtickle Trust](https://www.mindtickle.com/trust/)
- [Mindtickle compliance](https://www.mindtickle.com/trust/compliance/)
- [Mindtickle Support Services](https://www.mindtickle.com/legal/support-services/)

## Next Steps

Track remediation to evidence-backed closure and schedule the next access and contract review.

Versions

The database has no other skills named mindtickle-security-basics.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version bead4eec70d0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100mindtickle-reference-architecture
    Design a secure, tenant-scoped architecture for Mindtickle identity, managed connectors, APIs, data processing, and operations. Use when designing or reviewing an integration. Trigger with "design Mindtickle architecture".
  • 100lucidchart-security-basics
    Threat-model and harden Lucid API, Standard Import, editor extension, and data connector integrations. Use when reviewing secrets, scopes, data flows, or release security. Trigger with "secure Lucid integration".
  • 100apollo-security-basics
    Apply Apollo.io API security best practices. Use when securing Apollo integrations, managing API keys, or implementing secure data handling. Trigger with phrases like "apollo security", "secure apollo api", "apollo api key security", "apollo data protection".
  • 100linear-security-basics
    Secure API key management and OAuth best practices for Linear. Use when setting up authentication securely, implementing OAuth flows, or hardening Linear integrations. Trigger with phrases like "linear security", "linear API key security", "linear OAuth", "secure linear…
  • 90secure
    Use to assess security and privacy risks, model threats, or implement authorized hardening. Use Audit for a general review and Operate for an active incident.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.