connector-development

Develop connectors that standardize idempotent artifact publishing across Intune, Jamf Pro, SCCM, Landscape, and Ansible.

Updated Jan 4, 2026

Search Tags:#Ansible #idempotency #connectors #Jamf Pro #Graph API #Intune #SCCM

Ready to run

npx skills add https://github.com/buildworksai/EUCORA --skill connector-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: connector-development
Source: https://github.com/buildworksai/EUCORA/tree/main/.agents/skills/connector-development
Command: npx skills add https://github.com/buildworksai/EUCORA --skill connector-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

EUCORA's execution-plane connectors require consistent, idempotent patterns to integrate with diverse platforms (Intune, Jamf Pro, SCCM, Landscape, and Ansible) while maintaining governance and reliability across endpoints.

Core Features & Use Cases

Connector templates and base patterns for idempotent deployments across platforms.
Platform coverage: Intune, Jamf Pro, SCCM, Landscape, and Ansible with standard authentication and deployment workflows.
Use Case: Build a new Intune connector that can publish apps with correlation IDs and report deployment status back to EUCORA.

Quick Start

Use the connector-development pattern to scaffold a new integration, start with an Intune example, and adapt the base BaseConnector to implement authenticate, publish, and get_deployment_status.

Frequently Asked Questions about connector-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build idempotent connectors for Intune, Jamf Pro, and SCCM?▼

Idempotent connectors use correlation IDs to detect and skip duplicate deployments across platforms. The connector-development pattern provides a BaseConnector template with authenticate, publish, and get_deployment_status methods you implement per platform to standardize artifacts and report status back to EUCORA.

What's the best way to ensure consistent deployments across multiple execution planes?▼

Use a base connector pattern that standardizes authentication, deployment workflows, and status reporting across Intune, Jamf Pro, SCCM, Landscape, and Ansible. This approach maintains governance and reliability by applying the same correlation-based idempotency logic to each platform.

Can I use Ansible with the same connector pattern as Intune and Jamf Pro?▼

Yes. The connector-development Skill supports platform coverage across Intune, Jamf Pro, SCCM, Landscape, and Ansible through a reusable BaseConnector pattern. Adapt the base class to each platform's authentication and deployment APIs while maintaining consistent error handling and idempotency checks.

How do I handle deployment status reporting and error tracking across multiple platforms?▼

Implement the get_deployment_status method in your connector to report status back to EUCORA and use structured error handling with correlation IDs for tracking. This enables reliable deployment lifecycles and cross-platform governance in large-scale environments.

What prerequisites do I need before building a new connector integration?▼

You need platform-specific API credentials and authentication workflows for your target system (Intune, Jamf Pro, SCCM, Landscape, or Ansible), understanding of correlation-based idempotency patterns, and familiarity with standardizing artifact formats across execution planes.