Tencent SkillHub · Developer Tools

Pipeline

Launch automated multi-skill pipeline that chains skills into a loop. Use when user says "run pipeline", "automate research to PRD", "full pipeline", "resear...

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Launch automated multi-skill pipeline that chains skills into a loop. Use when user says "run pipeline", "automate research to PRD", "full pipeline", "resear...

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.4.0

Provenance

Publisher: fortunto2
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 14 sections Open source page

/pipeline

Launch an automated multi-skill pipeline. The Stop hook chains skills automatically — no manual invocation needed between stages.

Research Pipeline

/pipeline research "AI therapist app" Chains: /research -> /validate Produces: research.md -> prd.md

Dev Pipeline

/pipeline dev "project-name" "stack" /pipeline dev "project-name" "stack" --feature "user onboarding" Chains: /scaffold -> /setup -> /plan -> /build Produces: full project with workflow, plan, and implementation

1. Parse Arguments

Extract from $ARGUMENTS: Pipeline type: first word (research or dev) Remaining args: passed to the launcher script If no arguments or unclear, ask: Which pipeline do you want to run? 1. Research Pipeline — /research → /validate (idea to PRD) 2. Dev Pipeline — /scaffold → /setup → /plan → /build (PRD to running code)

2. Confirm with User

Show what will happen: Pipeline: {type} Stages: {stage1} → {stage2} → ... Idea/Project: {name} This will run multiple skills automatically. Continue? Ask via AskUserQuestion.

3. Start First Stage

Run the first skill in the pipeline directly: For research pipeline: Run /research "idea name" For dev pipeline: Run /scaffold project-name stack The Stop hook (if configured) will handle subsequent stages automatically. Without a Stop hook, manually invoke each skill in sequence.

3b. Launcher Scripts (optional, Claude Code plugin only)

If you have the solo-factory plugin installed, launcher scripts provide tmux dashboard and logging: # Only available with Claude Code plugin — skip if not installed solo-research.sh "idea name" [--project name] solo-dev.sh "project-name" "stack" [--feature "desc"] Pass --no-dashboard when running from within a skill context.

5. Pipeline Completion

When all stages are done, output: <solo:done/> The Stop hook checks for this signal and cleans up the state file.

State File

Location: .solo/pipelines/solo-pipeline-{project}.local.md (project-local) or ~/.solo/pipelines/solo-pipeline-{project}.local.md (global fallback) Log file: .solo/pipelines/solo-pipeline-{project}.log Format: YAML frontmatter with stages list, project_root, and log_file fields. The Stop hook reads this file on every session exit attempt. To cancel a pipeline manually: delete the state file solo-pipeline-{project}.local.md

tmux Dashboard (terminal use)

When launched from terminal (without --no-dashboard), a tmux dashboard opens automatically with: Pane 0: work area Pane 1: tail -f on log file Pane 2: live status display (refreshes every 2s)

Manual Monitoring

Monitor pipeline progress with standard tools: # Watch log file tail -f .solo/pipelines/solo-pipeline-<project>.log # Check pipeline state # Auto-refresh watch -n2 -c solo-pipeline-status.sh Otherwise, use standard tools: # Log tail tail -f .solo/pipelines/solo-pipeline-<project>.log # Check state file cat .solo/pipelines/solo-pipeline-<project>.local.md

Session Reuse

Re-running a pipeline reuses any existing state — completed stages are skipped automatically. No need to close/recreate — just run the same command again

Log Format

Critical Rules

Always confirm before starting a pipeline. Don't skip stages — the hook handles progression. Cancel = delete state file — tell users this if they want to stop. Max iterations prevent infinite loops (default 5 for research, 15 for dev). Use --no-dashboard when running from within Claude Code skill context.

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

1 Docs

SKILL.md Primary doc