[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7Z1285XP8KZP9JESSPEET":3,"skill-same:01M7D7Z1285XP8KZP9JESSPEET":65},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":5,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7D7Z1285XP8KZP9JESSPEET","managed-airflow-dag-authoring",null,"Provides guidance for authoring Apache Airflow DAGs in Managed Service for Apache Airflow (MSAA; formerly Cloud Composer). Covers environment context discovery, Airflow 2 vs 3 compatibility, authoring best practices, and local\u002Fremote validation processes. Use when creating or extending an Airflow DAG. Don't use when authoring Python code unrelated to Airflow DAGs.","tangyixiao\u002Ftangyixiao-skills","tangyixiao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F115929632?v=4","01M7D582YK6A4M63CAK4CSY4EW","Tang Yixiao","01M7D582Z64DMRSYR872SR34SA",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fmanaged-airflow-dag-authoring\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fmanaged-airflow-dag-authoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: managed-airflow-dag-authoring\ndescription: Provides guidance for authoring Apache Airflow DAGs in Managed Service\n  for Apache Airflow (MSAA; formerly Cloud Composer). Covers environment context discovery,\n  Airflow 2 vs 3 compatibility, authoring best practices, and local\u002Fremote validation\n  processes. Use when creating or extending an Airflow DAG. Don't use when authoring\n  Python code unrelated to Airflow DAGs.\nmetadata:\n  version: 1.0.1\n  category: BigDataAndAnalytics\n---\n\n# GCP Managed Airflow DAG Authoring Guide\n\nThis skill guides you through authoring and validating Apache Airflow DAGs for\nManaged Service for Apache Airflow (MSAA; formerly Cloud Composer) environments.\n\n--------------------------------------------------------------------------------\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:managed-airflow-dag-authoring)\"`\nand append `agent-skills\u002F1.0 (skill:managed-airflow-dag-authoring)` to `User-Agent` headers.\n\n## Phase 1: Context Discovery\n\nBefore writing any DAG code, you MUST understand the constraints (e.g. version\nof Airflow) and capabilities of your target environment if user is willing to\nprovide them.\n\n### 1.1 Identify Target Environment & Access\n\nDetermine if you have direct access to the target Managed Airflow environment,\nlocal development environment or if you are working offline (only changing local\nfiles without validation).\n\n*   **If environment access is available:** Use `gcloud` to inspect the\n    environment (see Section 1.3).\n*   **If offline:** Rely on user provided details.\n\n### 1.2 Identify Development Environment\n\nDetermine if a local development environment is available.\n\n*   Check if `composer-dev` CLI is installed.\n*   Check if a local Python environment with `airflow` is available.\n\n### 1.3 Inspect Target Environment (if available and requested)\n\nRun the following commands to discover version constraints:\n\n1.  **Get Airflow\u002FImage Version:**\n\n    ```bash\n    gcloud composer environments describe {env_name} \\\n        --location {region} \\\n        --format=\"value(config.softwareConfig.imageVersion)\"\n    ```\n\n2.  **Get Installed Packages (Versions):**\n\n    ```bash\n    gcloud composer environments describe {env_name} \\\n        --location {region} \\\n        --format=\"value(config.softwareConfig.pypiPackages)\"\n    ```\n\n3.  **Get DAGs GCS Bucket:**\n\n    ```bash\n    gcloud composer environments describe {env_name} \\\n        --location {region} \\\n        --format=\"value(config.dagGcsPrefix)\"\n    ```\n\n--------------------------------------------------------------------------------\n\n## Phase 2: DAG Authoring Best Practices\n\n### 2.1 General Airflow Best Practices\n\n*   **Idempotency:** Every task SHOULD be idempotent. Running it multiple times\n    with the same inputs (e.g., execution date) SHOULD produce the same result\n    and not duplicate data.\n*   **No Top-Level Code Execution:** Do NOT execute database queries, external\n    API calls, or heavy computations at the top level of the DAG file (outside\n    of tasks\u002Foperators). This code runs every few seconds during DAG parsing and\n    will degrade performance.\n*   **Explicit Catchup:** Always set `catchup=False` in the DAG definition\n    unless historical backfilling is explicitly required.\n*   **Use Airflow Variables\u002FConnections:** Never hardcode credentials or\n    environment-specific configs. Use `Variable.get()` (with\n    `deserialize_json=True` if applicable) and `BaseHook.get_connection()`.\n    Access variables via Jinja templates (e.g., `{{ var.value.my_var }}`) to\n    avoid database calls during DAG parsing.\n\n### 2.2 Airflow 2 vs Airflow 3 Compatibility\n\nUse managed-airflow-migrations skill to navigate adjusting the code to\nspecific target Airflow version.\n\n--------------------------------------------------------------------------------\n\n## Phase 3: Validation Process\n\nYou MUST validate DAGs before concluding your task.\n\n### 3.1 Local Validation (Offline\u002FPre-deployment)\n\n#### 3.1.1 Static Analysis & Linting\n\nUse `ruff` or `pylint` if available.\n\n```bash\nruff check path\u002Fto\u002Fdag.py\n```\n\n*   If targeting Airflow 3, check with Airflow 3 rules if rulesets are\n    available.\n\n#### 3.1.2 Local Dev Environment (`composer-dev`)\n\nIf the user has `composer-dev` configured:\n\n1.  Copy the DAG to the local directory with DAGs:\n\n    ```bash\n    cp path\u002Fto\u002Fdag.py $(composer-dev describe {local_env} --format=\"value(dags_directory)\")\n    ```\n\n2.  Verify parsing:\n\n    ```bash\n    composer-dev run-airflow-cmd {local_env} dags list-import-errors\n    ```\n\n### 3.2: Target Environment Validation\n\nOnly perform these steps if you have GCP access and are authorized to deploy to\na target environment.\n\n### 3.2.1 Deploy to GCS\n\nUpload the DAG to the target environment's GCS bucket:\n\n```bash\ngcloud storage cp path\u002Fto\u002Fdag.py gs:\u002F\u002F{target_bucket}\u002Fdags\u002F\n```\n\n### 3.2.2 Verify via Airflow CLI\n\nWait 1-2 minutes for the scheduler to parse the file, then run:\n\n1.  **Check for Import Errors:**\n\n    ```bash\n    gcloud composer environments run {env_name} \\\n        --location {region} \\\n        dags list-import-errors\n    ```\n\n*Pass Criteria:* Output should be \"No data found\" or empty.\n\n2.  **Verify DAG is Listed:**\n\n    ```bash\n    gcloud composer environments run {env_name} \\\n        --location {region} \\\n        dags list | grep {dag_id}\n    ```\n\n### 3.2.3 Monitor Cloud Logging\n\nCheck for runtime parsing errors in Cloud Logging:\n\n```query\nresource.type=\"cloud_composer_environment\"\nresource.labels.environment_name=\"{env_name}\"\nlog_id(\"airflow-scheduler\")\nseverity>=ERROR\ntextPayload:\"{dag_file_name}\"\n```\n\n--------------------------------------------------------------------------------\n\n## Definition of Done\n\n*   DAG code adheres to Airflow version constraints of the target environment.\n*   DAG code follows best practices (no top-level execution, idempotent if\n    possible).\n*   DAG parses locally without import errors.\n*   (If environment is available) DAG is deployed to the target environment and\n    verified to have no import errors.\n","# GCP Managed Airflow DAG Authoring Guide\n\nThis skill guides you through authoring and validating Apache Airflow DAGs for\nManaged Service for Apache Airflow (MSAA; formerly Cloud Composer) environments.\n\n--------------------------------------------------------------------------------\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:managed-airflow-dag-authoring)\"`\nand append `agent-skills\u002F1.0 (skill:managed-airflow-dag-authoring)` to `User-Agent` headers.\n\n## Phase 1: Context Discovery\n\nBefore writing any DAG code, you MUST understand the constraints (e.g. version\nof Airflow) and capabilities of your target environment if user is willing to\nprovide them.\n\n### 1.1 Identify Target Environment & Access\n\nDetermine if you have direct access to the target Managed Airflow environment,\nlocal development environment or if you are working offline (only changing local\nfiles without validation).\n\n*   **If environment access is available:** Use `gcloud` to inspect the\n    environment (see Section 1.3).\n*   **If offline:** Rely on user provided details.\n\n### 1.2 Identify Development Environment\n\nDetermine if a local development environment is available.\n\n*   Check if `composer-dev` CLI is installed.\n*   Check if a local Python environment with `airflow` is available.\n\n### 1.3 Inspect Target Environment (if available and requested)\n\nRun the following commands to discover version constraints:\n\n1.  **Get Airflow\u002FImage Version:**\n\n    ```bash\n    gcloud composer environments describe {env_name} \\\n        --location {region} \\\n        --format=\"value(config.softwareConfig.imageVersion)\"\n    ```\n\n2.  **Get Installed Packages (Versions):**\n\n    ```bash\n    gcloud composer environments describe {env_name} \\\n        --location {region} \\\n        --format=\"value(config.softwareConfig.pypiPackages)\"\n    ```\n\n3.  **Get DAGs GCS Bucket:**\n\n    ```bash\n    gcloud composer environments describe {env_name} \\\n        --location {region} \\\n        --format=\"value(config.dagGcsPrefix)\"\n    ```\n\n--------------------------------------------------------------------------------\n\n## Phase 2: DAG Authoring Best Practices\n\n### 2.1 General Airflow Best Practices\n\n*   **Idempotency:** Every task SHOULD be idempotent. Running it multiple times\n    with the same inputs (e.g., execution date) SHOULD produce the same result\n    and not duplicate data.\n*   **No Top-Level Code Execution:** Do NOT execute database queries, external\n    API calls, or heavy computations at the top level of the DAG file (outside\n    of tasks\u002Foperators). This code runs every few seconds during DAG parsing and\n    will degrade performance.\n*   **Explicit Catchup:** Always set `catchup=False` in the DAG definition\n    unless historical backfilling is explicitly required.\n*   **Use Airflow Variables\u002FConnections:** Never hardcode credentials or\n    environment-specific configs. Use `Variable.get()` (with\n    `deserialize_json=True` if applicable) and `BaseHook.get_connection()`.\n    Access variables via Jinja templates (e.g., `{{ var.value.my_var }}`) to\n    avoid database calls during DAG parsing.\n\n### 2.2 Airflow 2 vs Airflow 3 Compatibility\n\nUse managed-airflow-migrations skill to navigate adjusting the code to\nspecific target Airflow version.\n\n--------------------------------------------------------------------------------\n\n## Phase 3: Validation Process\n\nYou MUST validate DAGs before concluding your task.\n\n### 3.1 Local Validation (Offline\u002FPre-deployment)\n\n#### 3.1.1 Static Analysis & Linting\n\nUse `ruff` or `pylint` if available.\n\n```bash\nruff check path\u002Fto\u002Fdag.py\n```\n\n*   If targeting Airflow 3, check with Airflow 3 rules if rulesets are\n    available.\n\n#### 3.1.2 Local Dev Environment (`composer-dev`)\n\nIf the user has `composer-dev` configured:\n\n1.  Copy the DAG to the local directory with DAGs:\n\n    ```bash\n    cp path\u002Fto\u002Fdag.py $(composer-dev describe {local_env} --format=\"value(dags_directory)\")\n    ```\n\n2.  Verify parsing:\n\n    ```bash\n    composer-dev run-airflow-cmd {local_env} dags list-import-errors\n    ```\n\n### 3.2: Target Environment Validation\n\nOnly perform these steps if you have GCP access and are authorized to deploy to\na target environment.\n\n### 3.2.1 Deploy to GCS\n\nUpload the DAG to the target environment's GCS bucket:\n\n```bash\ngcloud storage cp path\u002Fto\u002Fdag.py gs:\u002F\u002F{target_bucket}\u002Fdags\u002F\n```\n\n### 3.2.2 Verify via Airflow CLI\n\nWait 1-2 minutes for the scheduler to parse the file, then run:\n\n1.  **Check for Import Errors:**\n\n    ```bash\n    gcloud composer environments run {env_name} \\\n        --location {region} \\\n        dags list-import-errors\n    ```\n\n*Pass Criteria:* Output should be \"No data found\" or empty.\n\n2.  **Verify DAG is Listed:**\n\n    ```bash\n    gcloud composer environments run {env_name} \\\n        --location {region} \\\n        dags list | grep {dag_id}\n    ```\n\n### 3.2.3 Monitor Cloud Logging\n\nCheck for runtime parsing errors in Cloud Logging:\n\n```query\nresource.type=\"cloud_composer_environment\"\nresource.labels.environment_name=\"{env_name}\"\nlog_id(\"airflow-scheduler\")\nseverity>=ERROR\ntextPayload:\"{dag_file_name}\"\n```\n\n--------------------------------------------------------------------------------\n\n## Definition of Done\n\n*   DAG code adheres to Airflow version constraints of the target environment.\n*   DAG code follows best practices (no top-level execution, idempotent if\n    possible).\n*   DAG parses locally without import errors.\n*   (If environment is available) DAG is deployed to the target environment and\n    verified to have no import errors.\n",{"name":5,"metadata":25,"description":7},{"version":26,"category":27},"1.0.1","BigDataAndAnalytics","main","2a870f189175a48c39f5f7e26a6d93b0be9cd13b",0,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills","https:\u002F\u002Ftangyixiao.github.io\u002Ftangyixiao-skills\u002F","https:\u002F\u002Fgithub.com\u002Ftangyixiao","http:\u002F\u002Fwww.sxyz.net\u002F","I am Tang Yixiao, a student in Shaoxing No.1 High School. I am eager to learn on GitHub and contribute my part to this community.","2026-11-11 15:45:59",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add tangyixiao\u002Ftangyixiao-skills --skill managed-airflow-dag-authoring",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill managed-airflow-dag-authoring",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill managed-airflow-dag-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fmanaged-airflow-dag-authoring\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"INSTALL-SOURCE.json","REFERENCE","参考文档",547,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fmanaged-airflow-dag-authoring\u002FINSTALL-SOURCE.json",{"path":58,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fattribution.md",1927,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fmanaged-airflow-dag-authoring\u002Freferences\u002Fattribution.md",[66,74,83,91,99,107],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M7D8JK8FYBFNNAJXWD89CFH7","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":20},"01M7D8JG8ERGGQQAMX0DWCG9GR","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","MIT","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M7D8JE672GW3EHSE8EF185M4","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M7D8JBK572YDFMND8Q6CEYJW","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7D8J5QPWEXX61EGBKYH73R8","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M7D8J36YWC8WZS5DK5AH03CD","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FSKILL.md",[],[]]