BugPack View Bug

View detailed bug context from BugPack including screenshots, environment info, and related files. Use when: user wants to see bug details, screenshots, or u...

Security Scan

The skill's instructions and requirements are coherent with its stated purpose (viewing bug details from a local BugPack service), with a small ambiguity about how 'relatedFiles' should be used to locate source code.

Purpose & Capability

Name/description align with the runtime instructions: it fetches bug details from BugPack via an HTTP GET to a localhost API and surfaces screenshots, env info, and related files. No unrelated credentials, binaries, or installs are requested.

Instruction Scope

Instructions limit network access to http://localhost:3456 and describe expected response fields. However the directive 'use [relatedFiles] to locate relevant source code' is ambiguous — it could imply reading local repository files or accessing other services, but the SKILL.md does not specify how to fetch file contents or which paths are allowed.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk during install.

Credentials

The skill requests no environment variables, credentials, or config paths; this is proportional to its described purpose of querying a local BugPack API.

Persistence & Privilege

Defaults are used (always: false, agent invocation allowed). The skill does not request permanent presence or special privileges.

Assessment

This skill is coherent for viewing bug details from a BugPack service running on your machine (http://localhost:3456). Before installing, confirm you want the agent to contact that local service and that the service is running on that port. Be aware that the instructions suggest using 'relatedFiles' to locate source code; although the skill does not explicitly instruct reading files, an agent with filesystem access could attempt to read repository files. If you do not want that, restrict the agent's file access or clarify the SKILL.md to specify allowed file paths or remove the automatic 'locate source' behavior. If you expect BugPack to be hosted elsewhere, update the endpoint in the instructions — contacting arbitrary external endpoints is not configured here.

BugPack - View Bug Details

Fetch full bug context from BugPack, including description, screenshots, environment info, and related files.

Instructions

1. Call GET http://localhost:3456/api/bugs/:id to get the full bug details.
2. The response includes:
   • title, description, status, priority
   • pagePath — the page/route where the bug occurs
   • device, browser — environment info
   • relatedFiles — array of file paths related to the bug
   • screenshots — array of screenshot objects with id, name, original_path, annotated_path
3. Display the bug info in a structured format.
4. If the bug has screenshots, mention them and offer to show annotated versions.
5. If relatedFiles are listed, use them to locate relevant source code.

Example

GET http://localhost:3456/api/bugs/abc-123

Response:

{
  "ok": true,
  "data": {
    "id": "abc-123",
    "title": "Button click not working",
    "description": "The submit button on the login page does not respond to clicks",
    "status": "open",
    "priority": "high",
    "pagePath": "/login",
    "device": "Desktop",
    "browser": "Chrome 120",
    "relatedFiles": ["src/pages/Login.tsx", "src/components/SubmitButton.tsx"],
    "screenshots": [
      {
        "id": "ss-001",
        "name": "login-bug.png",
        "original_path": "/uploads/MyProject/original.png",
        "annotated_path": "/uploads/MyProject/annotated.png"
      }
    ]
  }
}