Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

artifact-organizer

v1.0.0

按任务阶段而不是按文件类型整理混合产物。当编码、写作、脚本处理、研究、自动化或多步骤任务产生多个文件,且文件开始散落、临时产物与最终产物混在一起、目录结构不清晰,或用户提出“整理目录”“整理工作区”“归类”“归档”“收整产物”“文件有点乱”“帮我理一理结构”时,使用此技能。既支持任务开始前先规划 staged 目...

0· 41·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description describe organizing task artifacts by workflow stage; the skill requires no binaries, env vars, or installs. All declared requirements match the stated purpose and nothing requested is extraneous.
Instruction Scope
SKILL.md gives only local directory-organizing guidance (create stage folders, move/rename files, recommend moving precise secrets into a local secrets/ area). It does not instruct contacting external endpoints or accessing unrelated system config. The guidance to identify/relocate sensitive files is expected for this task.
Install Mechanism
No install spec and no code files — instruction-only skills have minimal surface and nothing will be written to disk by an installer.
Credentials
The skill requests no environment variables, credentials, or config paths. Mentions of 'secrets/' are advisory and not a request for secret values or credentials from the environment.
Persistence & Privilege
always is false and the skill has no install or background components. It does not request persistent presence or modifications to other skills or system-wide settings.
Assessment
This is an instruction-only organizer and is coherent with its purpose, but consider: (1) the agent will examine files in the task workspace — if you have sensitive data you do not want scanned or moved, either exclude those paths or tell the agent explicitly; (2) moving secrets into a local secrets/ folder can break scripts that expect files in place — back up or run a dry-run before large moves; (3) confirm any destructive actions (deletions/renames) and prefer manual approval for changes that could affect runtime or deployments.

Like a lobster shell, security has layers — review code before you run it.

latestvk97333mwazmkmj9k4kw8818hz983txme

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments