Agent skill · software engineering · jeremylongshore
mindtickle-deploy-integration
Deploy a tenant-scoped Mindtickle adapter through a canary, reconciliation, and rollback workflow. Use when promoting an approved integration build. Trigger with "deploy Mindtickle integration".
Why this skill is useful
Adds a complete Docker deployment script for a MindTickle integration service, including health checks and rolling updates, which the AI cannot generate on its own.
What it needs
Requires docker, node 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
Controlled Mindtickle Adapter Deployment Overview Promote a verified adapter without assuming a deployment platform, then prove tenant binding, safe behavior, and rollback from production evidence. Prerequisites An immutable build, passing CI receipt, contract digest, and dependency inventory Environment owners, secret references, tenant mapping, observability, and on-call coverage A canary workload, success thresholds, abort criteria, and tested rollback Tool Discipline Use Read, Glob, and Grep to inspect manifests and receipts, WebFetch for current authorized contracts, and Write or Edit for deployment configuration, runbooks, and redacted evidence. Current Contract Deployment architecture is customer-controlled. The adapter must use the exact tenant API or managed-connector contract already approved; health checks must prove local readiness separately from optional external dependency readiness. Authentication Resolve secrets at runtime from the approved provider, bind them to one environment and tenant, deny shell or log exposure, and verify rotation and revocation ownership before rollout. Instructions 1. Freeze build identity, contract digest, configuration digest, tenant map, dependencies, and data-flow classification. 2. Validate least-privilege runtime identity, egress allowlist, encryption, secret references, resource limits, and log redaction. 3. Separate liveness, local readiness, and external dependency signals so a vendor outage does not cause uncontrolled restart storms. 4. Present the deployment diff, canary population, expected operations, alert thresholds, approvers, and rollback command. 5. After approval, deploy the canary and observe latency, errors, throttling, backlog, duplicate prevention, and reconciliation. 6. Expand only when the evidence window passes; stop automatically on an abort threshold. 7. Reconcile expected versus actual tenant state and retain deployment and rollback receipts without sensitive payloads. 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-deploy-integration