Drop down text put into several places of same macro

I like to use some hidden rolls in my game when no players ask for rolls. For example they see some mushrooms, I will secretly roll nature for all and then whisper information to those that succeed. Currently I use one macro for each skill, but this is a pain to manage when creating new games or people change names. I want a drop down menu that inputs the skill into the macro. But since the skill  bonus is 12 different places, can the same drop down menu input the same value in all those 12 places? So if i choose Arcana in drop down menu, all the "arcana_bonus" will happen. If I choose insight, it will be updated with "insight_bonus" etc. /w gm  &{template:default} {{name=Arcana}} {{Exar (@{Exar|arcana_bonus})=[[d20+@{Exar|arcana_bonus}]] [[d20+@{Exar|arcana_bonus}]] }}{{Talvan Alendar(@{Talvan Alendar|arcana_bonus})=[[d20+@{Talvan Alendar|arcana_bonus}]] [[d20+@{Talvan Alendar|arcana_bonus}]] }}{{Puncher(@{Puncher|arcana_bonus})=[[d20+@{Puncher|arcana_bonus}]] [[d20+@{Puncher|arcana_bonus}]] }}{{Xernath Yarjerit(@{Xernath Yarjerit|arcana_bonus})=[[d20+@{Xernath Yarjerit|arcana_bonus}]] [[d20+@{Xernath Yarjerit|arcana_bonus}]] }}

I was going to suggest using a Chat Menu in place of a drop down, but you do still have the tricky problem of dealing with specific character names. A script might be a better solution, where you supply a list of character names, and which skill (through a dropdown), and it prints out the hidden roll template above.  Why do you have the roll+bonus repeated twice for each character? 

I'd suggest the Group Check script. It was made for applications like this. It's in the drop down.

Thank you. The group check script might work. And i see its used for other useful things :) GiGs: In d&d 5e you can have advantage/disadvantage on the roll. Which means you roll twice and take best/worst.

To answer the question: Yes, if you name the second query exactly the same as the first, roll20 will copy the first answet without asking again.  But you want to have the query inside an attribute-call. This might not work because of the order of operations.