Materials Cli

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill mostly matches its stated rendering and AI-generation purpose, but its AI path relies on an unreviewed local dependency and its Windows launcher may pass user input through a shell.

Install only if you trust the publisher and can verify the missing materials-agents dependency. Use a limited OpenAI key, avoid untrusted custom OpenAI base URLs, and be especially careful with prompt or file path strings on Windows until the shell launcher is fixed.

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.

What this means

Using generate may consume OpenAI credits and send the prompt/schema-generation request to OpenAI or a configured compatible endpoint.

Why it was flagged

The skill clearly discloses that AI generation needs an OpenAI credential; this is purpose-aligned but gives the tool authority to spend/use that account and send prompts to the configured provider.

Skill content
Uses `OPENAI_API_KEY` (and optionally `OPENAI_MODEL`, `OPENAI_BASE_URL`) if not passed via flags.
Recommendation

Use a limited OpenAI key where possible and only set OPENAI_BASE_URL to an endpoint you trust.

What this means

The generate command may depend on code that was not included in the review, and that code is involved in handling the prompt and OpenAI API key.

Why it was flagged

A core AI-generation dependency is a local sibling path rather than a pinned, included package, so its implementation and provenance are not reviewable from the provided artifacts.

Skill content
"materials-agents": "file:../materials-agents"
Recommendation

Require the dependency source to be included or pinned to a reviewed package/version before trusting the AI generation path.

What this means

On Windows, a crafted prompt or file path could potentially cause the CLI launcher to execute unintended shell behavior.

Why it was flagged

The launcher forwards all CLI arguments, including user-controlled prompts or paths, into a shell on Windows; shell metacharacters could be interpreted unexpectedly.

Skill content
const args = tsxLoader ? ['--import', tsxLoader, cliPath, ...process.argv.slice(2)] : [cliPath, ...process.argv.slice(2)]; const child = spawn(exec, args, { stdio: 'inherit', shell: process.platform === 'win32' });
Recommendation

Remove shell:true, or strictly escape/validate forwarded arguments; users should avoid running untrusted prompt/path strings with this CLI on Windows.