Agent skill · software engineering · jeremylongshore
mindtickle-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".
Why this skill is useful
Adds a complete multi-tenant integration architecture with executable service layer code and specific configurations for MindTickle that aren't in public documentation.
What it needs
Requires node, postgresql, rabbitmq, redis 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
Tenant-Scoped Mindtickle Integration Architecture Overview Produce a decision-ready architecture that identifies every trust boundary, system of record, contract, data flow, failure mode, and operational owner. Prerequisites A business workflow, tenant and environment inventory, package entitlement, and data classification Current identity, connector, and tenant API artifacts with owners and provenance Customer security, retention, residency, reliability, and support requirements Tool Discipline Use Read, Glob, and Grep to inspect repository topology and existing decisions, WebFetch for current official contracts, and Write or Edit for diagrams, decisions, threat models, and redacted evidence. Current Contract Mindtickle supports tenant-specific access, roles, managed integrations, REST-based API families, SCIM, SAML, OpenID, and package-dependent product modules. The architecture must not assume every tenant has every module or that managed connectors and custom APIs share one authorization model. Authentication Model interactive SSO, lifecycle provisioning, managed connectors, and API principals separately. Bind every principal, secret, queue, store, cache, and log to a tenant and environment with least privilege and revocation ownership. Instructions 1. Define scope, outcomes, non-goals, actors, systems of record, tenants, environments, and data classes. 2. Draw trust boundaries and directional flows for identity, content, users, reporting, events, administration, support, and deletion. 3. Attach an authoritative contract, owner, authentication class, and permitted operations to every external edge. 4. Choose managed integration, file exchange, tenant API, or human workflow per use case based on supportability and risk. 5. Define tenant isolation, schema validation, idempotency, reconciliation, backpressure, retention, encryption, and audit evidence. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-reference-architecture--cb2398