Maintainx Local Dev LoopSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Install
Commands as the repository documents them. They are shown, not run.
npm init -y
npm install axios dotenv
npm install -D typescript tsx vitest @types/node
npm init -y
npm install axios dotenv typescript ts-node @types/node
npm install -D jest @types/jest ts-jest nodemon
Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| cursor | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: maintainx-local-dev-loop description: 'Set up a local development loop for MaintainX integration development. Use when configuring dev environment, testing API calls locally, or setting up a sandbox workflow for MaintainX. Trigger with phrases like "maintainx dev setup", "maintainx local", "maintainx development environment", "maintainx testing setup". ' allowed-tools: Read, Write, Edit, Bash(npm:*), Bash(node:*), Bash(docker:*) version: 1.11.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - maintainx - api - testing - workflow compatibility: Designed for Claude Code --- # MaintainX Local Dev Loop ## Overview Set up an efficient local development workflow for building and testing MaintainX integrations with hot reload, mock servers, and automated testing. ## Prerequisites - Completed `maintainx-install-auth` setup - Node.js 18+ installed - `MAINTAINX_API_KEY` environment variable set ## Instructions ### Step 1: Initialize TypeScript Project ```bash mkdir maintainx-integration && cd maintainx-integration npm init -y npm install axios dotenv npm install -D typescript tsx vitest @types/node npx tsc --init --target ES2022 --module NodeNext --moduleResolution nodenext --outDir dist ``` Create `tsconfig.json` paths: ```json { "compilerOptions": { "target": "ES2022", "module": "NodeNext", "moduleResolution": "nodenext", "outDir": "dist", "strict": true, "esModuleInterop": true }, "include": ["src/**/*"] } ``` ### Step 2: Project Structure ``` maintainx-integration/ ├── src/ │ ├── client.ts # MaintainX API client (from install-auth) │ ├── work-orders.ts # Work order service layer │ └── sync.ts # Data sync logic ├── tests/ │ ├── client.test.ts # Unit tests with mocks │ └── integration.test.ts # Live API tests ├── .env # MAINTAINX_API_KEY=... ├── .env.example # MAINTAINX_API_KEY=your-key-here ├── package.json └── tsconfig.json ``` ### Step 3: Dev Scripts in package.json ```json { "scripts": { "dev": "tsx watch src/index.ts", "test": "vitest run", "test:watch": "vitest", "test:integration": "INTEGRATION=true vitest run tests/integration.test.ts", "build": "tsc", "repl": "tsx src/repl.ts" } } ``` ### Step 4: Write Unit Tests with Mocked API ```typescript // tests/client.test.ts import { describe, it, expect, vi, beforeEach } from 'vitest'; import axios from 'axios'; vi.mock('axios'); describe('MaintainXClient', () => { beforeEach(() => { vi.resetAllMocks(); process.env.MAINTAINX_API_KEY = 'test-key-123'; }); it('creates a work order', async () => { const mockResponse = { data: { id: 1, title: 'Test WO', status: 'OPEN' }, }; vi.mocked(axios.create).mockReturnValue({ post: vi.fn().mockResolvedValue(mockResponse), interceptors: { response: { use: vi.fn() } }, } as any); const { MaintainXClient } = await import('../src/client'); const client = new MaintainXClient(); const result = await client.createWorkOrder({ title: 'Test WO' }); expect(result.data.title).toBe('Test WO'); expect(result.data.status).toBe('OPEN'); }); it('paginates work orders', async () => { const page1 = { data: { workOrders: [{ id: 1 }], cursor: 'abc' } }; const page2 = { data: { workOrders: [{ id: 2 }], cursor: null } }; const getMock = vi.fn() .mockResolvedValueOnce(page1) .mockResolvedValueOnce(page2); vi.mocked(axios.create).mockReturnValue({ get: getMock, interceptors: { response: { use: vi.fn() } }, } as any); const { MaintainXClient } = await import('../src/client'); const client = new MaintainXClient(); const all = []; let cursor: string | undefined; do { const { data } = await client.getWorkOrders({ cursor }); all.push(...data.workOrders); cursor = data.cursor; } while (cursor); expect(all).toHaveLength(2); }); }); ``` ### Step 5: Interactive REPL ```typescript // src/repl.ts import * as repl from 'node:repl'; import 'dotenv/config'; import { MaintainXClient } from './client'; const client = new MaintainXClient(); console.log('MaintainX REPL ready. `client` is available.'); console.log('Try: await client.getWorkOrders({ limit: 3 })'); const r = repl.start({ prompt: 'maintainx> ' }); r.context.client = client; ``` ```bash # Start REPL npm run repl # maintainx> const { data } = await client.getWorkOrders({ limit: 3 }) # maintainx> data.workOrders.map(wo => wo.title) ``` ## Output - TypeScript project configured with `tsx watch` for hot reload - Vitest unit tests with mocked MaintainX API responses - Interactive REPL for exploring the API - `.env.example` template for team onboarding - Dev/test/build scripts in `package.json` ## Error Handling | Issue | Solution | |-------|----------| | `MAINTAINX_API_KEY` undefined | Copy `.env.example` to `.env` and fill in your key | | 429 Rate Limited during dev | Add delays between calls, use mocks for unit tests | | TypeScript import errors | Ensure `moduleResolution: "nodenext"` in tsconfig | | `tsx` not found | Install with `npm i -D tsx` | ## Resources - MaintainX API Reference - [Vitest Documentation](https://vitest.dev/) - [tsx - TypeScript Execute](https://github.com/privatenumber/tsx) ## Next Steps For SDK patterns and best practices, see `maintainx-sdk-patterns`. ## Examples **Docker-based dev environment**: ```dockerfile # Dockerfile.dev FROM node:20-slim WORKDIR /app COPY package*.json ./ RUN npm install COPY . . CMD ["npm", "run", "dev"] ``` ```yaml # docker-compose.dev.yml services: app: build: { dockerfile: Dockerfile.dev } env_file: .env volumes: ["./src:/app/src"] ``` **Run integration tests against live API**: ```bash INTEGRATION=true npm run test:integration ```
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__maintainx-local-dev-loop.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Maintainx Local Dev Loop skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Maintainx Local Dev Loop safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Maintainx Local Dev Loop access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Maintainx Local Dev Loop work with?
Its documentation mentions claude-code and cursor. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.