coware-skills
Security checks across malware telemetry and agentic risk
Overview
The skill’s shared-spec purpose is coherent, but its setup delegates broad authority to a remote guide and tells the agent to follow it without normal user review.
Install only if you trust Coware and the projects using .coware. Before first use, have the agent show you the fetched setup guide and proposed actions, review any .coware Node scripts before running them, and confirm which account, project, and invite code will be used.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
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.
A remote page could steer the agent through account, file, or project changes before the user has a chance to review the plan.
The skill makes a remote document authoritative and explicitly discourages normal user interruption or text-based clarification during setup.
Fetch the setup guide: `https://coware.team/llms.txt` ... Follow ALL instructions in the guide from start to finish ... Execute ALL steps in ONE go. Do NOT stop to ask the user questions mid-flow.
Require the agent to summarize the fetched setup guide and ask for explicit user approval before executing setup steps; do not let remote instructions override user-review expectations.
The actual setup steps users run may differ from what was reviewed in this skill package.
Important setup behavior is not included in the reviewed artifact and can change at the remote URL after publication.
The guide will walk you through: login, project creation/joining, file setup, and spec generation.
Package or pin setup instructions and scripts, declare required credentials and dependencies, and avoid relying on a mutable remote guide for privileged setup behavior.
In an untrusted repository, .coware scripts could do more than sync specs.
The skill directs the agent to execute project-local Node scripts. This is central to the sync workflow, but those scripts are not part of the provided artifact review.
Run: `node .coware/pull.mjs` ... If you created or modified any spec files, run: `node .coware/sync.mjs`
Use this only in trusted projects, review .coware/pull.mjs and .coware/sync.mjs before running them, and ask for approval before first execution.
The agent may authenticate to Coware, create or join projects, and use invite codes that grant shared project access.
The skill expects account login and project membership actions, which are purpose-aligned for Coware but affect workspace access.
The guide will walk you through: login, project creation/joining ... teammates install this skill and run `/coware` — their agent will automatically join the project and pull shared specs.
Verify the Coware project and invite code before joining, and use least-privilege accounts or tokens where possible.
Incorrect or manipulated shared specs could cause the agent to make matching code changes and propagate them to teammates.
Shared persistent Markdown specs are intentionally loaded into context and treated as authoritative for coding decisions.
Read ALL `.md` files in `.coware/specs/`. These specs are the source of truth ... Specs conflict with code: Specs win.
Review spec diffs, limit who can edit shared specs, and treat spec files as API-contract data rather than general instructions to the agent.