docs: update terminology from tools to skills

Author: twishabansal

BIGQUERY.md

@@ -1,27 +1,48 @@
+You are a highly skilled data engineer and data analyst. Your purpose is to help the developer interact with BigQuery datasets, execute queries, and generate data insights throughout the entire software delivery cycle.
+
+---
+
 # Setup
 
 ## Required Gemini CLI Version
 
 To install this extension, the Gemini CLI version must be v0.6.0 or above. The version can be found by running: `gemini --version`.
 
-## BigQuery MCP Server (Data Plane: Connecting and Querying)
+## BigQuery Skills (Data Plane: Connecting and Querying)
+
+This section covers connecting to BigQuery.
+
+1. **Extension Configuration**: This extension requires several settings (e.g., Project ID, Location). These values are gathered via prompts when you first install or link the extension:
+
+ * `BIGQUERY_PROJECT`: The GCP project ID.
+ * `BIGQUERY_LOCATION`: (Optional) Location of the BigQuery resources.
+
+ If you need to update any of these values later, use the `gemini extensions config bigquery-data-analytics` command.
+
+2. **Handle Missing Variables**: If a command fails with an error message containing a placeholder like `${BIGQUERY_PROJECT}`, it signifies a missing environment variable. Inform the user which variable is missing and instruct them to set it.
+
+3. **Handle Permission Errors**:
+ * For operations that execute queries and view metadata, the user needs the **BigQuery User** (`roles/bigquery.user`) and **BigQuery Metadata Viewer** (`roles/bigquery.metadataViewer`) role.
+ * For operations that create, or modify datasets and tables, the user needs the **BigQuery Data Editor** (`roles/bigquery.dataEditor`) role.
+ * If an operation fails due to permissions, identify the type of operation and recommend the appropriate role. You can provide these links for assistance:
+ * Granting Roles: https://cloud.google.com/iam/docs/grant-role-console
+ * BigQuery Permissions: https://cloud.google.com/iam/docs/roles-permissions/bigquery
+
+---
+
+# Usage Guidelines
+
+## Reusing Project Values
 
-This section covers connecting to a BigQuery instance.
+Users may have set project environment variables:
 
-1.  **Verify Environment Variables**: Before attempting to connect, confirm with the user that the following environment variables are set in the extension configuration or their shell environment.
+* `BIGQUERY_PROJECT`: The GCP project ID.
+* `BIGQUERY_LOCATION`: (Optional) Location of the BigQuery resources.
 
-    * `BIGQUERY_PROJECT`: The GCP project ID.
+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 `BIGQUERY_PROJECT`, `${BIGQUERY_PROJECT}`, or `$BIGQUERY_PROJECT`. 
+The value can be verified by the user using the `gemini extensions config bigquery-data-analytics` command or by checking their local settings.
 
-2.  **Handle Missing Variables**: If a command fails with an error message containing a placeholder like `${BIGQUERY_PROJECT}`, it signifies a missing environment variable. Inform the user which variable is missing and instruct them to set it.
+## Use Full Table Name Format "PROJECT.DATASET.TABLE"
 
-3.  **Handle Permission Errors**:
-    * For operations that execute queries and view metadata, the user needs the
-      **BigQuery User** (`roles/bigquery.user`) and **BigQuery Metadata Viewer** (`roles/bigquery.metadataViewer`) role.
-    * For operations that create, or modify datasets and tables, the user neds
-      the **BigQuery Data Editor** (`roles/bigquery.dataEditor`) role.
-    * If an operation fails due to permissions, identify the type of operation
-      and recommend the appropriate role. you can provide these links for
-      assistance:
-        *   Granting Roles: https://cloud.google.com/iam/docs/grant-role-console
-        *   BigQuery Permissions:
-            https://cloud.google.com/iam/docs/roles-permissions/bigquery
+**ALWAYS** use the full table name format, `PROJECT.DATASET.TABLE` in the generated SQL when executing the `execute_sql` script.

DEVELOPER.md

@@ -16,7 +16,7 @@ Before you begin, ensure you have the following:
 
 ### 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.
+The development process involves installing the extension locally into the Gemini CLI to test changes.
 
 1.  **Clone the Repository:**
 
@@ -25,29 +25,16 @@ The core logic for this extension is handled by a pre-built `toolbox` binary. Th
     cd bigquery-data-analytics
     ```
 
-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 `bigquery-data-analytics` tools to manually test your changes
+3.  **Testing Changes:** After installing, start the Gemini CLI (`gemini`).
+    You can now interact with the `bigquery-data-analytics` skills to manually test your changes
     against your connected database.
 
 ## Testing
@@ -76,13 +63,8 @@ are currently tested in the [MCP Toolbox GitHub](https://github.com/googleapis/m
 ## Building the Extension
 
 The "build" process for this extension involves packaging the extension's
-metadata files (`gemini-extension.json`, `bigquery-data-analytics.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.
+metadata files (`gemini-extension.json`, `BIGQUERY.md`, `LICENSE`) along with the
+skills.
 
 ## Maintainer Information
 
@@ -135,7 +117,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.

README.md

@@ -17,7 +17,7 @@ Learn more about [Gemini CLI Extensions](https://github.com/google-gemini/gemini
 
 * **Natural Language to data analytics :** Find required BigQuery tables and ask analytical questions in natural language.
 * **Seamless Workflow:** Stay in your CLI. No need to constantly switch contexts to the GCP console for generating analytical insights.
-* **Run advanced analytics :** Generate forecasts, run a contributions analysis using built-in advanced tools.
+* **Run advanced analytics :** Generate forecasts, run a contributions analysis using built-in advanced skills.
 
 
 ## Prerequisites
@@ -93,18 +93,12 @@ Interact with BigQuery using natural language right from your IDE:
   * "Using bigquery-public-data.pypi.file\_downloads show me the top 10 downloaded pypi packages this month."
   * “Using bigquery-public-data.pypi.file\_downloads can you forecast downloads for the last four months of 2025 for package urllib3?”
 
-## Supported Tools
+## Supported Skills
 
-This extension provides a comprehensive set of tools:
+This extension provides a comprehensive set of skills:
 
-* `execute_sql`: Executes a SQL query.
-* `forecast`: Forecast time series data.
-* `get_dataset_info`: Get dataset metadata.
-* `get_table_info`: Get table metadata.
-* `list_dataset_ids`: Lists dataset ids in the database.
-* `list_table_ids`: Lists table ids in the database.
-* `analyze_contribution`: Perform contribution analysis, also called key driver analysis.
-* `search_catalog`: Search for tables based on the provided query.
+* `bigquery-data`: Use these skills when you need to handle large-scale data exploration and dataset management. Use when users need to find data assets or run SQL at scale. Provides metadata discovery and query execution across the data warehouse.
+* `bigquery-analytics`: Use these skills when you need to handle advanced data intelligence and predictive tasks. Use when a user asks "why" data changed or needs future projections. Provides automated insight generation and time-series forecasting.
 
 ## Additional Extensions