CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dependency-flow

MAUI-specific dependency flow rules, channel conventions, and feed lookup workflows. Use when asked about darc, BAR, Maestro, feeds for .NET MAUI, build promotion, asset lookup, channel mappings, or dependency flow for dotnet/maui. Wraps the maestro-cli skill and maestro MCP tools with MAUI-specific guardrails.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Operationally excellent content: fully executable commands, explicit confirmation gates, validation checklists, and error-recovery loops covering destructive and batch operations. The weaknesses are length and structure — significant repetition, dated snapshots that will age, and a monolithic 640-line body where three large topics should be split into one-level-deep reference files.

Suggestions

Move Subscription Authoring & Lifecycle, Preview release readiness, and the Wiring checks into separate reference files (e.g., references/subscriptions.md, references/release-readiness.md, references/wiring-checks.md) linked from a lean SKILL.md overview, keeping the NEVER/confirmation lists and quick reference inline.

State the confirmation-gate requirement once in the 'Commands requiring explicit user confirmation' section and reference it by name elsewhere instead of repeating the full instruction at each occurrence; do the same for the angle-bracket shell-quoting tip.

Move the dated subscription baseline table and the 2026-07-07 worked example into an explicitly labeled 'snapshot / verify against live config' reference so time-sensitive data is isolated from the evergreen workflow guidance.

DimensionReasoningScore

Conciseness

Dense with genuinely non-obvious domain knowledge (no explaining of concepts Claude already knows), but noticeably over-long at ~640 lines with clear tightening opportunities: the confirmation-gate instruction is repeated in ~5 places ("Show the user the exact command and wait for explicit approval"), the shell-quoting tip about angle-bracket placeholders appears twice, PR #35364 is re-explained repeatedly, and time-sensitive snapshots ("MAUI subscription baseline (as of 2026-07-27)", a worked example dated "live 2026-07-07" with build #321033) sit outside any 'old patterns' section, though the baseline is at least flagged as aging out. Fits anchor 3 (mostly efficient, some unnecessary explanation, could be tightened) better than 2, since the verbosity is redundancy rather than low-value padding.

3 / 5

Actionability

Copy-paste-ready commands throughout: exact darc invocations with flags (`darc get-asset --name Microsoft.Maui.Controls --version X.Y.Z`, `darc add-build-to-channel --id <BAR_BUILD_ID> --channel ".NET 10 Workload Release"`), named MCP calls with parameters (`maestro_latest_build(repository="https://github.com/dotnet/maui")`), a complete `az repos pr create` command, git commands, and interpretation tables mapping every observed state to a meaning and a report action. Common cases are fully covered by executable examples.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops: the feed-lookup workflow's numbered steps include "4. STOP — show the user the exact add-build-to-channel command and wait for explicit confirmation" and a post-promotion poll loop ("Wait for promotion build (can take several minutes), then re-check"); the combined-PR pattern has a step-3 diff-review checklist with error recovery ("abandon the draft PR AND start over with a NEW $BRANCH name") and "Do NOT mark the PR ready for review until this check passes"; the access-tier workflow branches deterministically on a status token. Matches the anchor-5 example (explicit validation, error-recovery loops, checklists) — destructive/batch operations all carry validation, so no cap applies.

5 / 5

Progressive Disclosure

The single bundle file (scripts/Get-PreviewReleaseReadiness.ps1) is real and clearly referenced (`pwsh ./.github/skills/dependency-flow/scripts/Get-PreviewReleaseReadiness.ps1`), and in-file section organization with headers and a lifecycle quick-reference table is good. But ~640 lines are inlined monolithically: the Subscription Authoring & Lifecycle (~130 lines), Preview release readiness (~100 lines), and Wiring checks (~120 lines) sections clearly belong in separate reference files linked from a lean overview. Fits anchor 3 (some structure, content that should be separate is inline); not 2 because structure and the one existing reference are clear, not buried or nested.

3 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use when' clause carrying many natural trigger terms and a clearly stated, narrowly scoped MAUI niche. Its weaknesses are minor: capabilities are named as topics rather than actions, and it omits subscription management and release readiness, which make up much of the skill body.

Suggestions

Convert the 'what' clause toward concrete actions (e.g., 'looks up feeds for MAUI versions, promotes builds to workload release channels, and authors/verifies Maestro subscriptions') so capabilities read as verbs rather than topic nouns.

Add 'subscriptions', 'subscription health', and 'preview release readiness' to the trigger list, since these are major sections of the skill a user would ask about by name.

DimensionReasoningScore

Specificity

Names the domain plus several concrete capability areas — "dependency flow rules, channel conventions, and feed lookup workflows", "Wraps the maestro-cli skill and maestro MCP tools with MAUI-specific guardrails" — but capabilities are stated as topics rather than executable actions (feed lookup, build promotion appear only as trigger terms), and coverage has gaps: the body's large subscription-authoring and release-readiness sections are unmentioned. Not 3 (more than 1-2 concrete items); not 5 (nominal phrasing and coverage gaps).

4 / 5

Completeness

Explicitly answers both: what — "MAUI-specific dependency flow rules, channel conventions, and feed lookup workflows... Wraps the maestro-cli skill and maestro MCP tools with MAUI-specific guardrails"; when — "Use when asked about darc, BAR, Maestro, feeds for .NET MAUI, build promotion, asset lookup, channel mappings, or dependency flow for dotnet/maui" with concrete trigger phrases. Clear match to the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Good natural-term coverage: "darc, BAR, Maestro, feeds for .NET MAUI, build promotion, asset lookup, channel mappings, or dependency flow for dotnet/maui" — these are phrases a user would naturally say, including tool names and the repo name. Not 5 because a few natural terms are missing despite being major body topics: no "subscription(s)" trigger (roughly 40% of the skill) and no release-readiness or Version.Details.xml phrasing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: "MAUI-specific", "dotnet/maui", and darc/BAR/Maestro terms would not fire for unrelated skills. The "Wraps the maestro-cli skill" mention acknowledges a sibling skill but the triggers are scoped to MAUI, so overlap risk is minimal.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (646 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

dotnet/maui

Path

.github/skills/dependency-flow/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.