simsci-internal

Plugin simsci-internal from marketplace vivarium-ai-tools in ihmeuw/vivarium-suite. Commands read from the repo's manifest — 3 days ago.

Skills (13)

• brainstorming

  Use BEFORE any design or feature work — picking an approach, scoping a change, fleshing out a sparse ticket, deciding whether something needs a design doc. Runs a structured brainstorm with one-question-at-a-time clarification, 2–3 approaches with explicit tradeoffs, ultimately producing a design ar

• continuous-integration

  Use when the user asks about vivarium-suite CI — build status, Jenkins console logs, job structure, GitHub Actions runs, etc. Covers the GH Actions / Jenkins setup, the per-package Multibranch Pipeline layout, URL-to-jobFullName translation for the Jenkins MCP, and parallel matrix log interleaving.

• design-doc

  SimSci Engineering team convention for drafting a Design Document on the IHME hub. Use whenever the user asks to e.g. "draft a design doc", "write a design document", "make a design doc", or "start a PRD".

• environments

  How to pick up the right Python environment in a vivarium repo, and how to create one if you need to. Use whenever you need to run tests, lint, scripts, or execute make commands, anything that imports the package. Also use when the user asks to "set up an environment", "use the shared env", "rebuild

• framework-clis

  Reference for the vivarium-ecosystem console scripts that a standard model-repo conda env puts on PATH — `simulate`, `psimulate`, `vipin`, the per-repo `make_artifacts`, and `update_gbd_round`. Use whenever the task involves running, restarting, expanding, or smoke-testing a vivarium simulation; lau

• make-commands

  Reference for the shared `make` targets used across vivarium repositories, centralized in `vivarium/build_utils/resources/makefiles/`. Use this when the task involves making a new conda environment, formatting code, running development checks, or type hinting. Use whenever the user asks what a `make

• model-development

  Guided iteration loop for a vivarium model — take one model change from a

• plugin-setup

  Use when the user is performing post-install configuration for components shipped by this plugin — work that the plugin install itself doesn't perform.

• pytest

  Reference for the vivarium pytest setup. Use this skill when running, debugging, or developing automated test coverage.

• repo-maintenance

  Audit the repo's AI plaintext — both ai-tools plugins, simsci-internal (tools/ai-tools) and simsci (tools/ai-tools-public) (skills, agents, READMEs), and CLAUDE.md — for drift against the upstream sources those docs mirror, then fix approved findings. Use when the user asks to "audit the skills", "c

• team-conventions

  SimSci Engineering team conventions for everyday git/Jira/PR mechanics — branch naming from a MIC ticket, writing a Jira ticket against the team's hub doc, opening a PR with the repo's `.github/pull_request_template.md` via the GitHub MCP, and flagging the PR for team review in `#vivarium_dev`. Use

• ticket-triage

  Use after a code review when some findings won't be addressed in the current PR — triages them into Jira ticket recommendations. Classifies each unaddressed finding (address-now / ticket / drop), groups ticket candidates by theme, checks the MIC backlog for duplicates via the `_duplicate_finder` sub

• vivarium-research

  Search and retrieve content from the Vivarium Research documentation (vivarium-research.readthedocs.io). Use whenever the user asks, implicitly or explicitly, the specification for how something is modelled in Vivarium — a disease, risk factor, intervention, demographic process, or simulation-compon

Subagents (4)

• _claim_auditor

  Use when: auditing a single AI-plaintext unit (a skill, agent, plugin README, or CLAUDE.md) for drift — extracting its load-bearing checkable claims and verifying each against its upstream source, returning structured findings. Spawned per-unit by the /simsci-internal:repo-maintenance skill.

• _duplicate_finder

  Use when: checking candidate tickets against the Jira backlog for duplicates, returning a compact match list and keeping raw JQL search traffic out of the orchestrator's context.

• _model_implementer

  Use when: implementing one layer of a vivarium model iteration (artifact data-loading, a component/pipeline, or an observer) from an orchestrator-composed stage brief and the iteration plan.

• _vv_writer

  Use when: running an internal, blind verification for a vivarium model iteration — interactive-simulation checks plus a notebook whose plots/tables are posted to the PR as traces — from the iteration plan and the research doc. An engineering-confidence loop, not formal V&V; artifacts are not committ

Hooks (1)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/writing-style.sh"