voip-manager

Manage VoIP calls

Security Scan

The SKILL.md asks the agent to run a local Python script and to use a VOIP_API_KEY, but the package contains no code and the registry metadata declares no required credentials — an incoherent and potentially risky mismatch.

Purpose & Capability

The name/description (manage VoIP calls) plausibly requires a VOIP API key and code to call an external service, but the registry metadata lists no required env vars, no code files, and no homepage/source. SKILL.md references a local script (scripts/voip_manager.py) that is not present in the package — this is inconsistent and disproportionate.

Instruction Scope

Runtime instructions tell the agent to run `python3 scripts/voip_manager.py` and to export VOIP_API_KEY, but there is no scripts/voip_manager.py included and the env var is not declared in the metadata. The instructions are vague (no target service, no endpoints, no auth scope) and would require the agent to access an undeclared credential, making the runtime behavior unclear and potentially unsafe.

Install Mechanism

This is an instruction-only skill with no install spec and no downloads or extracted archives, so there is no install-time code being written to disk by the skill itself. That reduces install risk, but it also means the skill as-published is incomplete (missing code).

Credentials

SKILL.md instructs users to set VOIP_API_KEY, yet the registry lists no required environment variables or primary credential. Requesting a generic API key for an unspecified service is disproportionate without documentation about which service, what scopes/permissions the key needs, and how the key will be used or stored.

Persistence & Privilege

The skill does not request persistent presence (always: false), is user-invocable, and declares no config paths or special privileges. There is no indication it would modify agent/system-wide settings.

What to consider before installing

Do not install or enable this skill until the publisher provides missing artifacts and clarifications. Specifically: request the actual scripts (e.g., scripts/voip_manager.py) and readable source code; ask the author to declare VOIP_API_KEY in the registry metadata and to document which VoIP service and API the key is for and what minimum permissions it requires; confirm there are no external downloads or third-party hosts the skill will contact; review the code for network destinations and data handling (look for unexpected endpoints or credential transmission); if you must test, run it in a sandboxed environment and use a throwaway API key with minimal permissions. If the publisher cannot provide source, a homepage, or a clear explanation of the required credential, treat the package as incomplete and avoid handing over real credentials.

Manage VoIP calls

When to Use

• User needs voice related functionality
• Automating voip tasks
• Communication operations

Usage

python3 scripts/voip_manager.py --input <input> --output <output>

Configuration

Set required environment variables:

export VOIP_API_KEY="your-api-key"

Output

Returns JSON with results:

{
  "success": true,
  "data": {}
}