◇ Could this help me?
Yes. These are the controls that separate a usable skill library from a pile of overlapping prompts, and the two that matter most are the least used: invocation flags remove the ambiguity about whether a skill is a command or a capability, and arguments stop a library from growing one near-duplicate skill per variation. Pinning a cheaper model per skill is a real saving on skills that run often and need no judgment. General practice for anyone authoring skills, and the argument pattern is worth applying retroactively to any existing skill that currently asks a clarifying question every time it runs.
Review my existing skills for two things. First, find any set of skills that are near-duplicates of each other and differ only by one value, such as an environment or a target, and rewrite them as a single skill that takes that value as an argument. Second, for each skill tell me whether it should be invocable by you, by me, or by both, and set the flags accordingly with your reasoning. Also flag any skill that runs frequently and requires no real judgment, since those are candidates for pinning to a cheaper model, and tell me what I would lose by doing that.