Token导航 LogoToken导航

Agent Skill · 运维和基础设施

adf-master(ADF 主控器)

adf-master 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

adf-master 是运维和基础设施类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证为 MIT,第三方扫描有提醒项,按安装量在运维和基础设施类的 2,449 个 Skill 里排第 677。

总安装 2,081周安装 85GitHub Stars 33下载 666核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:adf-master(ADF 主控器)
来源仓库:https://github.com/josiahsiegel/claude-plugin-marketplace
仓库路径:skills/adf-master
安装命令:
npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill adf-master
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill adf-master

这个 Skill 是做什么的

运维和基础设施类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

用于管理 GitHub 仓库状态、Issue 和 Pull Request,协助代码协作与变更跟踪。可获取仓库差异、合并请求详情及协作历史,支持开发流程自动化。适用于需要实时同步代码库状态或分析提交历史的场景。需确认是否具备足够的仓库访问权限,避免触发认证失败或 API 限制。

adf-master 属于运维和基础设施类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/adf-master

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

adf-master 怎么安装?

在终端执行 npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill adf-maste…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

adf-master 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

adf-master 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

adf-master 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

adf-master 用的人多吗?

公开数据是累计安装 2,081 次,近一周安装 85 次,下载 666 次,GitHub 33 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

adf-master 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理运维和基础设施类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

运维和基础设施类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
brainstorming

头脑风暴 · Codex、Claude

3,148,776173,131操作浏览器MIT通过
copywriting

文案写作 · Codex、Claude

1,996,72425,583需要联网MIT通过
openclaw-secure-linux-cloud

OpenClaw secure linux cloud 命令行 · Codex、Claude

1,853,08840接触敏感数据未明确未通过
xget

xget 命令行 · Codex、Claude

1,799,28040执行命令未明确未通过
requesting-code-review

代码审查请求 · Codex、Claude

1,590,144173,103权限未标注MIT通过
adf-master

ADF 主控器 · 本页

2,08133调用外部服务MIT有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Azure Data Factory Master Knowledge Base

Deprecated Features

Apache Airflow Workflow Orchestration Manager - DEPRECATED

Status: Deprecated since early 2025. Available only for existing customers. Retirement Date: Not yet announced, but no new deployments permitted. Impact: New customers cannot provision Apache Airflow in Azure Data Factory.

Deprecation Details:

  • Apache Airflow Workflow Orchestration Manager is deprecated with no retirement date set
  • Only existing deployments can continue using this feature
  • No new Airflow integrations can be created in ADF

Migration Path:

  • Recommended: Migrate to Fabric Data Factory with native Airflow support
  • Alternative: Use standalone Apache Airflow deployments (Azure Container Instances, AKS, or VM-based)
  • Alternative: Migrate orchestration logic to native ADF pipelines with control flow activities

Why Deprecated:

  • Microsoft focus shifted to Fabric Data Factory as the unified data integration platform
  • Fabric provides modern orchestration capabilities superseding Airflow integration
  • Limited adoption and maintenance burden for standalone Airflow feature in ADF

Action Required:

  • If using Airflow in ADF: Migrate to Fabric Data Factory, standalone Airflow, or native ADF patterns
  • For new projects: Do NOT use Airflow in ADF
  • Monitor Microsoft announcements for official retirement timeline

Reference:

Feature Updates (2025-2026)

Microsoft Fabric Integration (GA)

ADF Mounting in Fabric:

  • Bring existing ADF pipelines into Fabric workspaces without rebuilding
  • Generally Available since June 2025
  • Seamless integration enables hybrid ADF + Fabric workflows

Cross-Workspace Pipeline Orchestration:

  • New Invoke Pipeline activity supports cross-platform calls
  • Invoke pipelines across Fabric, Azure Data Factory, and Synapse
  • Managed VNet support for secure cross-workspace communication

Variable Libraries:

  • Environment-specific variables for CI/CD automation
  • Automatic value substitution during workspace promotion
  • Eliminates separate parameter files per environment

Connector Enhancements:

  • ServiceNow V2 (V1 End of Support)
  • Enhanced PostgreSQL and Snowflake connectors
  • Native OneLake connectivity for zero-copy integration

Node.js 20.x Requirement for CI/CD

CRITICAL: As of 2025, npm package @microsoft/azure-data-factory-utilities requires Node.js 20.x

Breaking Change:

  • Older Node.js versions (14.x, 16.x, 18.x) may cause package incompatibility errors
  • Update CI/CD pipelines to use Node.js 20.x or compatible versions

GitHub Actions:

- name: Setup Node.js
  uses: actions/setup-node@v4
  with:
    node-version: '20.x'

Azure DevOps:

- task: UseNode@1
  inputs:
    version: '20.x'

Official Documentation Sources

Primary Microsoft Learn Resources

Main Documentation Hub:

  • URL: https://learn.microsoft.com/en-us/azure/data-factory/
  • Last Updated: February 2025
  • Coverage: Complete ADF documentation including tutorials, concepts, how-to guides, and reference materials
  • Key Topics: Pipelines, datasets, triggers, linked services, data flows, integration runtimes, monitoring

Introduction to Azure Data Factory:

Context7 Library Documentation

Library ID: /websites/learn_microsoft_en-us_azure_data-factory

  • Trust Score: 7.5
  • Code Snippets: 10,839
  • Topics: CI/CD, ARM templates, pipeline patterns, data flows, monitoring, troubleshooting

How to Access:

Use Context7 MCP tool to fetch latest documentation:
mcp__context7__get-library-docs:
  - context7CompatibleLibraryID: /websites/learn_microsoft_en-us_azure_data-factory
  - topic: "CI/CD continuous integration deployment pipelines ARM templates"
  - tokens: 8000

CI/CD Deployment Methods

Modern Automated Approach (Recommended)

npm Package: @microsoft/azure-data-factory-utilities

Key Features:

  • Validates ADF resources independently of service
  • Generates ARM templates programmatically
  • Enables true CI/CD without manual publish button
  • Supports preview mode for selective trigger management

package.json Configuration:

{
  "scripts": {
    "build": "node node_modules/@microsoft/azure-data-factory-utilities/lib/index",
    "build-preview": "node node_modules/@microsoft/azure-data-factory-utilities/lib/index --preview"
  },
  "dependencies": {
    "@microsoft/azure-data-factory-utilities": "^1.0.3"
  }
}

Commands:

# Validate resources
npm run build validate <rootFolder> <factoryId>

# Generate ARM templates
npm run build export <rootFolder> <factoryId> [outputFolder]

# Preview mode (only stop/start modified triggers)
npm run build-preview export <rootFolder> <factoryId> [outputFolder]

Official Documentation:

Traditional Manual Approach (Legacy)

Method: Git integration + Publish button

Process:

  1. Configure Git integration in ADF UI (Dev environment only)
  2. Make changes in ADF Studio
  3. Click "Publish" button to generate ARM templates
  4. Templates saved to adf_publish branch
  5. Release pipelines deploy from adf_publish branch

When to Use:

  • Migrating from existing setup
  • No build pipeline infrastructure
  • Simple deployments without validation

Limitations:

  • Requires manual publish action
  • No validation until publish
  • Not true CI/CD (manual step required)
  • Can't validate on pull requests

Migration Path: Modern approach recommended for new implementations

ARM Template Deployment

PowerShell Deployment

Primary Command: New-AzResourceGroupDeployment

Syntax:

New-AzResourceGroupDeployment `
  -ResourceGroupName "<resource-group-name>" `
  -TemplateFile "ARMTemplateForFactory.json" `
  -TemplateParameterFile "ARMTemplateParametersForFactory.<environment>.json" `
  -factoryName "<factory-name>" `
  -Mode Incremental `
  -Verbose

Validation:

Test-AzResourceGroupDeployment `
  -ResourceGroupName "<resource-group-name>" `
  -TemplateFile "ARMTemplateForFactory.json" `
  -TemplateParameterFile "ARMTemplateParametersForFactory.<environment>.json" `
  -factoryName "<factory-name>"

What-If Analysis:

New-AzResourceGroupDeployment `
  -ResourceGroupName "<resource-group-name>" `
  -TemplateFile "ARMTemplateForFactory.json" `
  -TemplateParameterFile "ARMTemplateParametersForFactory.<environment>.json" `
  -factoryName "<factory-name>" `
  -WhatIf

Azure CLI Deployment

Primary Command: az deployment group create

Syntax:

az deployment group create \
  --resource-group <resource-group-name> \
  --template-file ARMTemplateForFactory.json \
  --parameters ARMTemplateParametersForFactory.<environment>.json \
  --parameters factoryName=<factory-name> \
  --mode Incremental

Validation:

az deployment group validate \
  --resource-group <resource-group-name> \
  --template-file ARMTemplateForFactory.json \
  --parameters ARMTemplateParametersForFactory.<environment>.json \
  --parameters factoryName=<factory-name>

What-If Analysis:

az deployment group what-if \
  --resource-group <resource-group-name> \
  --template-file ARMTemplateForFactory.json \
  --parameters ARMTemplateParametersForFactory.<environment>.json \
  --parameters factoryName=<factory-name>

PrePostDeploymentScript

Current Version: Ver2

Location: https://github.com/Azure/Azure-DataFactory/blob/main/SamplesV2/ContinuousIntegrationAndDelivery/PrePostDeploymentScript.Ver2.ps1

Key Improvement in Ver2:

  • Turns off/on ONLY triggers that have been modified
  • Ver1 stopped/started ALL triggers (slower, more disruptive)
  • Compares trigger payloads to determine changes

Download Command:

# Linux/macOS/Git Bash
curl -o PrePostDeploymentScript.Ver2.ps1 https://raw.githubusercontent.com/Azure/Azure-DataFactory/main/SamplesV2/ContinuousIntegrationAndDelivery/PrePostDeploymentScript.Ver2.ps1

# PowerShell
Invoke-WebRequest -Uri "https://raw.githubusercontent.com/Azure/Azure-DataFactory/main/SamplesV2/ContinuousIntegrationAndDelivery/PrePostDeploymentScript.Ver2.ps1" -OutFile "PrePostDeploymentScript.Ver2.ps1"

Parameters

Pre-Deployment (Stop Triggers):

./PrePostDeploymentScript.Ver2.ps1 `
  -armTemplate "<path-to-ARMTemplateForFactory.json>" `
  -ResourceGroupName "<resource-group-name>" `
  -DataFactoryName "<factory-name>" `
  -predeployment $true `
  -deleteDeployment $false

Post-Deployment (Start Triggers & Cleanup):

./PrePostDeploymentScript.Ver2.ps1 `
  -armTemplate "<path-to-ARMTemplateForFactory.json>" `
  -ResourceGroupName "<resource-group-name>" `
  -DataFactoryName "<factory-name>" `
  -predeployment $false `
  -deleteDeployment $true

PowerShell Requirements

Version: PowerShell Core (7.0+) recommended

  • Azure DevOps: Use pwsh: true in AzurePowerShell@5 task
  • Locally: Use pwsh command, not powershell

Modules Required:

  • Az.DataFactory
  • Az.Resources

Official Documentation:

GitHub Actions CI/CD

Official Resources

Medium Article (Recent 2025):

Microsoft Community Hub:

Community Blog (February 2025):

Key GitHub Actions

Essential Actions:

  • actions/checkout@v4 - Checkout repository
  • actions/setup-node@v4 - Setup Node.js
  • actions/upload-artifact@v4 - Publish ARM templates
  • actions/download-artifact@v4 - Download ARM templates in deploy workflow
  • azure/login@v2 - Authenticate to Azure
  • azure/arm-deploy@v2 - Deploy ARM templates
  • azure/powershell@v2 - Run PrePostDeploymentScript

Authentication Methods

Service Principal (JSON credentials):

{
  "clientId": "<GUID>",
  "clientSecret": "<STRING>",
  "subscriptionId": "<GUID>",
  "tenantId": "<GUID>"
}

Store in GitHub secret: AZURE_CREDENTIALS

Workload Identity Federation (More secure):

Azure DevOps CI/CD

Official Resources

Microsoft Learn:

Community Guides:

Towards Data Science:

Key Azure DevOps Tasks

Build Pipeline Tasks:

  • UseNode@1 - Install Node.js
  • Npm@1 - Install packages, run build commands
  • PublishPipelineArtifact@1 - Publish ARM templates

Release Pipeline Tasks:

  • DownloadPipelineArtifact@2 - Download ARM templates
  • AzurePowerShell@5 - Run PrePostDeploymentScript
  • AzureResourceManagerTemplateDeployment@3 - Deploy ARM template

Service Connection Requirements

Permissions Needed:

  • Data Factory Contributor (on all Data Factories)
  • Contributor (on Resource Groups)
  • Key Vault access policies (if using secrets)

Configuration:

  • Project Settings → Service connections → New service connection
  • Type: Azure Resource Manager
  • Authentication: Service Principal (recommended) or Managed Identity

Troubleshooting Resources

Official Troubleshooting Guide

URL: https://learn.microsoft.com/en-us/azure/data-factory/ci-cd-github-troubleshoot-guide Last Updated: January 2025

Common Issues Covered:

  1. Template parameter validation errors
  2. Integration Runtime type cannot be changed
  3. ARM template size exceeds 4MB limit
  4. Git connection problems
  5. Authentication failures
  6. Deployment errors

Diagnostic Logs

Enable Diagnostic Settings:

Azure Portal → Data Factory → Diagnostic settings → Add diagnostic setting
Send to: Log Analytics workspace

Logs to Enable:
- PipelineRuns
- TriggerRuns
- ActivityRuns
- SandboxPipelineRuns
- SandboxActivityRuns

Kusto Queries for Troubleshooting:

// Failed pipeline runs in last 24 hours
ADFPipelineRun
| where Status == "Failed"
| where TimeGenerated > ago(24h)
| project TimeGenerated, PipelineName, RunId, Status, ErrorMessage, Parameters
| order by TimeGenerated desc

// Failed CI/CD deployments
ADFActivityRun
| where ActivityType == "ExecutePipeline"
| where Status == "Failed"
| where TimeGenerated > ago(7d)
| project TimeGenerated, PipelineName, ActivityName, ErrorCode, ErrorMessage
| order by TimeGenerated desc

// Performance analysis
ADFActivityRun
| where TimeGenerated > ago(7d)
| extend DurationMinutes = datetime_diff('minute', End, Start)
| summarize AvgDuration = avg(DurationMinutes) by ActivityType, ActivityName
| where AvgDuration > 10
| order by AvgDuration desc

Common Error Patterns

Error: "Template parameters are not valid"

  • Cause: Deleted triggers still referenced in parameters
  • Solution: Regenerate ARM template or use PrePostDeploymentScript cleanup

Error: "Updating property type is not supported"

  • Cause: Trying to change Integration Runtime type
  • Solution: Delete and recreate IR (not in-place update)

Error: "Operation timed out"

  • Cause: Network connectivity, large data volume, insufficient compute
  • Solution: Increase timeout, optimize query, increase DIUs

Error: "Authentication failed"

  • Cause: Service principal expired, missing permissions, wrong credentials
  • Solution: Verify credentials, check role assignments, renew if expired

Best Practices

Repository Structure

Recommended Folder Layout:

repository-root/
├── adf-resources/          # ADF JSON files (if using npm approach)
│   ├── dataset/
│   ├── pipeline/
│   ├── trigger/
│   ├── linkedService/
│   └── integrationRuntime/
├── .github/
│   └── workflows/          # GitHub Actions workflows
│       ├── adf-build.yml
│       └── adf-deploy.yml
├── azure-pipelines/        # Azure DevOps pipelines
│   ├── build.yml
│   └── release.yml
├── parameters/             # Environment-specific parameters
│   ├── ARMTemplateParametersForFactory.dev.json
│   ├── ARMTemplateParametersForFactory.test.json
│   └── ARMTemplateParametersForFactory.prod.json
├── package.json            # npm configuration
└── README.md

Git Configuration

Only Configure Git on Development ADF:

  • Development: Git-integrated for source control
  • Test: CI/CD deployment only (no Git)
  • Production: CI/CD deployment only (no Git)

Rationale: Prevents accidental manual changes in higher environments

Multi-Environment Strategy

Environment Flow:
Dev (Git) → Build → Test → Approval → Production
            ↓
        ARM Templates

Parameter Management:

  • Separate parameter file per environment
  • Store secrets in Azure Key Vault
  • Reference Key Vault in parameter files
  • Never commit secrets to source control

Monitoring and Alerting

Set up alerts for:

  • Build pipeline failures
  • Deployment failures
  • Pipeline run failures
  • Performance degradation
  • Cost anomalies

Recommended Tools:

  • Azure Monitor (Metrics and Alerts)
  • Log Analytics (Kusto queries)
  • Application Insights (for custom logging)
  • Azure Advisor (optimization recommendations)

Additional Resources

GitHub Repositories

Official Azure Data Factory Samples:

Community Examples:

  • Search GitHub for "azure-data-factory-cicd" for real-world examples
  • Many organizations publish their CI/CD patterns as reference

Community Support

Microsoft Q&A:

Stack Overflow:

  • Tag: azure-data-factory
  • Large knowledge base of resolved issues

Azure Status:

When to Fetch Latest Information

Situations requiring current documentation:

  1. npm package version updates
  2. New ADF features or activities
  3. Changes to ARM template schema
  4. Updates to PrePostDeploymentScript
  5. New GitHub Actions or Azure DevOps tasks
  6. Breaking changes or deprecations

How to Fetch:

  • Use WebFetch for Microsoft Learn articles
  • Check npm for latest package version
  • Use Context7 for comprehensive topic coverage
  • Review Azure Data Factory GitHub for script updates

This knowledge base should be your starting point for all Azure Data Factory questions. Always verify critical information with the latest official documentation when making production decisions.

Progressive Disclosure References

For detailed JSON schemas and complete reference materials, see:

  • Activity Types: references/activity-types.md - Complete JSON schemas for all activity types (Copy, ForEach, IfCondition, Switch, Until, Lookup, ExecutePipeline, WebActivity, DatabricksJob, SetVariable, AppendVariable, Wait, Fail, GetMetadata)
  • Expression Functions: references/expression-functions.md - Complete reference for all ADF expression functions (string, collection, logical, conversion, math, date/time, pipeline/activity references)
  • Linked Services: references/linked-services.md - Complete JSON configurations for all connector types (Blob Storage, ADLS Gen2, Azure SQL, Synapse, Fabric Lakehouse/Warehouse, Databricks, Key Vault, REST, SFTP, Snowflake, PostgreSQL)
  • Triggers: references/triggers.md - Complete JSON schemas for schedule, tumbling window, and event triggers
  • Datasets: references/datasets.md - Complete JSON schemas for all dataset types with parameterization patterns

For machine learning and analytics patterns, see the dedicated skill:

  • ML & Analytics: adf-master:adf-ml-analytics - Azure ML pipelines, batch endpoints, Azure AI Services, Databricks ML/MLflow, SQL-to-Storage archival, feature engineering with Data Flows

平台分布

Claude Code

28.4%
按下载量换算189

OpenCode

21.85%
按下载量换算146

Antigravity

18.22%
按下载量换算121

Gemini CLI

13.22%
按下载量换算88

windsurf

7.87%
按下载量换算52

Cursor

3.26%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills