agentleFS
SentryKnown publishergetsentry/MobileBuildMCP/.agents/skills/mobilebuildmcp-tool-contract-review/SKILL.md

mobilebuildmcp-tool-contract-review

Skill6.5k starsChanged 39 days agoMITView on GitHub

Use when reviewing MobileBuildMCP tool contract changes across implementation, manifests, workflow membership, output schema metadata, and next-step templates.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not edit product code unless the user explicitly requests implementation changes.

    line 13
  2. Distinctive:

    Avoid parallel legacy paths or duplicate implementation paths.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MobileBuildMCP Tool Contract Review

Review guardrails for tool contract changes across implementation, manifests, and workflow exposure.

Review scope

  • Review-only by default.
  • Do not edit product code unless the user explicitly requests implementation changes.

Files to inspect

  • src/mcp/tools/**
  • manifests/tools/*.yaml
  • manifests/workflows/*.yaml
  • src/core/manifest/schema.ts
  • src/runtime/tool-catalog.ts
  • src/runtime/types.ts
  • xcodebuildmcp.com/app/docs/_content/tool-authoring.mdx
  • xcodebuildmcp.com/app/docs/_content/architecture-manifest-visibility.mdx

Guardrails

  • Manifest id matches filename.
  • Manifest module points to implementation path without extension.
  • Tool module exports named schema and handler.
  • names.mcp remains globally unique.
  • names.cli stays workflow-local and consistent with CLI docs/fixtures.
  • Tool appears in at least one workflow unless intentionally hidden by availability.
  • outputSchema is present for tools that set ctx.structuredOutput.
  • nextSteps.toolId references existing manifest tool IDs.
  • Avoid parallel legacy paths or duplicate implementation paths.

Validation

  • npm run typecheck
  • npm test -- src/core/manifest/__tests__/schema.test.ts
  • npm test -- src/runtime/__tests__/tool-invoker.test.ts
  • npx skill-check .agents/skills/mobilebuildmcp-tool-contract-review

Download now (ZIP)

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 2 mentionsOct 2026: 5 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the getsentry/MobileBuildMCP repository that our weekly crawl found: only 7 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about getsentry/MobileBuildMCP

The biggest 5 of 7 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 7

Talked about on GitHub (7 times).

On GitHub · 7

2 more on GitHub

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.