56 results available
Sign in
Skills directory

agent-device

callstackincubator

·

Last changed
Hardened

This skill has been hardened by Chainguard

Last changed

This version passed the hardening gate. Hardening applied 2 targeted changes and preserved all other text. Classified findings before hardening: 2. Classified findings closed: 1. Classified findings remaining: 1. Unclassified scanner findings remaining: 0. Review findings closed: 2. Review findings remaining: 9.


Open before hardening

1

Medium

1

Low
Open after hardening

1

Medium

Expand
File
Group
Subtype
Severity
Status
references/remote-tenancy.md

Sensitive Data & Secret Exposure

Data exfiltration

Medium
Open
references/remote-tenancy.md

Prompt Injection

Third-party content as instructions

Low
Closed

2 findings


SKILL.md

agent-device

Use this skill as a router with mandatory defaults. Read this file first. For normal device tasks, always load references/bootstrap-install.md and references/exploration.md before acting. Use bootstrap to confirm or establish deterministic setup. Use exploration for UI inspection, interaction, and verification once the app session is open.

Default operating rules

  • Start conservative. Prefer read-only inspection before mutating the UI.
  • Use plain snapshot when the task is to verify what text or structure is currently visible on screen.
  • Use snapshot -i only when you need interactive refs such as @e3 for a requested action or targeted query.
  • Avoid speculative mutations. You may take the smallest reversible UI action needed to unblock inspection, such as dismissing a popup, closing an alert, or clearing an unintended surface.
  • Do not browse the web or use external sources unless the user explicitly asks.
  • Re-snapshot after meaningful UI changes instead of reusing stale refs.
  • Prefer @ref or selector targeting over raw coordinates.
  • Ensure the correct target is pinned and an app session is open before interacting.
  • Keep the loop short: open -> inspect/act -> verify if needed -> close.

Default flow

  1. Load references/bootstrap-install.md and references/exploration.md before acting on a normal device task.
  2. Use bootstrap first to confirm or establish the correct target, app install, and open app session.
  3. Once the app session is open and stable, use exploration for inspection, interaction, and verification.
  4. Start with plain snapshot if the goal is to read or verify what is visible.
  5. Escalate to snapshot -i only if you need refs for interactive exploration or a requested action.
  6. Use get, is, or find before mutating the UI when a read-only command can answer the question.
  7. End by capturing proof if needed, then close.

QA modes

Required references

  • For every normal device task, after reading this file, load references/bootstrap-install.md first, then references/exploration.md, before acting.
  • Use bootstrap to confirm or establish deterministic setup, especially in sandbox or cloud environments.
  • Use exploration once the app session is open and stable.
  • Load additional references only when their scope is needed.

Decision rules

  • Use plain snapshot when you need to verify whether text is visible.
  • Use snapshot -i mainly for interactive exploration and choosing refs.
  • Use get, is, or find when they can answer the question without changing UI state.
  • Use fill to replace text.
  • Use type to append text.
  • When a task asks to "go back", use plain back for predictable app-owned navigation and reserve back --system for platform back gestures or button semantics.
  • Use type --delay-ms or fill --delay-ms for debounced search fields that drop characters when typed too quickly.
  • If there is no simulator, no app install, or no open app session yet, switch to bootstrap-install.md instead of improvising setup steps.
  • Use the smallest unblock action first when transient UI blocks inspection, but do not navigate, search, or enter new text just to make the UI reveal data unless the user asked for that interaction.
  • Do not use external lookups to compensate for missing on-screen data unless the user asked for them.
  • If the needed information is not exposed on screen, say that plainly instead of compensating with extra navigation, text entry, or web search.
  • Prefer @ref or selector targeting over raw coordinates.

Additional references

Install

Install with chainctl
chainctl skill install public/callstackincubator/agent-device:latest
Get started with chainctl
View source

Harden your own skills

Bring Chainguard's hardening pipeline to your first-party skills — custom rulesets, automated remediation, full audit trail.

Provenance

Upstream sourcehttps://github.com/callstackincubator/agent-skills
Upstream commit23643af0f725b83f2e3bfdb2c2f55bcca6d10e00
OCI reference

skills.cgr.dev/public/github.com/callstackincubator/plugins/vendored/.agents/skills/agent-device:latest

License

MIT

Files

HARDENING.md

LICENSE

SKILL.md

references/bootstrap-install.md

references/coordinate-system.md

references/debugging.md

references/exploration.md

references/macos-desktop.md

references/remote-tenancy.md

references/verification.md


The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.