agent-device
Automate App Workflows with agent-device
App interaction tasks require reliable targeting and visible verification across device interfaces. This skill guides agent-device commands for navigation, inspection, verification, and session cleanup.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "agent-device" from https://skillstore.io/skills/callstack-agent-device.md and its manifest at https://skillstore.io/api/skills/callstack-agent-device/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.
Tester
Utilisation de « agent-device ». Illustrative request: open a configured test app and summarize its initial screen.
RĂ©sultat attendu:
- Illustrative result: the app opened in the foreground and returned an interactive snapshot.
- The visible screen contained a title and selectable controls with reference tokens.
- The session was closed after inspection.
Utilisation de « agent-device ». Illustrative request: find an off-screen settings entry and verify the destination.
RĂ©sultat attendu:
- Illustrative result: scrolling to the selected entry made it visible.
- Selecting the current reference opened the destination screen.
- The expected heading was verified, and the session was closed.
Audit de sécurité
SûrAll nine static findings are false positives: eight match Markdown backticks, and one matches the app-automation description. No evidence found of executable backtick substitution, malicious reconnaissance, data exfiltration, or prompt injection in the reviewed file. The skill provides CLI guidance; the external tool implementation and its runtime behavior were not reviewed.
Facteurs de risque
⚙️ Commandes externes (8)
Partager et citer ce rapport
Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.
Copier le lien du rapport
https://skillstore.io/skills/callstack-agent-device/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/callstack-agent-device?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/callstack-agent-device?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/callstack-agent-device/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/callstack-agent-device.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
callstack. (2026). agent-device security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/callstack-agent-device/audits/1Citation BibTeX
@techreport{callstack-callstack-agent-device-2026,
author = {callstack},
title = {agent-device security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/callstack-agent-device/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "agent-device security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "callstack"
date-released: "2026-09-30"
url: "https://skillstore.io/skills/callstack-agent-device/audits/1"
identifiers:
- type: other
value: "skillstore:callstack-agent-device:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Verify a Mobile App Flow
Navigate a test app, interact with current UI references, and verify an expected screen before closing the session.
Reproduce an Interface Issue
Repeat authorized navigation steps and inspect snapshots or supported screenshots to document the observed interface state.
Plan a TV App Check
Consult topic-specific help for TV controls, then plan app navigation and a named verification step on a configured target.
Essayez ces prompts
Open [test app] with agent-device on the configured target. Summarize its initial interactive snapshot, then close the session.
Open [test app], navigate to [screen] using current references, verify [expected text], then close the session.
In [test app], scroll until [selector] is visible, interact with it, and verify [expected state]. Preserve exact references and close the session.
Inspect [test app] on my configured test target. If accessibility data is unavailable, inspect a screenshot and use coordinates only as needed.
Bonnes pratiques
- Use authorized test targets and confirm the app scope before interacting with sensitive or consequential controls.
- Copy reference tokens exactly, including suffixes, and prefer current references or selectors over coordinates.
- Verify a named expectation after actions and close the session when the workflow finishes.
Éviter
- Do not reuse references from sparse or unavailable accessibility snapshots.
- Do not repeat bare scrolling when a selector-based scroll can locate the target.
- Do not treat interface changes as proof of success without checking the expected result.