[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B0D40FFHYXRE3RF5D66TH4":3,"skill-same:01M7B0D40FFHYXRE3RF5D66TH4":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":13,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7B0D40FFHYXRE3RF5D66TH4","building-data-apps",null,"Build modern data apps, dashboards, and interactive reports using either\nReact + Vite or Streamlit. Includes optional Gemini Data Analytics chat\nintegration for an AI powered \"chat with your data\" experience.\n\nRelevant when any of the following conditions are true:\n  1. User explicitly requests to build a data dashboard, data application, or visualization UI, and the UI pulls data from a GCP database (defaulting to BigQuery unless otherwise specified).\n  2. You need to generate a frontend web application to interact with, query, and visualize data from GCP data sources.\n  3. User wants to build a \"chat with your data\" experience or integrate the Gemini Data Analytics chat API into a web interface.\n\nDo NOT use when any of the following conditions are true:\n  1. The request is for building backend-only services.\n  2. The request is for simple CLI scripts or command-line applications.\n  3. The web application is not data-centric or does not involve visualizing\u002Fquerying data from GCP sources.","Krishp091205\u002Fgemini-config","Krishp091205","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F307182548?v=4","01M7AXCYY4NQ9WQ7DCT3R5Q5S4","01M7AXCYYR7QFCQQ6BFRKD93YH",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: building-data-apps\ndescription: |\n  Build modern data apps, dashboards, and interactive reports using either\n  React + Vite or Streamlit. Includes optional Gemini Data Analytics chat\n  integration for an AI powered \"chat with your data\" experience.\n\n  Relevant when any of the following conditions are true:\n    1. User explicitly requests to build a data dashboard, data application, or visualization UI, and the UI pulls data from a GCP database (defaulting to BigQuery unless otherwise specified).\n    2. You need to generate a frontend web application to interact with, query, and visualize data from GCP data sources.\n    3. User wants to build a \"chat with your data\" experience or integrate the Gemini Data Analytics chat API into a web interface.\n\n  Do NOT use when any of the following conditions are true:\n    1. The request is for building backend-only services.\n    2. The request is for simple CLI scripts or command-line applications.\n    3. The web application is not data-centric or does not involve visualizing\u002Fquerying data from GCP sources.\nlicense: Apache-2.0\nmetadata:\n  version: v1\n  publisher: google\n---\n\n# Building Data Applications\n\nArchitect high-quality data dashboards and interactive reports. You MUST select\nthe appropriate framework before implementation.\n\n## Step 0: Framework Selection\n\nYou MUST select the framework based on the user's maintenance requirements and\ndata ecosystem.\n\n### Choice: Streamlit\n\n-   **User Profile**: Data Scientists \u002F Python users.\n-   **Logic Complexity**: High Python dependency (Pandas, NumPy, local data\n    processing).\n-   **Deployment**: Single-file Python script.\n-   **Customization**: Standard layout (fast boilerplate).\n\n### Choice: React + Vite\n\n-   **User Profile**: Web Developers \u002F Full-stack teams.\n-   **Logic Complexity**: High UI and Interactivity requirements (e.g.,\n    drag-and-drop, interactive maps).\n-   **Deployment**: Standalone Frontend + Backend API.\n-   **Customization**: Infinite (Custom CSS, specialized JS libraries).\n\n### Guidance:\n\n-   **Check for existing stack first**: ALWAYS prefer the framework the user is\n    already using in their project (e.g., if you see a `package.json` with React\n    dependencies, use React; if you see existing Streamlit files, use\n    Streamlit).\n-   **Default to React + Vite** for production-grade applications that require\n    complex client-side state, custom branding, or integration into a larger web\n    ecosystem.\n-   **Default to Streamlit** if the user specifically mentions \"Python\n    dashboard\", needs to iterate on complex local Python data processing, or\n    requires a single-script deployment.\n\n## Step 1: Implementation Plan\n\nYou MUST propose a plan to the user that specifies the chosen framework and\njustifies the choice based on the criteria above.\n\n--------------------------------------------------------------------------------\n\n## Shared Design Standards\n\nRegardless of framework, you MUST follow the principles in\n`references\u002Fshared_design_system.md`.\n\n-   **Visual Style**: Minimal chrome, zinc color palette, and card-based\n    layouts.\n-   **Typography**: `DM Sans` for content, `JetBrains Mono` for data.\n\n--------------------------------------------------------------------------------\n\n## Framework Implementation\n\n### If using Streamlit:\n\n1.  Read `references\u002Fstreamlit_framework.md` for detailed CSS and component\n    patterns.\n2.  Follow the \"Checklist for New Dashboards\" in that file.\n\n### If using React + Vite:\n\n1.  Read `references\u002Freact_framework.md` for Tailwind and ECharts setup.\n2.  Follow the detailed component guidelines for KPI cards, Tables, and Panels.\n\n--------------------------------------------------------------------------------\n\n## AI Chat Interface (Optional Feature)\n\n```\n> [!IMPORTANT]\n>\n> If the user does not explicitly request a chat interface, you SHOULD\n> proactively ask them: \"Would you like to include a Gemini-powered chat\n> interface to enable natural language queries against your data?\" OR if\n> there is an implementation plan: \"Would you like to include a\n> Gemini-powered chat interface to enable natural language queries against\n> your data? Let me know and I'll update the plan!\".\n```\n\nIf the user requests or agrees to the chat interface:\n\n```\n> [!CAUTION]\n>\n> Adding the chat interface is a significant change. Implicit approval of\n> the implementation plan for including the chat interface MUST never be\n> assumed.\n```\n\n1.  **Gather Technical Details**: You MUST read `references\u002Fchat_integration.md`\n    for the technical requirements.\n2.  **Update the implementation plan**: If and only if there is an\n    implementation plan, you MUST update the implementation plan. This is a\n    significant change so the user must explicitly approve the updated plan.\n3.  **Verify Prerequisites**: Ensure the user has the Gemini Data Analytics API\n    enabled and data exists in BigQuery.\n4.  **Reference Examples**: Adapt the patterns in\n    `examples\u002Freact_chat_panel.jsx` and either `examples\u002Ffastapi_chat.py` or\n    `examples\u002Fexpress_chat.ts`.\n\n## Acceptance Criteria\n\n> [!CAUTION]\n>\n> If available, you MUST use browser testing capabilities (such as\n> `browser_subagent`, Puppeteer, Playwright, or an equivalent available tool) to\n> visually verify the frontend application is working correctly *before*\n> notifying the user that the task is complete.\n\n> [!IMPORTANT]\n>\n> The following checklist represents the strict requirements for this task. You\n> must include these items in whatever format you use to track your work (e.g.,\n> your task list, implementation plan, or internal checklist).\n\n-   [ ] Are CSS hover transitions smooth?\n-   [ ] Are date fields formatted readably? (e.g., `MMM dd, yyyy`)\n-   [ ] Do z-indexes stack correctly so dropdowns appear above table headers?\n    (`relative z-30`)\n-   [ ] Do all interactive form\u002Fbutton inputs handle loading\u002Fdisabled states?\n-   [ ] Is the application responsive and does the layout adapt well to\n    different screen sizes?\n-   [ ] Are API calls for data fetching successful, and is there appropriate\n    error handling?\n-   [ ] Does the dark mode toggle function correctly and apply styles\n    consistently?\n-   [ ] Do all visualizations render correctly and are they interactive where\n    expected?\n-   [ ] Is the dashboard visually appealing?\n","# Building Data Applications\n\nArchitect high-quality data dashboards and interactive reports. You MUST select\nthe appropriate framework before implementation.\n\n## Step 0: Framework Selection\n\nYou MUST select the framework based on the user's maintenance requirements and\ndata ecosystem.\n\n### Choice: Streamlit\n\n-   **User Profile**: Data Scientists \u002F Python users.\n-   **Logic Complexity**: High Python dependency (Pandas, NumPy, local data\n    processing).\n-   **Deployment**: Single-file Python script.\n-   **Customization**: Standard layout (fast boilerplate).\n\n### Choice: React + Vite\n\n-   **User Profile**: Web Developers \u002F Full-stack teams.\n-   **Logic Complexity**: High UI and Interactivity requirements (e.g.,\n    drag-and-drop, interactive maps).\n-   **Deployment**: Standalone Frontend + Backend API.\n-   **Customization**: Infinite (Custom CSS, specialized JS libraries).\n\n### Guidance:\n\n-   **Check for existing stack first**: ALWAYS prefer the framework the user is\n    already using in their project (e.g., if you see a `package.json` with React\n    dependencies, use React; if you see existing Streamlit files, use\n    Streamlit).\n-   **Default to React + Vite** for production-grade applications that require\n    complex client-side state, custom branding, or integration into a larger web\n    ecosystem.\n-   **Default to Streamlit** if the user specifically mentions \"Python\n    dashboard\", needs to iterate on complex local Python data processing, or\n    requires a single-script deployment.\n\n## Step 1: Implementation Plan\n\nYou MUST propose a plan to the user that specifies the chosen framework and\njustifies the choice based on the criteria above.\n\n--------------------------------------------------------------------------------\n\n## Shared Design Standards\n\nRegardless of framework, you MUST follow the principles in\n`references\u002Fshared_design_system.md`.\n\n-   **Visual Style**: Minimal chrome, zinc color palette, and card-based\n    layouts.\n-   **Typography**: `DM Sans` for content, `JetBrains Mono` for data.\n\n--------------------------------------------------------------------------------\n\n## Framework Implementation\n\n### If using Streamlit:\n\n1.  Read `references\u002Fstreamlit_framework.md` for detailed CSS and component\n    patterns.\n2.  Follow the \"Checklist for New Dashboards\" in that file.\n\n### If using React + Vite:\n\n1.  Read `references\u002Freact_framework.md` for Tailwind and ECharts setup.\n2.  Follow the detailed component guidelines for KPI cards, Tables, and Panels.\n\n--------------------------------------------------------------------------------\n\n## AI Chat Interface (Optional Feature)\n\n```\n> [!IMPORTANT]\n>\n> If the user does not explicitly request a chat interface, you SHOULD\n> proactively ask them: \"Would you like to include a Gemini-powered chat\n> interface to enable natural language queries against your data?\" OR if\n> there is an implementation plan: \"Would you like to include a\n> Gemini-powered chat interface to enable natural language queries against\n> your data? Let me know and I'll update the plan!\".\n```\n\nIf the user requests or agrees to the chat interface:\n\n```\n> [!CAUTION]\n>\n> Adding the chat interface is a significant change. Implicit approval of\n> the implementation plan for including the chat interface MUST never be\n> assumed.\n```\n\n1.  **Gather Technical Details**: You MUST read `references\u002Fchat_integration.md`\n    for the technical requirements.\n2.  **Update the implementation plan**: If and only if there is an\n    implementation plan, you MUST update the implementation plan. This is a\n    significant change so the user must explicitly approve the updated plan.\n3.  **Verify Prerequisites**: Ensure the user has the Gemini Data Analytics API\n    enabled and data exists in BigQuery.\n4.  **Reference Examples**: Adapt the patterns in\n    `examples\u002Freact_chat_panel.jsx` and either `examples\u002Ffastapi_chat.py` or\n    `examples\u002Fexpress_chat.ts`.\n\n## Acceptance Criteria\n\n> [!CAUTION]\n>\n> If available, you MUST use browser testing capabilities (such as\n> `browser_subagent`, Puppeteer, Playwright, or an equivalent available tool) to\n> visually verify the frontend application is working correctly *before*\n> notifying the user that the task is complete.\n\n> [!IMPORTANT]\n>\n> The following checklist represents the strict requirements for this task. You\n> must include these items in whatever format you use to track your work (e.g.,\n> your task list, implementation plan, or internal checklist).\n\n-   [ ] Are CSS hover transitions smooth?\n-   [ ] Are date fields formatted readably? (e.g., `MMM dd, yyyy`)\n-   [ ] Do z-indexes stack correctly so dropdowns appear above table headers?\n    (`relative z-30`)\n-   [ ] Do all interactive form\u002Fbutton inputs handle loading\u002Fdisabled states?\n-   [ ] Is the application responsive and does the layout adapt well to\n    different screen sizes?\n-   [ ] Are API calls for data fetching successful, and is there appropriate\n    error handling?\n-   [ ] Does the dark mode toggle function correctly and apply styles\n    consistently?\n-   [ ] Do all visualizations render correctly and are they interactive where\n    expected?\n-   [ ] Is the dashboard visually appealing?\n",{"name":5,"license":14,"metadata":23,"description":26},{"version":24,"publisher":25},"v1","google","Build modern data apps, dashboards, and interactive reports using either\nReact + Vite or Streamlit. Includes optional Gemini Data Analytics chat\nintegration for an AI powered \"chat with your data\" experience.\n\nRelevant when any of the following conditions are true:\n  1. User explicitly requests to build a data dashboard, data application, or visualization UI, and the UI pulls data from a GCP database (defaulting to BigQuery unless otherwise specified).\n  2. You need to generate a frontend web application to interact with, query, and visualize data from GCP data sources.\n  3. User wants to build a \"chat with your data\" experience or integrate the Gemini Data Analytics chat API into a web interface.\n\nDo NOT use when any of the following conditions are true:\n  1. The request is for building backend-only services.\n  2. The request is for simple CLI scripts or command-line applications.\n  3. The web application is not data-centric or does not involve visualizing\u002Fquerying data from GCP sources.\n","main","1f317365436456f9c1039c414a2f6426caabc74c","skills\u002Fbuilding-data-apps","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config","https:\u002F\u002Fgithub.com\u002FKrishp091205","2026-08-23 02:02:24",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Krishp091205\u002Fgemini-config --skill building-data-apps",{"tool":39,"command":40},"bunx","bunx skills add Krishp091205\u002Fgemini-config --skill building-data-apps",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Krishp091205\u002Fgemini-config --skill building-data-apps","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002FSKILL.md",true,[47,53,57,63,69,73,77],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"examples\u002Fexpress_chat.ts","SCRIPT","脚本",5108,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002Fexamples\u002Fexpress_chat.ts",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"examples\u002Ffastapi_chat.py",4774,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002Fexamples\u002Ffastapi_chat.py",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"examples\u002Freact_chat_panel.jsx","OTHER","其他",11937,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002Fexamples\u002Freact_chat_panel.jsx",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fchat_integration.md","REFERENCE","参考文档",4389,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002Freferences\u002Fchat_integration.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Freact_framework.md",10348,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002Freferences\u002Freact_framework.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fshared_design_system.md",1159,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002Freferences\u002Fshared_design_system.md",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fstreamlit_framework.md",8491,"https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-data-apps\u002Freferences\u002Fstreamlit_framework.md",[82,89,96,103,110,117],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7B0GYVAXB2M99PR4Z3N1WW0","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7B0GQ2CKFX5P1DTV802XMAB","notebook-guidance","This skill guides the use of Jupyter notebooks for data analysis, exploration, and visualization, particularly with BigQuery. It outlines best practices for notebook execution and validation (supporting both cell-by-cell execution and full notebook generation depending on tool availability), library installation, and structuring notebooks for clarity. It also covers specific rules for data cleaning, plotting, and integrating with BigQuery SQL and machine learning workflows.\nRelevant when any of the following conditions are true:\n  1. The user request involves a data analysis, data exploration, data visualization, or data insights task that requires multiple steps, queries, or visualizations to answer.\n  2. The user explicitly requests a notebook (.ipynb).\n  3. You are creating, editing, or executing cells in a Jupyter notebook.\n  4. You need to query BigQuery from within a notebook. DO NOT use the Python BigQuery client library; instead, you MUST use the `%%bqsql` magics explained in this skill.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fnotebook-guidance\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7B0GJ1K1JE2K593JZT4CAY9","ml-best-practices","CRITICAL RULE: You MUST use this skill whenever the task involves any machine learning tasks or data analysis.\nUse this skill if the user's prompt or requirements mention any of the following:\n  * Clustering\n  * Classification\n  * Regression\n  * Time series forecasting\n  * Statistical testing\n  * Model comparison\n  * ML\n  * Data analysis\n\nSQL\u002FBigQuery ML HANDOFF: If the user requires a SQL solution, use this skill to dictate the ANALYSIS STEPS (e.g., markdown analysis cells, visualization logic), but defer to `bigquery` for all SQL syntax.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fml-best-practices\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M7B0GD7FSN72WCSZ16WEDH42","managing-python-dependencies","Ensures proper Python dependency management, avoiding global `pip install` and\nadhering to project-specific tooling.\n\nUse this skill if any of the following are true:\n  1. Attempting to run `pip install {package_name}`.\n  2. Python packages or dependencies need to be added or modified.\n  3. Initiating a new Python project.\n  4. Creating a new notebook, even if just using BigQuery cells.\n  5. Generating Python code that includes `import` statements for third-party libraries.\n  6. Before executing Python scripts via the terminal to ensure the correct virtual environment is active.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fmanaging-python-dependencies\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M7B0G6CC6JP6QTQGPSTBMJTX","google-cloud-storage-basics","Stores, retrieves, and manages data as objects in Cloud Storage (Google Cloud Storage, or GCS) buckets. Use when you need to interact with Cloud Storage — create or configure buckets, upload, download, stream, or transfer data, organize objects with folders, generate signed URLs, control access (IAM, ACLs, public access prevention), set storage classes and tiering (Standard, Nearline, Coldline, Archive), manage cost and lifecycle, protect data (versioning, encryption\u002FCMEK, retention and Bucket Lock, object holds, soft delete), host static websites, trigger Pub\u002FSub notifications on object changes, mount buckets as a file system (gcsfuse), or optimize storage performance at any scale. Covers the gcloud storage \u002F gsutil CLI, JSON and XML APIs, client libraries, Terraform, and Cloud Storage MCP servers. Don't use for block storage (Persistent Disk), data warehousing\u002Fanalytics (BigQuery), or databases (Cloud SQL, Spanner, Bigtable, Firestore).","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle-cloud-storage-basics\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":18},"01M7B0G2DF32KW9A77S99QBZ4Q","gcs-security-assessment","Assesses security posture, evaluates risks, and checks SAIF compliance for Google Cloud Storage buckets or projects. Use when the user requests security scans, vulnerability checks, or SAIF assessments. Don't use when: The user is asking about non-GCS resources (Compute Engine, GKE, etc.), investigating a live production outage, or asking general security questions not tied to a specific project or bucket.","https:\u002F\u002Fgithub.com\u002FKrishp091205\u002Fgemini-config\u002Fblob\u002Fmain\u002Fskills\u002Fgcs-security-assessment\u002FSKILL.md",[],[]]