trae-agent

PassAudited by ClawScan on May 7, 2026.

Overview

This instruction-only code-agent skill is coherent for repository analysis and editing, but it can guide an agent to index code, change files, and run project commands, so use it in trusted or sandboxed repositories with review.

Before installing, confirm you want an agent that can analyze whole repositories, edit multiple files, and run validation commands. Use git, review all diffs, avoid untrusted repositories unless sandboxed, and exclude secrets or private data from any repository indexing.

Findings (4)

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

If used on the wrong repository or with an overly broad request, the agent could make unwanted code changes or remove files.

Why it was flagged

The skill is explicitly designed to modify and potentially delete repository files. This is expected for a repository code agent, but it is still mutation authority that should be user-directed and reviewed.

Skill content
Multi-file editing | Edit multiple files in one operation ... 4. **Delete** - Remove code safely
Recommendation

Use version control, review diffs before accepting changes, and ask the agent to confirm before broad refactors or deletions.

What this means

Running tests or lint scripts in an untrusted repository could execute code from that repository on the user's machine.

Why it was flagged

The example validation flow runs project commands. That is normal for software validation, but npm scripts can execute arbitrary local project code.

Skill content
command: 'npm run lint' ... command: 'npm test'
Recommendation

Run validation in a sandbox or container when working with untrusted code, and review package scripts before execution.

What this means

Sensitive files accidentally included in the repository could be indexed and reused in later context for the task.

Why it was flagged

The example describes repository indexing with embeddings and stored code metadata. This is aligned with repository search, but it may capture private code or secrets if the repository is not scoped or cleaned.

Skill content
const embeddings = await this.indexer.generateEmbeddings(file, symbols); ... await this.indexer.store(file, { ast, symbols, embeddings });
Recommendation

Exclude secrets, build artifacts, and private data from the repository index, and clear any generated index when finished if retention is not desired.

What this means

Users have less external context for who maintains the skill or where its instructions came from.

Why it was flagged

The skill has limited provenance information, although it does not include executable install code or dependencies.

Skill content
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill.
Recommendation

Treat it as an unverified instruction-only skill and review its behavior in a small repository before relying on it for important code changes.