agentsclimarketplace

Architecture zoo

Skill Aperivue/medsci-skills/skills/architecture-zoo

Choose a model architecture for a medical-imaging research question before scaffolding. Maps the task (classification, segmentation, detection, transfer), modality and dimensionality, labelled-data scale, and class imbalance to a shortlist of architectures, each grounded in its source paper with a when-to-use, a medical-imaging use, a reference implementation, the typical validation setup, and the matching model-scaffold template. Covers the foundational curriculum (ResNet, DenseNet, EfficientNet, ViT, Swin; U-Net, 3-D U-Net, Attention/Residual U-Net, nnU-Net (+ ResEnc/MedNeXt/STU-Net), Mask R-CNN; SAM/MedSAM, nnInteractive/VISTA3D interactive-3D, TotalSegmentator, BiomedCLIP, DINO/MAE/SimCLR; and graph neural nets — GCN/GraphSAGE/GAT/GIN/BrainGNN — for brain connectomes). It teaches archetypes and the task-to-architecture logic (including the "scale the CNN, new≠better" rigour caveat), not a live SOTA leaderboard.From its SKILL.md

Install
npx -y skills add Aperivue/medsci-skills --skill architecture-zoo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

6.5 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it

Architecture-Zoo Skill

Purpose

This skill turns a medical-imaging research question into a paper-grounded architecture choice — so the build starts from the right archetype (and a known validation setup) rather than from whatever is fashionable, and the choice carries its source citation into the Methods. It is the front end of the model-engineering lane: architecture-zoo (choose)/model-scaffold (build)/model-validation (validate).

It is advisory (Layer D): it writes a short decision note, never code or weights. The actual repo is /model-scaffold. It describes archetypes and the task → family → constraint logic, not a live SOTA leaderboard (SOTA churns; the logic does not).

When to use

  • You need to pick an architecture/backbone for a classification, segmentation, detection, or transfer-learning question and want it grounded in the literature with a sensible default.

When NOT to use

  • Generating the runnable repo → /model-scaffold.
  • Auditing a trained model's validation design → /model-validation.
  • Metrics / calibration → /model-evaluation + /analyze-stats.
  • General study/validity design → /design-study; AI-vs-expert benchmark → /design-ai-benchmarking.
  • LLM / MLLM → /mllm-eval.

Workflow

Phase 1 — Frame the question

State the task (classification / segmentation / detection / transfer), the modality + dimensionality (2-D vs 3-D volume), the labelled-data scale (events / structures, not just images), label availability (lots / few / unlabelled pool), and constraints (class imbalance, small structures, interpretability, deployment compute).

Phase 2 — Walk the decision tree

Open ${CLAUDE_SKILL_DIR}/references/index.md and follow task → constraints → default pick. It routes to a family card.

Phase 3 — Read the family card

  • ${CLAUDE_SKILL_DIR}/references/classification.md — ResNet / DenseNet / EfficientNet / Inception / ViT / Swin / DeiT.
  • ${CLAUDE_SKILL_DIR}/references/segmentation.md — U-Net / 3-D U-Net / V-Net / Attention & Residual U-Net / nnU-Net / SegResNet / Swin-UNETR / Mask R-CNN.
  • ${CLAUDE_SKILL_DIR}/references/detection.md — R-CNN family / Faster R-CNN + FPN / Mask R-CNN / RetinaNet / YOLO / DETR.
  • ${CLAUDE_SKILL_DIR}/references/synthesis.md — Pix2Pix / CycleGAN / SPADE / diffusion (DDPM, latent) / VAE / fastMRI reconstruction.
  • ${CLAUDE_SKILL_DIR}/references/foundation_models.md — SAM / MedSAM / MedSAM2 / TotalSegmentator / SegVol / BiomedCLIP / DINO / MAE / SimCLR / MoCo.
  • ${CLAUDE_SKILL_DIR}/references/graph.md — GCN / GraphSAGE / GAT / GIN / BrainGNN for brain connectomes & population graphs (integrate PyTorch Geometric / DGL; not scaffolded by model-scaffold). Each card gives the paper, core idea, when-to-use, medical-imaging use, reference implementation, and the typical validation/experiment setup for that architecture class.

Phase 4 — Write the decision note

Record decisions/architecture_choice.md: the task, the chosen architecture, its source paper, the reason against the constraints, the runner-up + why not, and the matching /model-scaffold template. Naming the source paper is mandatory; cite, never invent, any benchmark number.

Phase 5 — Hand off

Carry the decision note to /model-scaffold (instantiate the template), then /model-validation (split / validation design), /model-evaluation + /analyze-stats (metrics), and /write-paper (the Methods cite the architecture's source paper).

Anti-Hallucination

  • Never recommend an architecture without naming its source paper. Every card cites the paper; the decision note must carry that citation.
  • Never invent benchmark numbers or paper claims. If a number matters, cite it (verify via /search-lit); if uncertain, write [VERIFY] and ask.
  • Never recommend an architecture for a modality or data scale it does not suit (e.g. a from-scratch ViT on a few hundred images, or 2-D slices for a volumetric structure) — the constraints in the decision tree exist to prevent exactly that.
  • The zoo is a curated archetype map, not a current SOTA ranking — say so rather than implying a recommendation is the latest best.

Boundaries

architecture-zoo (this skill: choose, paper-grounded)
  └─ model-scaffold (build the reproducible repo from the chosen template)
       └─ model-validation -> model-evaluation -> write-paper (cite the source paper)

It does not build, train, evaluate, or rank live SOTA — it maps the research question to a defensible, paper-grounded archetype and hands the choice to /model-scaffold.

What ships with it: 8 files

51.4 KB alongside SKILL.md

Gives 0 of the 12 instructions most project setup skills give in ~1.2k tokens

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

  • Write the configuration filein 36 of 1553
  • Create the directory structurein 35 of 1553, across 33 files
  • Verify the setupin 31 of 1553, across 28 files
  • Run the setup scriptin 30 of 1553, across 29 files
  • Pre-determine the required sample sizein 29 of 1553, across 12 files
  • Check if the configuration already existsin 29 of 1553
  • Document every testin 26 of 1553, across 10 files
  • Start with a hypothesisin 26 of 1553, across 11 files
  • Ask one question at a timein 22 of 1553
  • Test a single variable per testin 21 of 1553, across 9 files
  • Read product marketing context before asking questionsin 19 of 1553, across 8 files
  • Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

  • Frame the question by task, modality, dimensionality, scale, and constraints.
  • Walk the decision tree to route to a family card.
  • Read the family card for paper, idea, and validation setup.
  • Record the decision note with task, architecture, and source paper.
  • Carry the decision note to model-scaffold and model-validation.
  • Name the source paper when recommending an architecture.

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.