Conversation
| } | ||
| }, | ||
| "contextFileName": "CLOUD-SQL-POSTGRESQL.md", | ||
| "settings": [ |
There was a problem hiding this comment.
Have you tested with the settings in the .env and having the extension load in the env vars? Does this allow the agents to use these variables without additional input from the user?
There was a problem hiding this comment.
Haoyu has edited his implementation to update the scripts to get the env vars from the global extension path. It is automatically set when the user runs gemini extensions install.
| @@ -0,0 +1,704 @@ | |||
| --- | |||
| name: cloudsql-postgres | |||
| description: skill for running tool operations in CloudSql postgres | |||
There was a problem hiding this comment.
For the first iteration, we will have to manually add the descriptions since Grouping (with the descriptions) most likely wont be complete.
There was a problem hiding this comment.
Do you mean grouping will be complete but without the descriptions? For now, I will add the descriptions manually.
|
Thank you Twisha for authoring this PR! After looking at the generated config, I realized there should be some improvements done to the skill generation logic we previously introduced.
|
9b122ab to
dca7c08
Compare
add presubmit workflow for skills fix workflow Update skills-validate.yml fix workflows ignore skills dir for license headers update docs fix header check fix copyright year test failure for validation workflow revert skill testing failure revert license file changes add year pattern regex test header check years Update header-check.yml Update settings fix env var propagation address comment
dca7c08 to
c405d16
Compare
Does not yet contain support for multiple sub-toolsets for cloudsql postgres