Skip to content

ai4curation/ai-gene-review / .claude/skills/gocam-curation

gocam-curation

Verified

Evaluate and review GO-CAM (Gene Ontology Causal Activity Model) activities / annotons — molecular-function typing, has-input, causal relations, complexes, evidence — and check their consistency with gene annotation reviews. Use when reviewing cached GO-CAMs under gocams/, filling a GoCamReview YAML (gocams/<id>/<id>-review.yaml), or grounding a module in GO-CAM models.

references/has-input.md

View on GitHub
# `has input`

`has input` names the molecule or entity an activity **targets or transforms**.
It is one of the easiest fields to misread; the wrong filler is QC flag
`HAS_INPUT_MISUSE`.

## Correct filler by activity type

| Activity | `has input` is… | NOT |
|---|---|---|
| Enzyme | the **substrate** being modified | the product |
| Transcription factor | the **target gene** | the DNA molecule itself |
| Receptor | the **downstream effector** it activates | the ligand |
| Transporter | the **cargo** moved | the membrane/compartment |

## The classic error: ligand→receptor

Do **not** use `has input` to record a ligand binding a receptor. The ligand is
an **upstream causal regulator** of the receptor's activity — model it as a
causal edge (ligand activity → receptor activity), not as the receptor's input.
See `causal-relations.md`.

## Rule of thumb

`has input` answers "what does this activity act **on** to do its job?" If the
candidate filler is what *triggers* the activity (a ligand, an upstream signal),
it belongs on a causal edge, not in `has input`.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall