CtrlK
BlogDocsLog inGet started
Tessl Logo

mobile-platforms

Domain knowledge for triaging and fixing .NET failures on Apple mobile (iOS, tvOS, MacCatalyst) and Android. Use when runtime-extra-platforms or mobile CI is failing, when investigating iOS, tvOS, MacCatalyst, iossimulator, tvossimulator, or Android build/test failures, or when a change touches mobile pipeline YAML, AppleAppBuilder/AndroidAppBuilder, code signing, provisioning, simulator/emulator startup, platform conditionals, or NativeAOT-on-mobile behavior. Covers failure triage (infrastructure vs code), CI pipeline structure, platform-specific code paths, and NativeAOT compilation on mobile.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%Weight 40%Scale 1-3

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

A dense, actionable triage reference that earns top marks for conciseness and actionability. It loses points on workflow clarity (no explicit fix-verification checkpoint) and progressive disclosure (monolithic single file with no references).

Suggestions

Add an explicit verification step to the failure triage workflow, e.g. "After the fix, re-run the failing job/PR pipeline and confirm the target job passes before merging."

Consider moving the detailed pipeline-YAML file listings and NativeAOT target-resolution specifics into reference files under references/ (e.g. PIPELINES.md, NATIVEAOT.md) and linking to them from SKILL.md, so the main body stays a concise overview.

Add a short 'Quick triage' decision tree at the top (failure type -> first file/path to check) so the classification checkpoint is explicit rather than implied.

DimensionReasoningScore

Conciseness

Dense, non-obvious reference material — real file paths, the MSBuild evaluation-order gotcha, and the dsymutil stdout/stderr note — with no padding explaining basic concepts Claude already knows.

3 / 3

Actionability

Highly actionable: concrete paths ("src/mono/msbuild/apple/build/"), an executable command ("git log --oneline --since='3 days ago'"), and exact config ("ILCompilerTargetsPath must be set to $(CoreCLRBuildIntegrationDir)Microsoft.DotNet.ILCompiler.SingleEntry.targets with _IlcReferencedAsPackage=false").

3 / 3

Workflow Clarity

The triage flow classifies infrastructure vs code with indicator checklists and a decision point, but there is no explicit verify-the-fix validation checkpoint or feedback loop, so it sits at the "sequence present but checkpoints implicit" level rather than 3.

2 / 3

Progressive Disclosure

Well-organized into headed sections and tables, but it is a single ~133-line file with no external references and inline detail (pipeline YAML listings, NativeAOT specifics) that could be split out, so it does not meet the "one-level-deep references, content appropriately split" bar for 3.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 precise, third-person description with explicit "Use when" triggers, concrete actions, and natural trigger terms scoped to a distinct .NET mobile niche. It cleanly satisfies all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "triaging and fixing .NET failures" and "Covers failure triage (infrastructure vs code), CI pipeline structure, platform-specific code paths, and NativeAOT compilation on mobile" — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what and when via "Use when runtime-extra-platforms or mobile CI is failing, when investigating ... build/test failures"; written in third person with no first/second person.

3 / 3

Trigger Term Quality

Strong coverage of natural terms a .NET mobile engineer would say: "iOS, tvOS, MacCatalyst, iossimulator, tvossimulator, or Android build/test failures" plus "code signing, provisioning, simulator/emulator startup", not just jargon.

3 / 3

Distinctiveness Conflict Risk

A clear niche — "triaging and fixing .NET failures on Apple mobile (iOS, tvOS, MacCatalyst) and Android" — with distinct, platform-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
dotnet/runtime
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.