Skip to content
TrustedSkillsbeta
Back to all skills

Uloop Get Logs

Checked
hatayama·vlatest·testing·MIT

Retrieves application logs from various sources using Uloop for troubleshooting and debugging issues quickly.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add hatayama/unity-cli-loop --skill uloop-get-logs -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

hatayama

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned hatayama/uloopmcp at 0c917acda0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0c917acda0
Manifest
.agents/skills/uloop-get-logs/SKILL.md
Scanned
2 files, 74 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, uloop-get-logs, retrieves logs from a ULoop system. It allows agents to access and analyze log data for troubleshooting or monitoring purposes. The retrieved information can be used to identify errors, track performance metrics, or understand system behavior.

When to use it

  • Troubleshooting application issues: When an application is experiencing problems, this skill can retrieve relevant logs to pinpoint the root cause.
  • Monitoring system health: Regularly fetching and analyzing logs helps proactively identify potential issues before they impact users.
  • Auditing user activity: Logs can be used to track user actions within a ULoop environment for security or compliance purposes.
  • Debugging automated processes: When automated workflows fail, the skill retrieves logs to help understand why the process did not complete successfully.

Key capabilities

  • Retrieves logs from a ULoop system.
  • Provides access to log data for analysis.
  • Supports troubleshooting and monitoring use cases.

Example prompts

  • "Get me the error logs from yesterday."
  • "Show me the logs related to user 'john.doe'."
  • "Retrieve all logs with a severity level of 'error' in the last hour."

Tips & gotchas

  • Requires access credentials and appropriate permissions within the ULoop system.
  • The volume of log data can be significant, so consider filtering by time or keywords to improve efficiency.