Back to skill
v1.0.0

Satellite Comm

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 8:12 AM.

Analysis

This skill appears to collect career assessment details for a satellite communications learning roadmap, with no code, installs, credentials, or destructive actions shown.

GuidanceThis skill looks benign for its stated purpose. Before using it, review what career, education, skills, goals, user ID, or session information you include, and avoid sharing unnecessary sensitive personal details.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Insecure Inter-Agent Communication
SeverityLowConfidenceMediumStatusNote
openapi.json
"/api/satcom/roadmap": { "post": { ... "description": "Generate personalized satellite communication engineering roadmap" ... "requestBody": ... "#/components/schemas/RoadmapRequest" } }

The skill exposes an API endpoint that receives user-provided assessment data to generate a roadmap. This is aligned with the skill's purpose, but it means user profile/career information may be transmitted through the API interface.

User impactYou may share education, work history, skills, goals, session IDs, and possibly a user ID when asking for a roadmap.
RecommendationOnly provide information you are comfortable sending for roadmap generation, and avoid adding unnecessary personal or sensitive details.
Insecure Inter-Agent Communication
SeverityInfoConfidenceHighStatusNote
openapi.json
"RoadmapRequest": { "properties": { "assessmentData": ..., "sessionId": { "type": "string" }, "userId": { "anyOf": [{ "type": "integer" }, { "type": "null" }] }, "timestamp": { "type": "string" } } }

The request schema includes session and optional user identifiers. These fields are expected for an API workflow but are still metadata that can link roadmap requests to a user or session.

User impactRoadmap requests may be associated with a session and optional user identifier.
RecommendationUse non-sensitive session identifiers where possible and avoid submitting personally identifying values unless needed.