Back to skill

Security audit

interview-question-kit

Security checks for vulnerabilities and agentic risk

Overview

The skill’s local interview-writing workflow is proportionate, but its simple checker cannot guarantee legal compliance.

Keep real candidate information out and have employment counsel review the questions before use. A clean lint report only means basic text checks passed. The optional Windows app is unnecessary for this workflow and requires a separate trust decision; its published hash does not establish safety.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The supplied script is a linter rather than an interview-kit builder. Its required-section checks only search for section-name substrings; they do not create or substantively validate those sections. Its banned-phrase checks partially support the declared unlawful-question flagging function, but are limited to fixed case-insensitive substring matches. Local input reading and report writing are ordinary supporting implementation details, and no unrelated resource access or hidden capability is evident.

Content

No source excerpt is available for this finding.

Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: file_write.

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.