[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DZ8GF40TKABJ9EPDRN7CK":3,"skill-same:01M79DZ8GF40TKABJ9EPDRN7CK":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M79DZ8GF40TKABJ9EPDRN7CK","datalineage-bigquery-asset-impact-analysis",null,"Analyzes the downstream impact (blast radius) when a BigQuery table or view is broken, stale, or modified. Identifies all downstream tables, dashboards, and processes that will be affected. Use when: - Performing a blast radius or impact analysis for a BigQuery table or view. - Assessing the consequences of modifying, deleting, or pausing updates to a BigQuery asset. - Identifying downstream dependencies (tables, dashboards, processes) of a BigQuery asset. Don't use for: - General BigQuery querying or data analysis (use BigQuery-related tools instead). - Non-BigQuery assets (e.g., Cloud Storage files) unless they are part of the BigQuery lineage. - Creating or modifying lineage links directly.","hamzabellouch\u002Fagent-skills","hamzabellouch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237856042?v=4","01M79BRYW7XAMK3YDWQEMTWGWS","Hamza Bellouch","01M79BRYWXQV3JK2TGVTX8GN2A",8,"MIT","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fdatalineage-bigquery-asset-impact-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: datalineage-bigquery-asset-impact-analysis\nmetadata:\n  category: BigDataAndAnalytics\ndescription: >-\n  Analyzes the downstream impact (blast radius) when a BigQuery table or view is broken, stale, or modified.\n  Identifies all downstream tables, dashboards, and processes that will be affected.\n  Use when:\n  - Performing a blast radius or impact analysis for a BigQuery table or view.\n  - Assessing the consequences of modifying, deleting, or pausing updates to a BigQuery asset.\n  - Identifying downstream dependencies (tables, dashboards, processes) of a BigQuery asset.\n  Don't use for:\n  - General BigQuery querying or data analysis (use BigQuery-related tools instead).\n  - Non-BigQuery assets (e.g., Cloud Storage files) unless they are part of the BigQuery lineage.\n  - Creating or modifying lineage links directly.\n---\n\n# BigQuery Asset Impact Analysis\n\nThis skill guides the agent in performing a downstream impact analysis (blast\nradius assessment) when a BigQuery table or view is reported as broken, stale,\nmissing, or when a user is planning maintenance and wants to know the\nconsequences of modifying or pausing updates to an asset.\n\nIt relies primarily on the **Google Cloud Data Lineage (Knowledge Catalog) MCP Server**\nto discover relationships between assets.\n\n## Prerequisites\n\nThis skill requires access to the Google Cloud Data Lineage API and an active\nclient connection to the Data Lineage MCP Server. For detailed connection\nconfigurations and tool schemas, refer to [MCP Usage](references\u002Fmcp-usage.md).\n\n## Analysis Workflow\n\n### 1. Resolve the Asset's Fully Qualified Name (FQN)\n\n*   Ensure you have the correct FQN format for the BigQuery asset:\n    *   *Format:* `bigquery:{project_id}.{dataset_id}.{table_or_view_id}`\n    *   *Example:* `bigquery:my-prod-project.analytics.orders`\n\n\n### 2. Determine Locations and Parent Path\n\nIdentify the locations to search and construct the Data Lineage API request:\n\n*   **Discover Asset Location**: Run the command `bq show --format=json\n    {project_id}:{dataset_id}` and extract the `location` field (e.g.,\n    `us-central1` or `us`). If location discovery fails due to permissions or\n    missing tools, prompt the user for the dataset's location.\n*   **Set Parent Path**: Set the `parent` path using the project ID and the\n    MCP server's location. Consult the `DataLineageServer` tool definition\n    to find the configured region or location (e.g., `us`). The format is:\n    `projects\u002F{project_id}\u002Flocations\u002F{mcp_server_location}`.\n*   **Configure Search Scope**: Include the discovered asset location in the\n    `locations` array of the payload (e.g., `[\"us-central1\"]` or `[\"us\",\n    \"us-central1\"]`).\n\n### 3. Retrieve the Downstream Lineage Graph\n\nCall the `DataLineageServer:search_lineage` tool to fetch downstream\nrelationships.\n\n*   **Direction**: Set to `DOWNSTREAM`.\n*   **Search Parameters**: Use `max_depth = 10` and `max_process_per_link = 5`\n    as robust defaults.\n\n### 4. Identify the Blast Radius\n\nTraverse the returned lineage links to build the impact graph:\n\n*   **Affected Assets**: The `target` of each link represents a downstream asset\n    that depends on your source asset.\n*   **Transform Processes**: Inspect the `processes` field on each link. This\n    identifies the ETL pipelines, BigQuery Views, or Scheduled Queries that\n    propagate the data.\n*   **Direct vs. Indirect Impact**:\n    *   **Direct Impact (Depth 1)**: Assets directly consuming the source asset.\n        If a link has `dependency_type: EXACT_COPY`, mark the target as\n        \"Directly Stale \u002F Identical Copy\".\n    *   **Indirect Impact (Depth > 1)**: Assets further down the stream that\n        will experience cascading stale data or failures.\n\n### 5. Summarize and Format the Output\n\nPresent your findings clearly to the user using the following structure:\n\n1.  **Executive Summary**: State the total number of downstream assets affected\n    and the maximum depth of the impact.\n2.  **Critical Path**: Highlight high-priority downstream assets (e.g., assets\n    containing \"prod\", \"dashboard\", \"reporting\", or \"master\" in their names).\n3.  **Blast Radius Table**: A clean Markdown table listing the dependencies. You\n    MUST include all columns:\n\n    | Downstream Asset                 | Transform Process                     | Depth | Impact Type |\n    | :------------------------------- | :------------------------------------ | :---- | :---------- |\n    | `bigquery:project.dataset.table` | `projects\u002Fp\u002Flocations\u002Fl\u002Fprocesses\u002Fproc` | 1     | Direct      |\n    | `bigquery:project.dataset.view`  | `projects\u002Fp\u002Flocations\u002Fl\u002Fprocesses\u002Fview` | 2     | Indirect    |\n4.  **Analysis Metadata**: Provide transparency on the parameters and boundaries\n    of your search so the user can choose to expand them:\n    *   **Locations Searched**: `{list_of_locations_queried}`\n    *   **Parent Location**: `{parent_path}`\n    *   **Depth Limit**: `{max_depth}`\n    *   **Process per Link Limit**: `{max_process_per_link}`\n    *   *Tip for User*: Let the user know they can request to rerun the analysis\n        with expanded locations or larger depth limits.\n\n## Crucial Constraints & Guardrails\n\n1.  **Interpret Empty Responses Correctly**:\n    *   If the lineage response is empty, immediately assume that no\n        dependencies exist in the queried locations and report this to the\n        user.\n2.  **Strictly Banned Bypasses**:\n    *   Exclusively retrieve downstream relationships using the\n        `DataLineageServer:search_lineage` tool.\n3.  **Verify Asset Existence First**:\n    *   If `bq show` indicates the source table does not exist, stop and report\n        this directly to the user. Do not attempt to guess alternative table\n        names unless the user explicitly instructs you to do so.\n4.  **No Output Shortcutting or Hallucinated Artifacts**:\n    *   Present the complete downstream blast radius table directly in your\n        final response. Avoid telling the user you have created a separate\n        Markdown file or artifact containing the details unless you have\n        explicitly executed file-writing tools to create it.\n\n## Reference Directory\n\n-   [MCP Usage](references\u002Fmcp-usage.md): Using the Google Cloud Data Lineage\n    remote MCP server and tool preferences.\n\n## External Documentation\n\n-   [Google Cloud Knowledge Catalog Data Lineage Documentation](https:\u002F\u002Fcloud.google.com\u002Fdataplex\u002Fdocs\u002Fabout-data-lineage)\n-   [Use the Data Lineage MCP server](https:\u002F\u002Fdocs.cloud.google.com\u002Fdataplex\u002Fdocs\u002Fuse-lineage-mcp)\n-   [Knowledge Catalog Data Lineage API Reference](https:\u002F\u002Fcloud.google.com\u002Fdataplex\u002Fdocs\u002Freference\u002Fdata-lineage\u002Frest)\n","# BigQuery Asset Impact Analysis\n\nThis skill guides the agent in performing a downstream impact analysis (blast\nradius assessment) when a BigQuery table or view is reported as broken, stale,\nmissing, or when a user is planning maintenance and wants to know the\nconsequences of modifying or pausing updates to an asset.\n\nIt relies primarily on the **Google Cloud Data Lineage (Knowledge Catalog) MCP Server**\nto discover relationships between assets.\n\n## Prerequisites\n\nThis skill requires access to the Google Cloud Data Lineage API and an active\nclient connection to the Data Lineage MCP Server. For detailed connection\nconfigurations and tool schemas, refer to [MCP Usage](references\u002Fmcp-usage.md).\n\n## Analysis Workflow\n\n### 1. Resolve the Asset's Fully Qualified Name (FQN)\n\n*   Ensure you have the correct FQN format for the BigQuery asset:\n    *   *Format:* `bigquery:{project_id}.{dataset_id}.{table_or_view_id}`\n    *   *Example:* `bigquery:my-prod-project.analytics.orders`\n\n\n### 2. Determine Locations and Parent Path\n\nIdentify the locations to search and construct the Data Lineage API request:\n\n*   **Discover Asset Location**: Run the command `bq show --format=json\n    {project_id}:{dataset_id}` and extract the `location` field (e.g.,\n    `us-central1` or `us`). If location discovery fails due to permissions or\n    missing tools, prompt the user for the dataset's location.\n*   **Set Parent Path**: Set the `parent` path using the project ID and the\n    MCP server's location. Consult the `DataLineageServer` tool definition\n    to find the configured region or location (e.g., `us`). The format is:\n    `projects\u002F{project_id}\u002Flocations\u002F{mcp_server_location}`.\n*   **Configure Search Scope**: Include the discovered asset location in the\n    `locations` array of the payload (e.g., `[\"us-central1\"]` or `[\"us\",\n    \"us-central1\"]`).\n\n### 3. Retrieve the Downstream Lineage Graph\n\nCall the `DataLineageServer:search_lineage` tool to fetch downstream\nrelationships.\n\n*   **Direction**: Set to `DOWNSTREAM`.\n*   **Search Parameters**: Use `max_depth = 10` and `max_process_per_link = 5`\n    as robust defaults.\n\n### 4. Identify the Blast Radius\n\nTraverse the returned lineage links to build the impact graph:\n\n*   **Affected Assets**: The `target` of each link represents a downstream asset\n    that depends on your source asset.\n*   **Transform Processes**: Inspect the `processes` field on each link. This\n    identifies the ETL pipelines, BigQuery Views, or Scheduled Queries that\n    propagate the data.\n*   **Direct vs. Indirect Impact**:\n    *   **Direct Impact (Depth 1)**: Assets directly consuming the source asset.\n        If a link has `dependency_type: EXACT_COPY`, mark the target as\n        \"Directly Stale \u002F Identical Copy\".\n    *   **Indirect Impact (Depth > 1)**: Assets further down the stream that\n        will experience cascading stale data or failures.\n\n### 5. Summarize and Format the Output\n\nPresent your findings clearly to the user using the following structure:\n\n1.  **Executive Summary**: State the total number of downstream assets affected\n    and the maximum depth of the impact.\n2.  **Critical Path**: Highlight high-priority downstream assets (e.g., assets\n    containing \"prod\", \"dashboard\", \"reporting\", or \"master\" in their names).\n3.  **Blast Radius Table**: A clean Markdown table listing the dependencies. You\n    MUST include all columns:\n\n    | Downstream Asset                 | Transform Process                     | Depth | Impact Type |\n    | :------------------------------- | :------------------------------------ | :---- | :---------- |\n    | `bigquery:project.dataset.table` | `projects\u002Fp\u002Flocations\u002Fl\u002Fprocesses\u002Fproc` | 1     | Direct      |\n    | `bigquery:project.dataset.view`  | `projects\u002Fp\u002Flocations\u002Fl\u002Fprocesses\u002Fview` | 2     | Indirect    |\n4.  **Analysis Metadata**: Provide transparency on the parameters and boundaries\n    of your search so the user can choose to expand them:\n    *   **Locations Searched**: `{list_of_locations_queried}`\n    *   **Parent Location**: `{parent_path}`\n    *   **Depth Limit**: `{max_depth}`\n    *   **Process per Link Limit**: `{max_process_per_link}`\n    *   *Tip for User*: Let the user know they can request to rerun the analysis\n        with expanded locations or larger depth limits.\n\n## Crucial Constraints & Guardrails\n\n1.  **Interpret Empty Responses Correctly**:\n    *   If the lineage response is empty, immediately assume that no\n        dependencies exist in the queried locations and report this to the\n        user.\n2.  **Strictly Banned Bypasses**:\n    *   Exclusively retrieve downstream relationships using the\n        `DataLineageServer:search_lineage` tool.\n3.  **Verify Asset Existence First**:\n    *   If `bq show` indicates the source table does not exist, stop and report\n        this directly to the user. Do not attempt to guess alternative table\n        names unless the user explicitly instructs you to do so.\n4.  **No Output Shortcutting or Hallucinated Artifacts**:\n    *   Present the complete downstream blast radius table directly in your\n        final response. Avoid telling the user you have created a separate\n        Markdown file or artifact containing the details unless you have\n        explicitly executed file-writing tools to create it.\n\n## Reference Directory\n\n-   [MCP Usage](references\u002Fmcp-usage.md): Using the Google Cloud Data Lineage\n    remote MCP server and tool preferences.\n\n## External Documentation\n\n-   [Google Cloud Knowledge Catalog Data Lineage Documentation](https:\u002F\u002Fcloud.google.com\u002Fdataplex\u002Fdocs\u002Fabout-data-lineage)\n-   [Use the Data Lineage MCP server](https:\u002F\u002Fdocs.cloud.google.com\u002Fdataplex\u002Fdocs\u002Fuse-lineage-mcp)\n-   [Knowledge Catalog Data Lineage API Reference](https:\u002F\u002Fcloud.google.com\u002Fdataplex\u002Fdocs\u002Freference\u002Fdata-lineage\u002Frest)\n",{"name":5,"metadata":24,"description":7},{"category":25},"BigDataAndAnalytics","main","e905af21e5f1e1c3ca605e9656c3a7930360a84e","Programming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fdatalineage-bigquery-asset-impact-analysis",1,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills","https:\u002F\u002Fhamzabellouch.github.io\u002F","https:\u002F\u002Fgithub.com\u002Fhamzabellouch","hamzabellouch.github.io","CEO & Founder of @tknoglobal | Researcher in Technology & Applied Sciences.","2026-10-17 03:20:19",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add hamzabellouch\u002Fagent-skills --skill datalineage-bigquery-asset-impact-analysis",{"tool":42,"command":43},"bunx","bunx skills add hamzabellouch\u002Fagent-skills --skill datalineage-bigquery-asset-impact-analysis",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hamzabellouch\u002Fagent-skills --skill datalineage-bigquery-asset-impact-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fdatalineage-bigquery-asset-impact-analysis\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fmcp-usage.md","REFERENCE","参考文档",1243,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fdatalineage-bigquery-asset-impact-analysis\u002Freferences\u002Fmcp-usage.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79FHH2H815A9TAP6WNKH4Q8","security-audit","Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FSecurity_Audit_and_Code_Review\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79FHBGXVBY6VQ1X7ETAZMF1","malware-analysis-reversing","Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static\u002Fdynamic binary analysis, memory forensics, and YARA detection rule authoring.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fmalware-analysis-reversing\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79FH6EACDR801TZCE4R8SAC","application-security-pentesting","Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST\u002FDAST pipeline integration, secure code review, threat modeling, and defensive security posture.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fapplication-security-pentesting\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79FH0VKVT44FK923K520ZQA","oauth2-oidc-security-flows","Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Foauth2-oidc-security-flows\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79FGVVB3R4T88XXD8FRSV5B","jwt-session-management-hardening","Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256\u002FEdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Fjwt-session-management-hardening\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79FGNCPZ85CVEY0B3NE4H3B","soc2-compliance-automation","Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI\u002FCD security gates.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FGovernance_Compliance_and_Legal_Tech\u002Fsoc2-compliance-automation\u002FSKILL.md",[],[]]