Meta Research
PassAudited by ClawScan on May 1, 2026.
Overview
This is an instruction-only research workflow skill with disclosed file, web, and command capabilities that fit its purpose, but users should review commands, stored logs, and provenance before relying on it.
This skill appears safe to use for structured research assistance. Before installing or invoking it on important work, verify the source if needed, run it in the intended project directory, review any proposed shell commands or file edits, and require explicit human approval before releasing code, data, models, or papers publicly.
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.
You may not be able to easily verify where the skill came from or compare it to an upstream project.
The package has limited provenance information. This does not show malicious behavior, and the skill is instruction-only with no install script, but users have less source context to verify authorship.
Source: unknown; Homepage: none
Verify the publisher and source if provenance matters for your environment, especially before using it on sensitive research projects.
When invoked, the assistant may edit research files, run local commands, search the web, and manage task state as part of the workflow.
The skill declares broad local file, shell, web, and task-management tools. These are expected for literature search, experiment setup, and analysis, but they are still capabilities users should supervise.
allowed-tools: Read, Write, Edit, Glob, Grep, Bash, WebSearch, WebFetch, Task, TaskCreate, TaskUpdate, TaskList, AskUserQuestion
Use it in the intended project workspace and review proposed file edits, Bash commands, expensive experiments, or publication/release actions before approving them.
Research decisions, datasets, paper notes, and literature summaries may remain in project files and be reused later.
The workflow intentionally persists decisions, research artifacts, evidence maps, and reusable resources across explorations. This is purpose-aligned, but persistent notes can retain sensitive or incorrect context.
Logbox tracking: maintain a running log of milestones ... Failed explorations stay in place ... Shared resources ... shared/literature/
Avoid putting private, identifiable, embargoed, or confidential material into shared logs unless that is intended, and periodically review archived/shared artifacts for stale or sensitive content.