helix.mcp: Skill for Claude Code

SKILL: Helix Job Source Filter

Purpose: Look up all Helix jobs for an AzDO build using the canonical Job.ListAsync(source) + BuildId filter pattern, instead of scraping AzDO timeline task names.

---

Problem

AzDO timeline scraping (Name.Contains("helix", …)) fails for repos where the Helix dispatch task has a non-standard name (e.g., dotnet/sdk uses "🟣 Run TestBuild Tests"). The Helix API has first-class support for this lookup via job source strings and the BuildId job property.

---

Source string formula (from arcade HelixJobSource.Compute)

source = "{prefix}/{teamProject}/{repository}/{sourceBranch}"

prefix rules (case-insensitive, mirror arcade exactly):
  Build.Reason == "PullRequest"    → "pr"
  System.TeamProject == "internal" → "official"
  anything else                    → "ci"

Examples:

• PR build on public: pr/public/dotnet/runtime/refs/pull/42/merge
• CI on main (public): ci/public/dotnet/sdk/refs/heads/main
• Internal official: official/internal/dotnet/runtime/refs/heads/main
• Manual on public: ci/public/dotnet/arcade/refs/heads/main (NOT "official")

System.TeamProject (AzDO variable) is in Build.Project.Name in the REST response. Build.Repository.Name for GitHub-backed repos is owner/repo (e.g. dotnet/runtime).

---

Filter logic (from arcade HelixService.GetJobsForBuildAsync)

// count: 100_000 cap — generous for ~1k–5k jobs per build; realistic CI never hits it
var jobs = await helixApi.Job.ListAsync(source: source, count: 100_000);
return jobs.Where(j => j.Properties is JObject props
    && props.TryGetValue("BuildId", out var id)
    && id.ToString() == buildId.ToString());

Key points:

• BuildId is stored as a JSON string in Properties; compare via ToString() not int
• JToken.ToString() on a string-valued token returns the string value directly
• Job.ListAsync(source) does a prefix match — pass the full source string for exact match

---

AzdoBuild fields required