device-interaction skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
device-interaction is agent-read markdown (skill) from tartinerlabs/skills: Verify app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Device Interaction TRIGGER when: user asks to verify/test/check if the app works on device, after implementing a UI-affecting feature that needs device verification, user says "does it work", "test this", "check on device", user reports UI doesn't work as expected, need to debug touch/interaction issues. DO NOT TRIGGER when: user asks about unit tests only, build-only requests without device testing, code review without device testing, simulator configuration questions, changes that don't affect UI (e.g. comments, refactors, non-UI logic). --- # For the Main Agent **This is a SUBAGENT skill.** Invoke it via the Agent tool when device verification is needed. If there is an open session for that work, provide that session identifier to a subagent for exclusive use by that subagent. ``` Agent tool: - subagent_type: "general-purpose" - description: "Verify login feature works" - prompt: "Using the device-interaction skill, verify that the login feature works correctly on session <session-identifier>. Launch the app, capture screenshot and UI hierarchy, check that the login button is visible and tappable, and report if the implementation is working correctly." ``` …
Read the whole file at its exact version.
How to install
mdr add tartinerlabs/skills/device-interaction@git:20260919.39b6890mdr add tartinerlabs/skills/device-interaction@sha256:fa6cc5115c15f43fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_vhiy5i3lfwiocmq7)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.39b6890 latest | 2026-09-19 | 39b6890 | 12,495 B | A | view · diff |
| git:20260713.ba4f7f8 | 2026-07-13 | ba4f7f8 | 7,873 B | A | view |
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 (12495 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
tartinerlabs/skills · 8 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vhiy5i3lfwiocmq7 GET https://markdownregistry.com/api/v1/resolve?ref=tartinerlabs/skills/device-interaction GET https://markdownregistry.com/api/v1/blob/fa6cc5115c15f43fd5b2718c8705bec6cc0d6932309bf0df47ede28c0592b044
Your agent 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.
More from tartinerlabs/skills
Every file in tartinerlabs/skills