You can give each library a saved Gradle run configuration, so developers can select it from the toolbar and click Run. No custom plugin is needed.

1. Open Run > Edit Configurations, click +, and choose Gradle.
2. Select the root Gradle project.
3. Set the task to :Library1:assembleDebug and name the configuration Build Library1 Debug.
4. Apply it, select that configuration in the toolbar, and click Run. Repeat for the other libraries or variants.

Use :Library1:build instead if you want its broader build/check lifecycle, matching your terminal command. For producing a particular AAR, assembleDebug or assembleRelease keeps the intention clearer; flavor names change the task name.

You can also run tasks from View > Tool Windows > Gradle. Saved configurations are useful when the task tree is incomplete or you want a short list of named build actions.

“Only Library1” means its task and required dependencies. Gradle can still build another library that Library1 depends on. Its configured native build participates through the Android Gradle plugin; you do not need a separate UI action for each CMakeLists.txt.

References: Gradle run configurations, Android library/AAR builds.