Agent skill · software engineering · jeremylongshore
mindtickle-ci-integration
Create a fail-closed CI lane for a Mindtickle adapter using contract fixtures, secret scanning, and an explicitly gated tenant smoke test. Use when hardening integration delivery. Trigger with "test Mindtickle in CI".
Why this skill is useful
Adds a GitHub Actions workflow for testing MindTickle API integrations, including unit and integration tests with specific configurations.
What it needs
Requires 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
Fail-Closed Mindtickle Integration CI Overview Gate adapter changes on contract integrity and sanitized behavior while keeping external tenant access isolated, read-only, and manually authorized. Prerequisites Deterministic local tests and sanitized fixtures from mindtickle-local-dev-loop Protected branches, pinned CI permissions, a secret scanner, and artifact retention policy A separately owned non-production tenant principal if a live smoke lane is justified Tool Discipline Use Read, Glob, and Grep to inspect workflows and dependency locks, WebFetch for current CI and tenant contracts, and Write or Edit for workflow files, tests, and redacted evidence. Current Contract The always-on lane must not depend on a live Mindtickle tenant. A live lane is optional and must use the customer's documented read-only operation, protected environment approval, bounded execution, and redacted logs. Authentication Grant workflow tokens minimal repository permissions. Store any tenant credential in the CI secret provider, restrict it to the protected environment, prevent fork access, and never expose it to pull-request code. Instructions 1. Inventory CI triggers, permissions, third-party actions, caches, artifacts, and secret exposure paths. 2. Build an always-on lane for metadata validation, secret scanning, static checks, unit tests, contract fixtures, and generated-content drift. 3. Pin actions and dependencies according to repository policy and reject unreviewed network downloads. 4. Assert fixture sanitization, contract digest, tenant isolation, retry bounds, mutation denial, and stable output. 5. If justified, add a separate manual or protected-main smoke lane using one documented read-only operation and a strict timeout. 6. Ensure fork pull requests never receive tenant secrets and smoke logs record only status and safe identifiers. 7. Test success, missing secret, revoked access, contract mismatch, timeout, and artifact-redaction paths. 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-ci-integration