Linkedin Video Creator

LinkedIn video creator that produces professional business videos through AI chat. Create thought leadership clips, company updates, product announcements, t...

Security Scan

The skill's declared purpose (creating LinkedIn-style videos) aligns with the single required credential (NEMO_TOKEN) and the instruction-only design, but there is a minor metadata inconsistency you should confirm before installing.

Purpose & Capability

The name/description (LinkedIn video creation) match the declared needs: a single service token (NEMO_TOKEN) and an apiDomain pointing to nemovideo. There are no unrelated environment variables or unexpected binaries requested.

Instruction Scope

SKILL.md is instruction-only and does not instruct the agent to read arbitrary system files or call unrelated endpoints. However the SKILL.md metadata lists a config path (~/.config/nemovideo/) which implies the skill may read local configuration files; the registry metadata shown elsewhere listed no required config paths — this mismatch should be clarified.

Install Mechanism

No install spec and no code files are present; the skill is instruction-only so nothing is being downloaded or written by the skill bundle itself.

Credentials

Only NEMO_TOKEN is required and set as the primary credential, which is proportional to a third‑party video API. The potential access to ~/.config/nemovideo/ (declared in SKILL.md metadata) could expose additional local tokens or settings — verify whether the skill actually reads that path and why.

Persistence & Privilege

The skill does not request always: true and does not declare modifications to other skills or system-wide settings. Autonomous invocation is allowed (default) but that is the platform norm.

Assessment

This skill appears to be what it says: a connector to a Nemovideo API that needs a single NEMO_TOKEN. Before installing, confirm: (1) the NEMO_TOKEN is from a trusted Nemovideo account and you understand its scope; (2) whether the skill will read ~/.config/nemovideo/ (SKILL.md metadata lists it) and what data lives there; and (3) that apiDomain (mega-api-prod.nemovideo.ai) matches the vendor you expect. If you don't trust the source or can't confirm the config-path usage, avoid providing your token or run the skill in an isolated environment. If you want higher assurance, ask the publisher for documentation or verify the linked repository/homepage for matching code and release artifacts.

Loading…