Skip to main content
Glama

skillporter_scan

Read-only

Run static security and supply-chain checks on a skill directory to detect secrets, prompt injection, risky code, and symlink escapes before deployment.

Instructions

[READ] Run static security and supply-chain checks on a skill directory (secrets, prompt injection, AST/JS/encoded analysis, symlink escapes).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "skillporter_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesWorkspace-relative path to skill directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The [READ] tag is consistent with readOnlyHint=true, and the description goes beyond the annotation by listing the actual check categories performed, which tells the agent this is an analysis pass rather than a mutation. It stops short of saying whether findings are returned inline, whether anything is written to disk, or how results are ranked.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the read-only tag, then the action, then the enumerated checks. Nothing is redundant and no clause needs to be re-read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only tool this is nearly sufficient, but with no output schema the description should hint at what the agent receives back (findings list, severity, pass/fail) so the agent knows how to consume the result. That gap is the main omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single path parameter is already documented as a workspace-relative skill directory path. The description's phrase 'skill directory' reinforces but does not extend the schema with formatting rules, path constraints, or error behavior, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition names a specific verb (run static security and supply-chain checks) and resource (a skill directory), and the parenthetical enumerates the concrete analyses performed (secrets, prompt injection, AST/JS/encoded analysis, symlink escapes). It doesn't distinguish itself from potentially overlapping siblings like skillporter_diagnose, skillporter_detect, or skillporter_inspect, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scope of the scan implies when it is appropriate (before installing or importing a skill), but the description never states that explicitly, nor does it say when not to use it or which sibling to reach for instead. Usage is inferable rather than guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.