Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Pipeline
v1.4.0Launch automated multi-skill pipeline that chains skills into a loop. Use when user says "run pipeline", "automate research to PRD", "full pipeline", "resear...
⭐ 0· 609·0 current·0 all-time
byRust@fortunto2
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description state the pipeline behavior and the SKILL.md instructs exactly how to chain and invoke other skills. No unexpected environment variables, binaries, or external services are requested, so the declared capability matches the requested resources.
Instruction Scope
The instructions tell the agent to invoke other skills (e.g., /research, /validate, /scaffold) and to read/write per-project state and log files under .solo/pipelines and optionally ~/.solo. That file I/O and the launcher/tmux behavior are consistent with managing a pipeline, but the skill metadata did not list any required config paths even though the runtime expects filesystem state files. The SKILL.md also recommends deleting those files to cancel. Confirm you are comfortable with the skill creating/reading/writing files in your project/home before use.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is low-risk from an install perspective because nothing will be downloaded or written by an installer.
Credentials
The skill requests no credentials or environment variables. It uses $ARGUMENTS (a runtime argument source) and standard filesystem paths; that access is proportional to a pipeline manager's needs. No SECRET/TOKEN/PASSWORDs are requested.
Persistence & Privilege
always is false and the skill does not request elevated platform privileges. It relies on the platform's Stop hook and can autonomously invoke other skills (model invocation is enabled by default). Autonomous chaining is expected for a pipeline skill, but that capability means it can trigger any skill it references — ensure the skills it will call are trusted.
Assessment
This skill appears to do what it claims (chain other skills and keep lightweight state/log files). Before installing or running it: 1) confirm you trust the downstream skills it will invoke (they may perform network access, write files, or use credentials); 2) be aware it will create/read/write .solo/pipelines/*.local.md and .solo/pipelines/*.log in your project or home directory (the metadata did not declare those config paths — expect file I/O); 3) it can run autonomously to chain stages, so always use the explicit confirmation step it requires and verify what it will do when asked; 4) to cancel a run, delete the state file named solo-pipeline-{project}.local.md; and 5) if you do not want terminal dashboards, use the recommended --no-dashboard flag or run only via the platform UI. If you want additional assurance, ask the author for a list of exact skill names this pipeline will invoke and inspect those skills for safety before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97bx275aakk9xm5rk61v5vzs981kcab
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔄 Clawdis