Name: dependency-flow
Rating: 71.2 (1 reviews)
Author: dotnet

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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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

The content is highly actionable with excellent workflow sequencing and validation gates for risky/batch operations, but it is a verbose monolith that would benefit from splitting reference-grade material into separate files and trimming restated rationale and time-sensitive specifics.

Suggestions

Split the large "Subscription Authoring & Lifecycle" and "Preview release readiness" sections into one-level-deep reference files (e.g. references/subscription-lifecycle.md, references/preview-readiness.md) and link to them from a concise overview in SKILL.md.

De-duplicate the PR #35364 channel/branch mismatch trap and the "public BAR cannot identify the blessed build" rationale — state each once and cross-reference, instead of restating across channel naming, subscription authoring, and readiness sections.

Move time-sensitive specifics (the 2026-06-02 subscription baseline, 2026-07-07 worked examples, numeric channel IDs) into a clearly dated "current state" reference so the core guidance does not age inline.

Dimension	Reasoning	Score
Conciseness	The body is operationally dense but ~580 lines with notable padding — the PR #35364 trap and the "public BAR can't identify the blessed build" rationale are each restated across multiple sections, and inline time-sensitive specifics ("2026-06-02", "2026-07-07", channel IDs) age the content without living in a deprecation/old-patterns section.	2 / 3
Actionability	Commands are concrete and copy-paste ready with real flags (e.g. `darc get-asset --name Microsoft.Maui.Controls --version X.Y.Z`, the full combined-PR bash loop, MCP calls with exact parameter names), and the "User says → Action" table maps natural requests to exact commands.	3 / 3
Workflow Clarity	Multi-step workflows are explicitly sequenced with validation checkpoints — the feed-lookup flow is numbered 1–6 with a STOP-and-confirm gate, and the combined-PR pattern has a numbered REQUIRED review-gate checklist plus a "do not mark ready until this check passes" feedback loop.	3 / 3
Progressive Disclosure	The one bundle script is correctly externalized and referenced at its real path, but the SKILL.md itself is a monolithic 580-line document carrying several reference-grade sections (channel naming, subscription authoring, preview readiness, the A/B/C checks) inline rather than split into one-level-deep reference files.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is specific, trigger-rich, third-person, and clearly answers both what and when with an explicit "Use when" clause. It carves a distinct MAUI niche that is unlikely to fire for the wrong skill.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities — "dependency flow rules, channel conventions, and feed lookup workflows" plus "build promotion, asset lookup, channel mappings" — rather than vague language.	3 / 3
Completeness	It explicitly answers both what (MAUI-specific dependency flow rules/conventions/workflows) and when (an explicit "Use when asked about ..." trigger clause).	3 / 3
Trigger Term Quality	The "Use when asked about darc, BAR, Maestro, feeds for .NET MAUI, build promotion, asset lookup, channel mappings, or dependency flow" clause covers the natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	It is scoped tightly to MAUI/dotnet-maui with distinct triggers (darc, BAR, Maestro-for-MAUI); the "wraps the maestro-cli skill and maestro MCP tools" framing is a clear niche rather than a generic overlap.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (586 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
Commit: 6a24ec5

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.