simulator-runtime-verification SKILL.md skillA
simulator-runtime-verification from wei18/apple-dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wei18/apple-dev-skills/simulator-runtime-verification@git:20261114.0aa217ePins git:20261114.0aa217e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wei18/apple-dev-skills
- Path
apple-dev-skills/skills/simulator-runtime-verification/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261114.0aa217e, committed Nov 14, 2026
- Size
- 17,201 bytes
- Repository stars
- 18
- License
- MIT
Verify on an iOS Simulator the runtime behaviour unit tests cannot reach, and avoid the traps that fake a result: APNs device tokens and pushes (`simctl push`), Universal Links and custom-scheme sign-in returns (`simctl openurl`), Keychain writes, seeded `UserDefaults`, ATT and permission resets, and an old-build-to-new-build upgrade install. Use when a check must prove push registration, deep-link or sign-in return handling, or persisted state surviving an app update; when probing a framework…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Simulator Runtime Verification Recipes for proving app behaviour that only exists at runtime (push registration, link handling, Keychain and `UserDefaults` state, permission prompts, upgrade installs) on an iOS Simulator, run from the main session with `xcrun simctl`, `lldb`, host `defaults`, `strings` and a local HTTP server. Most of the traps below do not fail loudly. They produce a wrong verdict: a regression that is not there, or a pass that proves nothing. Version stamps give the Simulator runtime and date each behaviour was observed on. "Observed once" means one sighting; re-check it on your runtime before you rely on it. ## When to invoke - A change touches push registration, notification presentation, or a Notification Service Extension, and the PR claims it was verified. - A change touches Universal Link, custom URL scheme, or sign-in redirect handling. - A change touches stored state (`UserDefaults`, Keychain) and must keep working when a user updates from the previous release. - A Simulator Keychain call returns `-34018`, or sign-in succeeds on the server but the app stays signed out. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_tlmtnnphyuzio3mk/14ac6bf3dc0bbe44fc52395d901f3f8eec7b0985f64886eadb034aa78d984303.json
Then /plugin install simulator-runtime-verification@markdownregistry-tlmtnnphyuzio3mk in Claude Code. It installs git:20261114.0aa217e, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add wei18/apple-dev-skills/simulator-runtime-verification@sha256:14ac6bf3dc0bbe44The line at the top of this page pins the label git:20261114.0aa217e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_tlmtnnphyuzio3mk)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in wei18/apple-dev-skills/simulator-runtime-verification since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of simulator-runtime-verification from somewhere else? Ask it: where did my simulator-runtime-verification come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 14, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/simulator-runtime-verification/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17201 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wei18/apple-dev-skills · 18 stars · license MIT · pushed 2026-11-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tlmtnnphyuzio3mk GET https://markdownregistry.com/api/v1/resolve?ref=wei18/apple-dev-skills/simulator-runtime-verification GET https://markdownregistry.com/api/v1/blob/14ac6bf3dc0bbe44fc52395d901f3f8eec7b0985f64886eadb034aa78d984303
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.