The request sounded simple: could omaTrail learn from the original Oregon Trail without becoming a copy of it?
We treated that as three separate requirements:
- Preserve the decisions that made the early game memorable.
The request sounded simple: could omaTrail learn from the original Oregon Trail without becoming a copy of it?
We treated that as three separate requirements:
The public reports hub for the Intent Eval Platform — it verifies signed evidence before it renders a single row, and refuses to let one number lie about many predicates.
intent-eval-dashboard is the 6th member of the Intent Eval Platform and its satellite consumer — not one of the 5 convergence repos. It ingests DSSE-signed Evidence Bundles from the platform repos, re-verifies every one (OIDC subject, Rekor inclusion proof, DSSE signature, kernel schema) before rendering, and publishes the results as a static hub at labs.intentsolutions.io. Methodology-first by design: the eval-set browser ships before any results browser, so readers see what was measured before they see how it scored.
Links: GitHub · [Live site](https://labs.intentsoluti
Self-hosted, auditable email triage for Claude — Gmail and Outlook, with real actions.
IntentMail is a single-repo, self-hosted MCP server (+ CLI/TUI, Discord bot, and web dashboard) that gives an AI assistant a full grip on your inbox: daily-digest triage with priority and "why", long-thread summaries, group-by-category, and actual write actions (archive / flag / move / draft / delete) across Gmail and Microsoft Graph — while you hold the OAuth token and the mailbox never leaves your machine.
How the cost-leak hunter actually works under the hood: the filesystem, the data model it reads, the SQL primitive, the four detectors, and the deterministic ranker — exposed.
| Skill | databricks-cost-leak-hunter |
| Version | 0.1.0 |
| Author | Jeremy Longshore <jeremy@intentsolutions.io> |
| License | MIT |
Make AI-assisted open-source contributions land cleanly — caught by deterministic gates before they reach maintainers as slop.
A local-only Claude Code skill plus workspace for contributing to open-source projects you don't own. It runs 51 deterministic safety gates over every claim comment, design issue, and pull request, so AI-generated work never reaches an upstream maintainer as low-quality "slop." State is plain markdown — greppable, git-trackable, no database, no cloud calls.
Links: GitHub · Latest release
audit-harness — @intentsolutions/audit-harness one-pager + operator audit + changelog
Deterministic test-enforcement toolkit — hash-pinned policy, escape-scan refusal gates, CRAP scoring, architecture checks, and signed evidence emission, installed in the repo it governs.
A zero-runtime-dependency CLI (Node dispatcher + bash/Python scripts) that makes test-quality policy enforceable on fresh clones. Companion to the audit-tests and implement-tests Claude Code skills, and the deterministic-gates layer of the Intent Eval Platform — but usable standalone in any repo.
intent-eval-core — @intentsolutions/core one-pager + operator audit + changelog
The canonical contracts kernel for the Intent Eval Platform — types, schemas, and validators with no runtime attached.
TypeScript types, JSON Schemas (draft 2020-12), generated Zod validators, and state machines for the platform's 16 canonical entities, the NORMATIVE gate-result/v1 in-toto predicate, and the bicameral authoring-contract families (authoring/v1, byte-frozen, plus the strict authoring/v2 skill-frontmatter fork). Every validator in the platform — deterministic gates, behavioral evaluators, the rollout-gate decision shell — imports its contract definitions from this one package.
The methodology and specs home of the Intent Eval Platform — where spec authority is kept provably in sync with upstream truth.
A research umbrella for vendor-neutral evaluation methodology around AI plugins, agents, MCP servers, and skill-discovery systems. The repo ships no application code: its outputs are versioned spec modules, normative blueprints, a decision-record governance corpus, and a continuous spec-compliance watcher that monitors 16 upstream spec surfaces daily and feeds the canonical contracts kernel (@intentsolutions/core).
Links:
intent-rollout-gate — one-pager + operator audit + changelog
A GitHub Action that consumes signed Evidence Bundles and decides allow / block for your CI pipeline — fail closed, zero decision logic in the action itself.
intent-rollout-gate is the GitHub Action shell layer of the Intent Eval Platform. It reads an Evidence Bundle (in-toto Statement v1 rows under predicateType https://evals.intentsolutions.io/gate-result/v1), resolves a declared rollout policy, and emits an allow or block decision with full reasoning. Every line of decision logic is delegated to the published @intentsolutions/rollout-gate package (Apache-2.0, sigstore provenance) — the action only wires inputs, files, outputs, and exit codes around it. The consumption contract was frozen at v0.2.0 (2026-06-13); the current release is v0.3.1 (2026-07-05). It is no longer expe
Live demo: https://demos.intentsolutions.io/databricks-cost-leak-hunter/
That's ~$324K/year. The $100K/month spend is the only assumed input; the 27% waste rate is published.¹ Every line below is one config change.
| # | Where it's leaking | $/month | The fix |