JarvusInnovations

@jarvusinnovations source repo

19 skills
0 followers
19 hours ago last updated

▌
Otter Axi · jarvusinnovations
AXI-compliant CLI for Otter.ai — find and pull meeting transcripts from the terminal with token-efficient TOON output. Use when the user wants to search their Otter meetings (by keyword, date range, title, attendee, channel, or folder), browse recent conversations, or pull a full meeting transcript by id/URL. Wraps Otter's hosted MCP server over OAuth; prefer this over the hosted MCP connector for scriptable, headless access.

0
installs
▌
Metabase Axi · jarvusinnovations
AXI-compliant CLI for Metabase — query and explore a Metabase instance from the terminal with token-efficient TOON output. Use when the user wants to run SQL/MBQL against Metabase, execute or inspect saved questions (cards), introspect database schema (tables/fields/types), search Metabase content, browse dashboards/collections, or export query results to a file. Prefer this over raw Metabase API calls.

0
installs
▌
Specs · jarvusinnovations bundle
The companion skill

0
installs
▌
Remarkable Axi · jarvusinnovations bundle
Use this skill for anything involving a reMarkable tablet. That includes sending or uploading a PDF, EPUB, or URL to the tablet; designing, rendering, or checking a page, flyer, or document against the reMarkable's e-ink screen; browsing or organizing what's on the tablet; and downloading handwriting, ink, annotations, or typed notes off it. Use it immediately whenever notes or handwriting on a reMarkable appear missing or lost — blank pages the user knows they wrote on, ink gone after a sync, or annotations possibly destroyed by replacing a document — because it contains the step-by-step ink-recovery procedure, and the first rule is to stop touching the device. If a query mentions a reMarkable (or "my tablet" in a reMarkable context) plus documents, pages, notes, ink, or sync, use this skill. Do not use it for other devices or apps (iPad, Kindle, Notion), generic file recovery, or printing questions unrelated to the tablet.

0
installs
▌
Gitsheets · jarvusinnovations bundle
Use this skill whenever the user is working with `gitsheets` — the git-backed document store on npm. Trigger on mentions of `gitsheets`, `.gitsheets/<name>.toml` configs, sheet path templates with `${{ field }}` syntax, content-typed records (markdown with TOML frontmatter), the `git sheet` / `gitsheets` CLI, `openRepo` / `openSheet` / `openStore` / `repo.transact` API calls, or push-daemon setup. Also trigger when the user shows a TOML record file, asks about validating records with JSON Schema layered with Zod/Valibot, mentions canonical TOML normalization, or asks how to model document-style records (blog posts, knowledge bases) in a git repo. Reach for this skill *before* improvising — gitsheets has a specific API shape and config grammar that's easy to get subtly wrong.

0
installs
▌
Specops · jarvusinnovations bundle
Spec-driven development workflow where specs are the source of truth, paired with a plan protocol for tracking work-in-flight as a micro-DAG. Use this skill whenever starting new features, planning implementation, writing specs, reviewing code against specs, working in or with a `plans/` directory, closing out a plan, or when the user mentions "spec", "specs/", "spec-first", "plans/", "plan protocol", "closeout commit", or asks how something should work or what to work on next. Also use when creating a new project that will use this development methodology, or when onboarding someone to a spec-driven codebase.

0
installs
▌
Harvest Axi · jarvusinnovations
Review, log, and edit Harvest time entries from the terminal. Use when asked to review tracked time over a period (for yourself, the team, a project, or a client), summarize hours, check today's entries or a running timer, log time, or edit/delete timesheet entries. Triggers on "Harvest", "time entries", "timesheet", "how many hours", "log time", "review my week", "billable hours".

0
installs
▌
Hologit · jarvusinnovations bundle
Configure and use hologit, a Git-native framework for declarative code automation. Use when working with .holo/ directories, holobranches, holosources, holomappings, hololenses, TOML configuration files under .holo/, the git holo CLI, or stock lenses (helm3, kustomize, k8s-normalize, k8s-patch, npm-install, npm-run, mkdocs, shell). Triggers on: configuring .holo/, adding sources, creating holobranches, setting up mappings, applying lenses, projecting branches, or any hologit-related task.

0
installs
▌
Slack Axi · jarvusinnovations
Read, search, and cite Slack from the shell. Use when asked to read or summarize a Slack channel, find a discussion across Slack, look up private channels / group DMs / DMs, read a channel over a date range, follow a thread, or produce permalink citations for Slack messages. Token-efficient TOON output; human date ranges in, permalinks out.

0
installs
▌
Axi Skills · jarvusinnovations bundle
Packaging-and-distribution recipe for baking an AXI CLI (axi-sdk-js) into a Claude Code skill — bundling it under the skill's scripts/ as a self-contained committed .mjs shipped via `npx skills add`. This is the build/ship companion to the upstream `axi` skill: `axi` covers what good agent-facing CLI output looks like (TOON, schemas, content-first); this covers how to ship that CLI *inside a skill*. Use whenever you're turning an AXI tool into an installable skill, or working on any of its moving parts — the esbuild → committed .mjs build, the bash shim, the SessionStart hook (install/uninstall/status, project vs global scope), generating SKILL.md from a single-source command reference, the CI drift gate, or splitting a lean every-session "home" view from an on-demand live "dashboard". Triggers: "bundle my CLI in a skill", "AXI in a skill", "ship this CLI via npx skills", "self-contained skill bundle", "add a session-start hook to my skill", "generate SKILL.md from the CLI", or noticing a repo with `scripts/b

1
install
▌
Jarvus Dbt · jarvusinnovations bundle
Jarvus house conventions for writing, testing, and linting dbt projects — model layering and grain, what each stage may/may not do, the no-inner-joins and semantic-alias rules, the fast (<5 min) local dev-loop requirement, the no-unvalidated-demo-work-in-main rule, the generic + quality-model + unit-test patterns, the sqlfluff config, and a credential-free multi-tenant CI gate. Use when building or reviewing dbt models, deciding materialization or test coverage, setting up dbt linting/CI, or when "dbt", "sqlfluff", "staging/intermediate/marts", "dbt test", or "TIDES" come up. This is the opinionated house layer ON TOP OF dbt-labs' first-party dbt skills (which cover the mechanics) — see "Relationship to other skills".

1
install
▌
Repo Setup · jarvusinnovations bundle
Stand up a new Jarvus repository the house way — the one-time bootstrap that wires `develop` as the default branch, `main` as the release target, merge-commit-only merge policy, branch rulesets that keep auto-delete from eating `develop`, and the `JarvusInnovations/infra-components` Release-PR workflows. Use when creating a new repo, running `gh repo create`, pushing an existing local project to GitHub for the first time, adopting the develop→main release flow in a repo that lacks it, or auditing an existing repo against house conventions. Also use when something in the branch/merge plumbing misbehaves: `develop` vanished after a release merged, a release PR reports "No commits between main and develop", PR checks sit at `action_required` on a new repo, someone squash-merged, or a first npm publish fails from CI. Triggers: "new repo", "create a repo", "set up a repo", "gh repo create", "push this to GitHub", "repo settings", "branch protection", "rulesets", "default branch", "develop branch is gone", "set up

1
install
▌
Jarvus Extjs · jarvusinnovations bundle
Maintain, stabilize, and clean up the Jarvus/Slate ExtJS 6.2 classic-toolkit web apps — SlateAdmin, the Slate CBL apps (SlateTasksTeacher/Student/Manager, SlateDemonstrations*, SlateStudentCompetenciesAdmin), and anything else living in a sencha-workspace/. Use this whenever the task touches Ext.define, Ext.app.Controller, a Sencha workspace, app.json, an ExtJS view/store/model/proxy, jarvus-* or slate-* Sencha packages, writing or debugging Cypress e2e specs for these apps, or fixing bugs and jank in these apps — even if the user just says "the admin UI" or "the teacher dashboard". The stack is frozen on Ext 6.2.0.981: this skill encodes the house patterns to converge on and the upgrades/migrations to explicitly NOT attempt.

1
install
▌
Jarvus React · jarvusinnovations bundle
Build or maintain Jarvus frontend applications that use Bun, Vite, React 19, TypeScript, Tailwind CSS v4, and React Router v7. Use when a repository already uses this stack or when the user explicitly asks to bootstrap or migrate to it; preserve an existing package manager, framework, and routing mode unless migration is requested. shadcn/ui is optional.

1
install
▌
Release Flow · jarvusinnovations bundle
Cut a release in a repo that uses the Jarvus develop→main Release-PR automation (the JarvusInnovations/infra-components release-prepare/validate/publish GitHub Actions). Use this whenever you're shipping merged work to production, drafting or editing a "Release: vX.Y.Z" PR, deciding a version bump, writing release notes/changelog, or the user says "ship it", "cut a release", "publish", "do the release", "merge the release PR", or "release notes". Also use it the moment you notice a repo has `.github/workflows/release-prepare.yml` (or release-publish/release-validate) or an open PR titled "Release: v*" — that's the signal this workflow is in effect. Covers: pushing develop to open the Release PR, pulling the bot-generated changelog, sorting commits into Improvements vs Technical, recommending semver bump, and merging to publish.

1
install
▌
Jarvus Fastify · jarvusinnovations bundle
Backend development using Fastify + TypeScript on Bun. Use when creating new backend APIs, adding routes, implementing services, working with plugins, or configuring environment variables.

1
install
▌
Jarvus Flutter · jarvusinnovations bundle
Mobile app development using Flutter + Riverpod + go_router. Use when creating Flutter apps, adding screens, managing state with Riverpod, implementing routing, building offline-first features, or setting up storybook component development. Also use when the user mentions Flutter, Dart, mobile apps, or cross-platform development.

1
install
▌
CI Quality Gates · jarvusinnovations bundle
Stand up the pre-merge CI quality gates a repo runs before code lands on develop — tool provisioning (asdf + .tool-versions + cache), lockfile-frozen installs, path-filtered GitHub Actions, and the lint / format:check / typecheck / test gate set with Jarvus's standard linters (oxlint + oxfmt for TypeScript, ruff for Python, tofu fmt/validate for IaC). Use when setting up CI for a new repo, adding a lint/format/type-check/test gate to an existing one, wiring GitHub Actions for code quality, choosing or standardizing linters/formatters, fixing CI that re-installs tools slowly, or noticing a repo runs tests but no linter. Scope stops at merge — Release-PR automation belongs to release-flow; build/publish/deploy to per-stack build + deploy skills. Triggers: "set up CI", "add linting/CI", "GitHub Actions checks", "oxlint", "oxfmt", "ruff", "format check", "type-check in CI", "quality gate", "lint isn't running in CI", "asdf in CI".

1
install
▌
Agent Dev Workflow · jarvusinnovations bundle
Set up an agent-friendly local dev workflow — a bin/ task-runner (inspired by GitHub's scripts-to-rule-them-all) over a shared Postgres container that gives every git worktree its own isolated database and ports, plus a dedicated test database so tests never clobber dev data. Use this whenever a project needs worktree-isolated local development, when setting up for AI agent orchestrators (Conductor and similar) that spin up a worktree per session and register setup/run/cleanup commands, when multiple copies of a backend must run concurrently on one machine, when replacing a docker-compose-for-local-postgres setup, when deciding whether auxiliary dev services (a validator container, a local OIDC IdP) replicate per worktree or run shared, when merged agent worktrees pile up and need sweeping, when idle per-project Postgres containers or leftover dev servers accumulate on a machine and need auditing or shutting down, or when tests keep wiping local dev/demo data. Triggers on "bin/ scripts", "worktree isolation",

1
install

19 published skills