← all publishers

JarvusInnovations

@jarvusinnovations-claude-assist source repo

Report this profile Claim this profile

• 10 skills
• 0 followers
• 3 days ago last updated

1. ▌
   Axi Skills · jarvusinnovations-claude-assist 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
   2 installs
2. ▌
   Jarvus Fastify · jarvusinnovations-claude-assist 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.
   0 installs
3. ▌
   CI Quality Gates · jarvusinnovations-claude-assist 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".
   0 installs
4. ▌
   Assist Gmail · jarvusinnovations-claude-assist bundle

   Manage Gmail email sync, triage, and analysis workflows. Use when user wants to sync emails, triage inbox, check email analysis results, view email statistics, manage the email processing pipeline, find newsletters, check pending emails, or understand email workflow status. Triggers on phrases like "sync my emails", "triage inbox", "email status", "check newsletters", "email analysis", "what emails do I have", "pending emails", "unsubscribe from newsletters".
   1 install
5. ▌
   Assist Pages · jarvusinnovations-claude-assist bundle

   Publish interactive pages and worksheets to stable URLs and collect structured responses, via the bundled pages-axi CLI. Use whenever a human needs to act on something that outlives the current turn — a decision queue, a review-and-annotate artifact, an option picker — and ALWAYS when collecting quantities a human must physically measure. Triggers: "prep sheet", "worksheet", "publish a page", "collect weights", "make me a form", "send me something to fill in", "what came back from that page", "review page", "check responses".
   1 install
6. ▌
   Assist Kitchen · jarvusinnovations-claude-assist bundle

   Read and write the kitchen consumption journal and inventory via the bundled kitchen-axi CLI. Use to log meals or snacks, adjust a portion after the fact, check today's calorie/macro totals, see what food is on hand or aging (eat-first), scan a grocery receipt, record opening/finishing/tossing an item, answer needs-info questions, or seed products and the receipt lexicon. Triggers: "log this meal", "what did I eat today", "I only ate half", "what's about to expire", "what's in the fridge", "scan this receipt", "I opened/finished/tossed the X", "kitchen inventory".
   2 installs
7. ▌
   Specops · jarvusinnovations-claude-assist 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.
   1 install
8. ▌
   Assist Sessions · jarvusinnovations-claude-assist bundle

   Search past Claude sessions for context. Use when asked "where did we leave off?", "what did we discuss about X?", "find a previous conversation", or when needing context from earlier work across machines. Also use for time-based queries like "what did I work on today/yesterday/this week/this morning?", "what happened on Monday?", "show me everything from last Tuesday", "give me a standup summary", or any request to review work across a time period or across projects.
   2 installs
9. ▌
   Assist Google Setup · jarvusinnovations-claude-assist bundle

   Set up Google accounts for Gmail sync and triage. Use when user wants to add a Gmail account, connect their email, configure email sync settings, set up OAuth authorization, or add name aliases for commitment extraction. Triggers on phrases like "set up gmail", "add google account", "connect my email", "configure email sync", "authorize gmail".
   1 install
10. ▌
    Agent Dev Workflow · jarvusinnovations-claude-assist 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, or when tests keep wiping local dev/demo data. Triggers on "bin/ scripts", "worktree isolation", "per-worktree database/port", "scripts to rule them all", "agent dev environment", "setup/run/cleanup scripts", "shared auxil
    1 install