Agent skill · software engineering · jeremylongshore
mindtickle-local-dev-loop
Build a fast, secret-free local development loop for a Mindtickle adapter using frozen tenant-contract fixtures. Use when developing without live learner data. Trigger with "set up Mindtickle local development".
Why this skill is useful
Adds a complete local development environment with executable scripts for mocking MindTickle API responses and testing workflows.
What it needs
Requires npm 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
Mindtickle Contract-Fixture Development Loop Overview Make adapter development deterministic by separating domain behavior from the tenant transport and exercising only sanitized, versioned fixtures locally. Prerequisites An authorized tenant contract digest and sanitized success and failure examples A product-specific adapter boundary from mindtickle-sdk-patterns A secret scanner and repository policy for generated or confidential artifacts Tool Discipline Use Read, Glob, and Grep to inspect code and fixtures, WebFetch only to refresh approved contract sources, and Write or Edit for local adapters, fixtures, tests, and documentation. Current Contract Public Mindtickle pages establish API families but not a public emulator or universal SDK. Local mode must therefore emulate the frozen customer contract, identify synthetic values clearly, and fail closed when an unrecorded operation appears. Authentication Local mode accepts no real credential. Represent auth outcomes with synthetic fixtures and reserve any tenant smoke test for a separately approved integration lane. Instructions 1. Record the contract digest, fixture provenance, sanitization method, and supported operation list. 2. Route domain code through the adapter interface; reject direct network calls outside the transport module. 3. Add deterministic fixtures for success, empty results, pagination, validation, authorization, throttling signal, timeout ambiguity, and schema drift. 4. Validate fixtures against internal schemas and scan them for secrets and identifying data. 5. Provide a fake clock, stable identifiers, bounded randomness, and deterministic retry scheduling. 6. Run focused tests after every change and compare normalized outputs rather than vendor-specific ordering unless documented. 7. Fail the local server when code requests an unknown route, tenant, or fixture instead of silently returning a generic response. 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-local-dev-loop