v1.0.0

Reef n8n Automation

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 5:38 AM.

Analysis

This instruction-only skill is coherently focused on building n8n workflows, but users should review imported templates and keep API credentials scoped.

GuidanceThis appears suitable for n8n workflow building. Before installing or using it, make sure the referenced template library is trusted, inspect any template before import, use scoped credentials, and manually test workflows before enabling scheduled, webhook, or production execution.

Findings (3)

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.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

SKILL.md

Build, customize, and deliver n8n workflows using our 2,061-template library. Reference: `~/projects/n8n-workflows/`

The skill relies on a large local template library that is not part of the submitted artifact. This is coherent with the stated purpose, but imported workflow templates should be reviewed before use.

User impactA workflow template could contain unexpected nodes, API calls, or field mappings if the local library is stale or untrusted.

RecommendationInspect selected template JSON before importing it into n8n, especially credentials, HTTP Request nodes, Code nodes, and activation settings.

Tool Misuse and Exploitation

SeverityMediumConfidenceHighStatusNote

SKILL.md

API call (no native node) | HTTP Request | Works with any REST API

The skill encourages use of n8n's generic HTTP Request capability. This is purpose-aligned, but it can perform broad actions against external APIs depending on configuration.

User impactA misconfigured workflow could send data to the wrong API endpoint or perform unintended changes in connected systems.

RecommendationReview HTTP methods, URLs, headers, payloads, and rate limits before running workflows with live credentials.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityMediumConfidenceHighStatusNote

SKILL.md

Update credentials (Client's API keys)

The skill explicitly expects workflows to be configured with client API keys. This is normal for n8n integrations, but those credentials can grant authority over third-party accounts.

User impactWorkflows built with real API keys may read or change data in connected client services.

RecommendationUse least-privilege credentials, avoid sharing secrets in prompts or output files, and confirm account-changing actions with the client before activating workflows.