Maintainx Data HandlingSAFE
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-09Host 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-data-handling description: 'Data synchronization, ETL patterns, and data management for MaintainX. Use when syncing data between MaintainX and other systems, building ETL pipelines, or managing data consistency. Trigger with phrases like "maintainx data sync", "maintainx etl", "maintainx export", "maintainx data migration", "maintainx data pipeline". ' allowed-tools: Read, Write, Edit, Bash(npm:*) version: 1.11.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - maintainx - migration - data-pipeline - etl compatibility: Designed for Claude Code --- # MaintainX Data Handling ## Overview Patterns for synchronizing, transforming, and exporting data between MaintainX and external systems (databases, data warehouses, ERPs). ## Prerequisites - MaintainX API access configured - Node.js 18+ with `axios` - Target database or data warehouse available ## Instructions ### Step 1: Incremental Sync with Cursor Pagination ```typescript import { MaintainXClient } from './client'; import { writeFileSync, existsSync, readFileSync } from 'fs'; const SYNC_STATE_FILE = '.maintainx-sync-state.json'; interface SyncState { lastSyncAt: string; workOrderCursor?: string; assetCursor?: string; } function loadSyncState(): SyncState { if (existsSync(SYNC_STATE_FILE)) { return JSON.parse(readFileSync(SYNC_STATE_FILE, 'utf-8')); } return { lastSyncAt: new Date(0).toISOString() }; } function saveSyncState(state: SyncState) { writeFileSync(SYNC_STATE_FILE, JSON.stringify(state, null, 2)); } async function incrementalSync(client: MaintainXClient) { const state = loadSyncState(); const syncStart = new Date().toISOString(); console.log(`Syncing changes since ${state.lastSyncAt}`); // Sync work orders updated since last run let cursor: string | undefined; let totalWOs = 0; do { const response = await client.getWorkOrders({ updatedAtGte: state.lastSyncAt, limit: 100, cursor, }); for (const wo of response.workOrders) { await upsertWorkOrder(wo); // Your DB write function totalWOs++; } cursor = response.cursor ?? undefined; } while (cursor); // Sync assets updated since last run let assetCursor: string | undefined; let totalAssets = 0; do { const response = await client.getAssets({ updatedAtGte: state.lastSyncAt, limit: 100, cursor: assetCursor, }); for (const asset of response.assets) { await upsertAsset(asset); // Your DB write function totalAssets++; } assetCursor = response.cursor ?? undefined; } while (assetCursor); saveSyncState({ lastSyncAt: syncStart }); console.log(`Synced ${totalWOs} work orders, ${totalAssets} assets`); } ``` ### Step 2: Export to CSV ```typescript import { createWriteStream } from 'fs'; async function exportWorkOrdersToCSV(client: MaintainXClient, outputPath: string) { const stream = createWriteStream(outputPath); stream.write('id,title,status,priority,assignee,asset,location,created_at,completed_at\n'); let cursor: string | undefined; let count = 0; do { const response = await client.getWorkOrders({ limit: 100, cursor }); for (const wo of response.workOrders) { const row = [ wo.id, `"${(wo.title || '').replace(/"/g, '""')}"`, wo.status, wo.priority, wo.assignees?.map((a: any) => a.id).join(';') || '', wo.assetId || '', wo.locationId || '', wo.createdAt, wo.completedAt || '', ].join(','); stream.write(row + '\n'); count++; } cursor = response.cursor ?? undefined; } while (cursor); stream.end(); console.log(`Exported ${count} work orders to ${outputPath}`); } // Usage await exportWorkOrdersToCSV(client, 'work-orders-export.csv'); ``` ### Step 3: Export to BigQuery ```typescript import { BigQuery } from '@google-cloud/bigquery'; const bq = new BigQuery({ projectId: 'your-project' }); const dataset = bq.dataset('maintenance'); const table = dataset.table('work_orders'); async function syncToBigQuery(client: MaintainXClient) { let cursor: string | undefined; const batch: any[] = []; do { const response = await client.getWorkOrders({ limit: 100, cursor }); for (const wo of response.workOrders) { batch.push({ id: wo.id, title: wo.title, status: wo.status, priority: wo.priority, asset_id: wo.assetId, location_id: wo.locationId, created_at: wo.createdAt, completed_at: wo.completedAt, synced_at: new Date().toISOString(), }); } cursor = response.cursor ?? undefined; } while (cursor); if (batch.length > 0) { await table.insert(batch); console.log(`Inserted ${batch.length} rows into BigQuery`); } } ``` ### Step 4: Data Reconciliation ```typescript async function reconcile(client: MaintainXClient, localDb: any) { const remoteOrders = await paginate( (cursor) => client.getWorkOrders({ limit: 100, cursor }), 'workOrders', ); const localOrders = await localDb.query('SELECT id, updated_at FROM work_orders'); const remoteMap = new Map(remoteOrders.map((wo: any) => [wo.id, wo.updatedAt])); const localMap = new Map(localOrders.map((row: any) => [row.id, row.updated_at])); const missing = remoteOrders.filter((wo: any) => !localMap.has(wo.id)); const stale = remoteOrders.filter( (wo: any) => localMap.has(wo.id) && localMap.get(wo.id) < remoteMap.get(wo.id), ); const orphaned = localOrders.filter((row: any) => !remoteMap.has(row.id)); console.log(`Missing locally: ${missing.length}`); console.log(`Stale locally: ${stale.length}`); console.log(`Orphaned locally: ${orphaned.length}`); return { missing, stale, orphaned }; } ``` ## Output - Incremental sync with persistent cursor state - CSV export of work orders with proper quoting - BigQuery streaming insert pipeline - Data reconciliation report
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-data-handling.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 Data Handling 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 Data Handling 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 Data Handling access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Maintainx Data Handling 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.