Agent skill

Device Log

by blokadaorg in blokadaorg/blokada

A skill your agent uses for pulling recent Blokada app logs from a connected device, using the same share-log file exposed in Settings.

MPL-2.0Auto-check passedMobile

Install Device Log

skills CLI
$ npx skills add blokadaorg/blokada --skill device-log -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install blokadaorg/blokada device-log --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/blokadaorg/blokada.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/device-log .claude/skills/device-log && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
device-log
GitHub stars
3.3k
Token cost
~762 tokens
SKILL.md length
291 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MPL-2.0

At a glance

A skill your agent uses for pulling recent Blokada app logs from a connected device, using the same share-log file exposed in Settings.

  • Pulling recent Blokada app logs from a connected device
  • SKILL.md covers Default command, Behavior and Notes
  • Calls node
  • Using the same share-log file exposed in Settings

What it does

Device Log is an agent skill from blokadaorg/blokada. Use for pulling recent Blokada app logs from a connected device, using the same share-log file exposed in Settings. Trigger when Codex needs the most recent app log lines for debugging, wants logs from the last hour or today, or needs a manual operator workflow for recent device logs without going through Appium UI automation.

Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Mobile testing and debugging. It works with iOS and Android. The repository describes itself as: The official repo for Blokada apps. The licence is MPL-2.0.

When your agent uses it

  • Pulling recent Blokada app logs from a connected device
  • Using the same share-log file exposed in Settings
  • Codex needs the most recent app log lines for debugging
  • Wants logs from the last hour

Example prompts

  • “/device-log”

What it can do on your machine

Read from SKILL.md and the folder at commit 5279136. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Device Log loads about 762 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 291 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~762

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from blokadaorg/blokada at commit 5279136, republished under its MPL-2.0 licence (© blokadaorg). 291 words, ~762 tokens.

Download SKILL.mdSave it as .claude/skills/device-log/SKILL.md (or your agent's skills folder).
name
device-log
description
Use for pulling recent Blokada app logs from a connected device, using the same share-log file exposed in Settings. Trigger when Codex needs the most recent app log lines for debugging, wants logs from the last hour or today, or needs a manual operator workflow for recent device logs without going through Appium UI automation.

Device Log

Use this skill when the task is to read the recent Blokada shared app log or crash report from a connected device.

The current implementation supports iOS real devices only. Keep the skill name generic so Android can be added later without splitting the workflow again.

This skill reads the same share-log file exposed in Settings, then filters it on the host. It does not drive UI automation.

Default command

In Codex, request elevated access before running the command. The iOS device services are not reliably reachable from the sandbox.

Prefer the dedicated automation script:

bash
node automation/device/log.mjs

Optional overrides:

bash
WINDOW=today node automation/device/log.mjs
LINES=800 node automation/device/log.mjs
IOS_DEVICE_NAME="Example iPhone" node automation/device/log.mjs
APP_BUNDLE_ID=net.blocka.app.family node automation/device/log.mjs
ARTIFACT=crash node automation/device/log.mjs
ARTIFACT=crash APP_BUNDLE_ID=net.blocka.app.family node automation/device/log.mjs

Default behavior:

  • auto-selects the first connected device when no device selector is provided
  • reads the last hour of the shared app log
  • returns up to 400 lines after time filtering
  • saves artifacts under automation/device/output/

Supported variables:

  • ARTIFACT defaults to log, supports log or crash
  • IOS_DEVICE_NAME
  • IOS_UDID
  • APP_BUNDLE_ID defaults to net.blocka.app
  • WINDOW defaults to 1h, supports 1h or today
  • LINES defaults to 400

Behavior

  • ARTIFACT=log:
    • pulls the share-log file from the app group container group.net.blocka.app, under Library/Application Support/Blokada/ (devicectl on Xcode 26.5+ cannot list or copy files at the container root, only inside the standard Library/ hierarchy)
    • chooses the newest matching file for the selected bundle:
      • net.blocka.app -> blokada-i6x*.log
      • net.blocka.app.family -> blokada-iFx*.log
    • filters on the host for the last hour or today
    • applies LINES after time filtering
    • saves artifacts under automation/device/output/logs/
  • ARTIFACT=crash:
    • lists the systemCrashLogs domain
    • chooses the newest matching file for the selected bundle:
      • net.blocka.app -> Dev-*.ips
      • net.blocka.app.family -> FamilyDev-*.ips
    • saves artifacts under automation/device/output/crashlogs/

Notes

  • ARTIFACT=log reads the Settings share-log equivalent, not blokada.log.
  • ARTIFACT=crash is the post-mortem path when the app already terminated or Appium cannot stay attached.
  • If no matching share-log file exists, treat that as a tooling or app-state problem and report it clearly.

© blokadaorg, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/device-log of blokadaorg/blokada.

Open the folder on GitHubat commit 5279136

Compare with similar skills

Device Log next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Device Log compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Device Log this skillblokadaorg/blokada3.3k—~762Automated safety check: PassMPL-2.0
Mobilerun Docs Referencedroidrun/mobilerun9.6k—~943Automated safety check: PassMIT
Phoneagentrounak/PhoneAgent798—~2.2kAutomated safety check: PassMIT
Simvynpranshuchittora/simvyn437—~938Automated safety check: PassMIT
Mobile Automation with agent-devicenuclearpasta/react-native-drax714—~1.4kAutomated safety check: PassMIT
Screenmapaleqsio/screenmap239—~7.2kAutomated safety check: PassMIT

Similar skills

  • Mobilerun Docs Reference

    droidrun/mobilerun

    Answers questions about Mobilerun, the LLM-agent framework for automating Android and iOS devices, by pointing the agent to the right page of its v5 documentation.

    9.6k GitHub stars~943 tokensUpdated 2 days ago
    MobileAuto-check passed
  • Phoneagent

    rounak/PhoneAgent

    Control a connected iPhone, iOS simulator, Android emulator, or Android device from macOS through PhoneAgent's JSON-RPC bridge.

    798 GitHub stars~2.2k tokensUpdated 1 mo ago
    MobileAuto-check passed
  • Simvyn

    pranshuchittora/simvyn

    Operate iOS Simulators, Android Emulators, and connected mobile devices with Simvyn.

    437 GitHub stars~938 tokensUpdated 6 days ago
    MobileAuto-check passed
  • Mobile Automation with agent-device

    nuclearpasta/react-native-drax

    Drives iOS and Android devices and simulators from the command line: open apps, snapshot the UI tree, tap, type, scroll, take screenshots and read UI info.

    714 GitHub stars~1.4k tokensUpdated 3 days ago
    MobileAuto-check passed
  • Screenmap

    aleqsio/screenmap

    Generate a visual navigation map of an Expo / React Native or NativeScript app.

    239 GitHub stars~7.2k tokensUpdated 2 days ago
    MobileAuto-check passed
  • Simulator Audio E2E

    hyochan/react-native-nitro-sound

    Build and run repeatable react-native-nitro-sound recorder/player regression tests on an iOS Simulator or Android emulator, with explicit virtual-device selection, microphone permission, Maestro…

    961 GitHub stars~1.1k tokensUpdated 8 days ago
    MobileAuto-check passed

More from blokadaorg/blokada

  • Appium

    blokadaorg/blokada

    A skill your agent uses for dynamic inspection and navigation of the Blokada app through the repo-local Appium machine session.

    3.3k GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Dep Validate

    blokadaorg/blokada

    A skill your agent uses to validate risky dependency bumps end to end as a local or cloud-launched agent.

    3.3k GitHub stars~5.7k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Device Log

What does Device Log do?

A skill your agent uses for pulling recent Blokada app logs from a connected device, using the same share-log file exposed in Settings. Device Log is an agent skill from blokadaorg/blokada. Use for pulling recent Blokada app logs from a connected device, using the same share-log file exposed in Settings.

When should I use Device Log?

Device Log fits situations like: pulling recent Blokada app logs from a connected device; using the same share-log file exposed in Settings; Codex needs the most recent app log lines for debugging; wants logs from the last hour.

How do I install Device Log in Claude Code?

Run `npx skills add blokadaorg/blokada --skill device-log -a claude-code`. Or copy the skill folder (.agents/skills/device-log in blokadaorg/blokada) into .claude/skills/device-log in your project. Claude Code loads it when a task matches its description.

How do I install Device Log in Codex?

Run `npx skills add blokadaorg/blokada --skill device-log -a codex`. Or copy the skill folder (.agents/skills/device-log in blokadaorg/blokada) into .agents/skills/device-log in your project. Codex loads it when a task matches its description.

Can I use Device Log in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add blokadaorg/blokada --skill device-log -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/device-log, .gemini/skills/device-log, .github/skills/device-log and .opencode/skills/device-log in your project.

What does Device Log need to run?

Going by SKILL.md and its folder, Device Log needs the command-line tools its instructions call (node).

Does Device Log access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Device Log safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Device Log use?

Device Log is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Device Log use?

About 762 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Device Log?

Skills that share tags, products or a category with Device Log: Mobilerun Docs Reference (droidrun/mobilerun, 9.6k stars), Phoneagent (rounak/PhoneAgent, 798 stars), Simvyn (pranshuchittora/simvyn, 437 stars) and Mobile Automation with agent-device (nuclearpasta/react-native-drax, 714 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Device Log?

blokadaorg (a GitHub organization) maintains it in blokadaorg/blokada, which has 3,265 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: blokadaorg/blokada on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.