Skip to content
TrustedSkillsbeta
Back to all skills

Localstack Logs

Checked
localstack·vlatest·testing·Apache-2.0

This skill integrates with LocalStack to provide detailed logs from your event streams, simplifying debugging and troubleshooting of distributed applications.

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 localstack/skills --skill localstack-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

localstack

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 localstack/skills at 3526362740.

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

Scanned
1 file, 143 lines
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 provides access to LocalStack logs. It allows AI agents to retrieve and analyze log data generated by LocalStack, a fully managed open-source platform that reproduces AWS services locally. This enables debugging, monitoring, and auditing of applications interacting with LocalStack resources. The skill facilitates efficient troubleshooting and performance analysis within a local AWS environment.

When to use it

  • Debugging application errors: Retrieve logs related to specific function invocations or API calls in your LocalStack environment.
  • Monitoring resource usage: Analyze log data to identify trends in resource consumption (e.g., SQS queue size, DynamoDB table reads/writes).
  • Auditing security events: Examine logs for suspicious activity or unauthorized access attempts within your LocalStack setup.
  • Performance troubleshooting: Identify bottlenecks and optimize the performance of applications interacting with LocalStack services by analyzing request latency and error rates from logs.

Key capabilities

  • Access to LocalStack log data.
  • Retrieval of specific log entries based on criteria (e.g., timestamp, service).
  • Analysis of log data for debugging and monitoring purposes.

Example prompts

  • "Show me the logs for my SQS queue 'my-queue' from the last hour."
  • "What errors occurred in Lambda function 'my-function' during the past 5 minutes?"
  • "Retrieve all DynamoDB table access events from yesterday."

Tips & gotchas

  • Ensure LocalStack is properly configured and logging enabled for the desired services. The quality of logs directly impacts the usefulness of this skill.