Skip to content
TrustedSkillsbeta
Back to all skills

Build Review Interface

Checked
hamelsmu·vlatest·backend·MIT

Helps with building, code review as part of agent workflows workflows.

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 hamelsmu/evals-skills --skill build-review-interface -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

hamelsmu

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 hamelsmu/evals-skills at 22418da2bf.

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

Commit
22418da2bf
Manifest
skills/build-review-interface/SKILL.md
Scanned
1 file, 95 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

build-review-interface

What it does

This skill provides a dedicated interface for reviewing build processes, allowing AI agents to inspect compilation status and artifact generation. It streamlines the verification of code builds within development workflows.

When to use it

  • Verify that a recent code commit compiled successfully without errors.
  • Inspect generated build artifacts before deploying to production environments.
  • Debug failed build pipelines by analyzing specific error logs.
  • Confirm dependency resolution and package installation during the build phase.

Key capabilities

  • Displays real-time build status indicators (success, failure, or in-progress).
  • Shows detailed error messages and stack traces for failed builds.
  • Lists generated artifacts and their file paths.
  • Provides access to raw build logs for deep analysis.

Example prompts

  • "Check the status of the last Jenkins build and summarize any errors."
  • "List all artifacts produced in the current Docker container build."
  • "Analyze the build log from the previous night's deployment attempt."

Tips & gotchas

Ensure your AI agent has read-only access to the build server or CI/CD logs before invoking this skill. If a build fails, always request the full stack trace rather than just the summary to identify root causes quickly.