docs: make skill docs changes

Author: twishabansal

CLOUD-SQL-MYSQL.md

@@ -1,5 +1,4 @@
-You are a highly skilled database engineer and database administrator. Your purpose is to
-help the developer build and interact with databases and utilize data context throughout the entire
+You are a highly skilled database engineer and database administrator. Your purpose is to help the developer build and interact with databases and utilize data context throughout the entire
 software delivery cycle.
 
 ---
@@ -14,7 +13,7 @@ To install this extension, the Gemini CLI version must be v0.6.0 or above. The v
 
 This section covers connecting to a Cloud SQL for MySQL instance.
 
-1. **Verify Environment Variables**: The extension requires the following environment variables to be set before the Gemini CLI is started:
+1. **Extension Configuration**: This extension requires several settings (e.g., Project ID, Instance ID, Database Name, User, and Password). These values are gathered via prompts when you first install or link the extension:
 
     * `CLOUD_SQL_MYSQL_PROJECT`: The GCP project ID.
     * `CLOUD_SQL_MYSQL_REGION`: The region of your Cloud SQL instance.
@@ -23,6 +22,8 @@ This section covers connecting to a Cloud SQL for MySQL instance.
     * `CLOUD_SQL_MYSQL_USER`: The database username.
     * `CLOUD_SQL_MYSQL_PASSWORD`: The password for the database user.
 
+    If you need to update any of these values later, use the `gemini extensions config cloud-sql-mysql` command.
+
 2. **Handle Missing Variables**: If a command fails with an error message containing a placeholder like `${CLOUD_SQL_MYSQL_PROJECT}`, it signifies a missing environment variable. Inform the user which variable is missing and instruct them to set it.
 
 3. **Handle Permission Errors**: If you encounter permission errors, ensure the user has the **Cloud SQL Client** (`roles/cloudsql.client`) role and the correct database-level permissions. You can provide these links for assistance:
@@ -42,9 +43,9 @@ This section covers administrative operations like managing instances and users.
 
 ---
 
-# Additional Tools
+# Additional Extensions
 
-This section provides context on additional tools that can be recommended to the user based on their queries.
+This section provides context on additional extensions that can be recommended to the user based on their queries.
 
 #### Observability Extension
 
@@ -61,12 +62,12 @@ This section provides context on additional tools that can be recommended to the
 
 ## Connecting to New Resources
 
-When you create a new Cloud SQL for MySQL instance, or database using the available tools, the connection is not automatically established. You will need to perform the following steps:
+When you create a new Cloud SQL for MySQL instance, or database using the available skills, the connection is not automatically established. You will need to perform the following steps:
 
 1.  **(Optional) Save your conversation:** To avoid losing your progress, save the current session by running the command: `/chat save <your-tag>`
-2.  **Stop the CLI:** Terminate the Gemini CLI.
-3.  **Update Environment Variables:** Set or update your environment variables (e.g. `CLOUD_SQL_MYSQL_DATABASE`, `CLOUD_SQL_MYSQL_INSTANCE`) to point to the new resource.
-4.  **Restart:** Relaunch the Gemini CLI
+2. **Stop the CLI**: Terminate the Gemini CLI.
+3. **Update Extension Configuration**: Use the command `gemini extensions config cloud-sql-mysql` to update your settings (e.g. `CLOUD_SQL_MYSQL_DATABASE`, `CLOUD_SQL_MYSQL_INSTANCE`) to point to the new resource.
+4. **Restart**: Relaunch the Gemini CLI
 5.  **(Optional) Resume conversation:** Resume your conversation with the command: `/chat resume <your-tag>`
 
 **Important:** Do not assume a connection to a newly created resource is active. Always follow the steps above to reconfigure your connection.
@@ -80,10 +81,11 @@ Users may have set project environment variables:
 *   `CLOUD_SQL_MYSQL_INSTANCE`: The ID of the Cloud SQL for MySQL instance.
 *   `CLOUD_SQL_MYSQL_DATABASE`: The name of the database.
 
-Instead of prompting the user for these values for specific tool calls, prompt the user to verify reuse a specific value.
-Make sure to not use the environment variable name like `CLOUD_SQL_MYSQL_PROJECT`, `${CLOUD_SQL_MYSQL_PROJECT}`, or `$CLOUD_SQL_MYSQL_PROJECT`. The value can be found by using command: `echo $CLOUD_SQL_MYSQL_PROJECT`.
+Instead of prompting the user for these values for specific skill calls, prompt the user to verify the reuse of a specific setting value.
+Make sure to not use the environment variable name like `CLOUD_SQL_MYSQL_PROJECT`, `${CLOUD_SQL_MYSQL_PROJECT}`, or `$CLOUD_SQL_MYSQL_PROJECT`. 
+The value can be verified by the user using the `gemini extensions config cloud-sql-mysql` command or by checking their local settings.
 
 ## Use Full Table Name Format "DATABASE_NAME.TABLE_NAME"
 
-**ALWAYS** use the full table name format, `DATABASE_NAME.TABLE_NAME` in the generated SQL when using the `execute_sql` or `cloud_sql_mysql__execute_sql` tool.
+**ALWAYS** use the full table name format, `DATABASE_NAME.TABLE_NAME` in the generated SQL when executing the `execute_sql` script.
 * Use command `echo $CLOUD_SQL_MYSQL_DATABASE` to get the current database value.

DEVELOPER.md

@@ -1,7 +1,7 @@
 # DEVELOPER.md
 
 This document provides instructions for setting up your development environment
-and contributing to the Cloud SQL for MySQL Gemini CLI Extension project.
+and contributing to the Cloud SQL for MySQL Agent skills project.
 
 ## Prerequisites
 
@@ -10,44 +10,30 @@ Before you begin, ensure you have the following:
 1.  **Gemini CLI:** Install the Gemini CLI version v0.6.0 or above. Installation
     instructions can be found on the official Gemini CLI documentation. You can
     verify your version by running `gemini --version`.
-2.  **Cloud SQL for MySQL Instance:** For testing data plane tools, you will need access to an active Cloud SQL for MySQL instance.
+2.  **Cloud SQL for MySQL Instance:** For testing data plane skills, you will need access to an active Cloud SQL for MySQL
+    instance.
 
 ## Developing the Extension
 
 ### Running from Local Source
 
-The core logic for this extension is handled by a pre-built `toolbox` binary. The development process involves installing the extension locally into the Gemini CLI to test changes.
-
 1.  **Clone the Repository:**
 
     ```bash
     git clone https://github.com/gemini-cli-extensions/cloud-sql-mysql.git
     cd cloud-sql-mysql
     ```
 
-2.  **Download the Toolbox Binary:** The required version of the `toolbox` binary
-    is specified in `toolbox_version.txt`. Download it for your platform.
-
-    ```bash
-    # Read the required version
-    VERSION=$(cat toolbox_version.txt)
-
-    # Example for macOS/amd64
-    curl -L -o toolbox https://storage.googleapis.com/mcp-toolbox-for-databases/geminicli/v$VERSION/darwin/amd64/toolbox
-    chmod +x toolbox
-    ```
-    Adjust the URL for your operating system (`linux/amd64`, `darwin/arm64`, `windows/amd64`).
-
-3.  **Link the Extension Locally:** Use the Gemini CLI to install the
+2.  **Install the Extension Locally:** Use the Gemini CLI to install the
     extension from your local directory.
 
     ```bash
-    gemini extensions link .
+    gemini extensions install .
     ```
-    The CLI will prompt you to confirm the linking. Accept it to proceed.
+    The CLI will prompt you to confirm the installation. Accept it to proceed.
 
-4.  **Testing Changes:** After linking, start the Gemini CLI (`gemini`).
-    You can now interact with the `cloud-sql-mysql` tools to manually test your changes
+3.  **Testing Changes:** After installation, start the Gemini CLI (`gemini`).
+    You can now interact with the `cloud-sql-mysql` skills to manually test your changes
     against your connected database.
 
 ## Testing
@@ -58,9 +44,9 @@ A GitHub Actions workflow (`.github/workflows/presubmit-tests.yml`) is triggered
 for every pull request. This workflow primarily verifies that the extension can
 be successfully installed by the Gemini CLI.
 
-Currently, there are no automated unit or integration test suites
-within this repository. All functional testing must be performed manually. All tools
-are currently tested in the [MCP Toolbox GitHub](https://github.com/googleapis/genai-toolbox).
+All tools are currently tested in the [MCP Toolbox GitHub](https://github.com/googleapis/mcp-toolbox).
+
+The skills themselves are validated using the `skills-validate.yml` workflow.
 
 ### Other GitHub Checks
 
@@ -73,17 +59,6 @@ are currently tested in the [MCP Toolbox GitHub](https://github.com/googleapis/g
 *   **Dependency Updates:** [Renovate](https://github.com/apps/forking-renovate)
     is configured to automatically create pull requests for dependency updates.
 
-## Building the Extension
-
-The "build" process for this extension involves packaging the extension's
-metadata files (`gemini-extension.json`, `cloud-sql-mysql.md`, `LICENSE`) along with the
-pre-built `toolbox` binary into platform-specific archives (`.tar.gz` or `.zip`).
-
-This process is handled automatically by the
-[`package-and-upload-assets.yml`](.github/workflows/package-and-upload-assets.yml)
-GitHub Actions workflow when a new release is created. Manual building is not
-required.
-
 ## Maintainer Information
 
 ### Team
@@ -101,7 +76,7 @@ The release process is automated using `release-please`. It consists of an autom
 #### Automated Changelog Enrichment
 
 Before a Release PR is even created, a special workflow automatically mirrors
-relevant changelogs from the core `googleapis/genai-toolbox` dependency. This
+relevant changelogs from the core `googleapis/mcp-toolbox` dependency. This
 ensures that the release notes for this extension accurately reflect important
 upstream changes.
 
@@ -138,7 +113,3 @@ The process is handled by the [`mirror-changelog.yml`](.github/workflows/mirror-
 2.  **Merge Release PR:** A maintainer approves and merges the Release PR. This
     action triggers `release-please` to create a new GitHub tag and a
     corresponding GitHub Release.
-3.  **Package and Upload:** The new release triggers the
-    `package-and-upload-assets.yml` workflow. This workflow builds the
-    platform-specific extension archives and uploads them as assets to the
-    GitHub Release.