CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

jbaruch/reclaim-tripit-sync

Syncs TripIt travel itineraries to Reclaim.ai timezone segments and Google Calendar OOO blocks.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

runtime-state.mdskills/sync-tripit/references/

Installed runtime snapshot

skills/sync-tripit/scripts/runtime-state.mjs owns and is the only reader/writer of INSTALL_DIRECTORY/.sync-runtime.json. The installer calls seal only after a successful staged dependency installation, and check before reusing it. Both commands emit a JSON result with operation, ready, path and requestedVersion; the installer consumes it and emits its own single result.

Schema version 1 is one JSON object: schema_version (1), requestedVersion (release semver), and files (relative managed file paths to SHA-256 hex strings). The owner inventories the entrypoint, package metadata, library files and npm's hidden lock. It checks their live bytes, installed package directories and local resolution of required dependencies. It never imports the application or reads .env. The snapshot proves installation completion, not authorization.

A missing, malformed, older, or mismatched-version snapshot means no usable prior state. A mismatch with the live filesystem also requires repair. The installer stages a fresh pinned installation and the owner writes a new version-1 snapshot. A newer schema refuses both checking and sealing with exit 4 and an actionable reader-update diagnostic; it is never overwritten by an older owner. Configuration is preserved. There are no readers in another release pipeline.

README.md

tile.json