Generate Harness Connector YAML for integrations and create/test via MCP. Use when user says "create connector", "git connector", "aws connector", "docker connector", "cloud connector", or wants to connect Harness to external services.
83
73%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/claude/skills/create-connector/SKILL.mdGitHub connector YAML structure
Github connector type
100%
100%
Http authentication type
100%
100%
UsernameToken auth spec
100%
100%
username field present
100%
100%
tokenRef for PAT
100%
100%
apiAccess block
100%
100%
apiAccess Token type
100%
100%
Account or Repo scope
100%
100%
executeOnDelegate field
100%
100%
org URL field
100%
100%
Kubernetes connector with delegate selectors and account-level secrets
K8sCluster connector type
100%
100%
ManualConfig credential type
100%
100%
masterUrl field
100%
100%
ServiceAccount auth type
100%
100%
serviceAccountTokenRef field
100%
100%
caCertRef field
100%
100%
delegateSelectors field
100%
100%
Exact delegate tag value
100%
100%
SA token account-level secret
100%
100%
CA cert account-level secret
100%
100%
Azure connector YAML and full MCP lifecycle workflow
Azure connector type
100%
100%
ManualConfig credential
100%
100%
applicationId field
100%
100%
tenantId field
100%
100%
azureEnvironmentType field
100%
100%
Project-level secret format
100%
100%
executeOnDelegate: false
0%
100%
harness_create tool call
0%
100%
org_id and project_id parameters
0%
100%
harness_execute test_connection
0%
100%
Verify secrets before creation
100%
100%
a000afa
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.