Airflow adapter pattern for v2/v3 API compatibility. Use when working with adapters, version detection, or adding new API methods that need to work across Airflow 2.x and 3.x.
This skill should be used when the user asks about "Azure Data Factory CI/CD", "ADF ARM template deployment", "ADF npm build validation", "PrePostDeploymentScript", or needs guidance on ADF pipelines, triggers, GitHub Actions, or Azure DevOps integration. --- # 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:** - Microsoft Roadmap: https://www.directionsonmicrosoft.com/roadmaps/ref/azure-data-factory-roadmap/ ## 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
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills:
