Skip to main content
Agent skill

Grokbot Pipeline

Operator-run pump.fun screening pipeline ported to src/pumpgrok/engine (retired oracle pin in docs/VENDORPIN.md). Produces dry-run trade evidence (nine-stage pipeline, four Grok agents, JSONL log, replay tooling) that feeds all eight desk roles via pumpgrok scout pipeline (JSON plus PIPELINE-EVIDENCE). Never enables live trading.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Grokbot Pipeline when an AI agent needs a reusable SKILL.md workflow for this job: Operator-run pump.fun screening pipeline ported to src/pumpgrok/engine (retired oracle pin in docs/VENDORPIN.md). Produces dry-run trade evidence (nine-stage pipeline, four Grok agents, JSONL log, replay tooling) that feeds all eight desk roles via pumpgrok scout pipeline (JSON plus PIPELINE-EVIDENCE). Never enables live trading.

When not to use it

Skip Grokbot Pipeline when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/grokbot-pipeline
# Save SKILL.md to ~/.claude/skills/grokbot-pipeline/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/grokbot-pipeline/SKILL.md. For a shared project, commit the folder at .claude/skills/grokbot-pipeline/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Grokbot Pipeline skill for this task: Use Grokbot Pipeline when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
56/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokinferred

    The skill text mentions Grok or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# GrokBot Pipeline

## L1 - Summary The pump.fun screening pipeline that turns a firehose of new launches into pre-screened, scored, evidence-backed candidates. It runs dry-run only with real market prices; its verdicts enter the ticket flow as evidence, never as authorization. The oracle tree is retired: the ported engine lives at `src/pumpgrok/engine/` (provenance in `docs/VENDOR_PIN.md`, license at `src/pumpgrok/engine/LICENSE-grokbot-pumpfun`).

## L2 - Method 1. Component location and provenance: the ported engine lives at `src/pumpgrok/engine/` (monitor, analyzer, scoring, reputation, exits, watcher, agents, pipeline, tune). The desk reaches it through `pumpgrok scout pipeline`; nothing imports the retired oracle. 2. Execution is paper only: the desk runs in `paper` mode and the live path refuses with exit 3. The retired `mode: live` stub raised `NotImplementedError`; the desk never used it and never will. 3. One-time setup (host or operator): `uv sync` at the repository root. No separate virtualenv, no `requirements.txt`, no `config.yaml` copy: the ported engine reads `src/pumpgrok/config/overlays/` plus `PUMPGROK_*` env. Secrets boundary: `GROKBOT_*` and `PUMPGROK_*` secrets stay in the operator environment and are never written into the journal, briefs, proposals, `desk.md`, or any repository file. 4. Run the screen (paper only): ```bash pumpgrok scout pipeline --candidates --limit 5 pumpgrok report --daily ``` Candidate evidence enters the ticket flow through `pumpgrok scout pipeline --candidates` (JSON plus PIPELINE-EVIDENCE). Scores are prior only, never clearance. 5. Desk bridge (from the repository root): ```bash pumpgrok scout pipeline --candidates --limit 5 ``` Archived vendor logs stay readable through the `ledger/export.py` cursor (`trades.jsonl`); there is no `--log` flag on the port verb. Missing nested objects become `unavailable`; never invent scores. A missing log fails closed. 6. Stage-to-role mapping: SCOUT prefers `buy` records as the candidate pool (score is not clearance); RISK treats analyzer, audit, and checker output as additional evidence for its live checks (checker `approve: false` is counter-evidence, not a KILL substitute); WHALE uses metrics as prior with live holder checks still required; SHILL uses narrative output as prior; CHIEF uses timing and total score for queue priority but ingest never creates tickets; RUG uses `close.reason` as watch context; EXIT studies `close.reason` distributions; SNIPER ignores pipeline `tx_hash` and sends only after RISK plus exact human approval.

## Failure modes - Engine cannot start: report the concrete failure and continue manual scouting with `BLIND` evidence standards. - Failed or empty run: report unavailable data, never a token endorsement. - High score or `approve: true`: not authorization and not CLEAR; the full RISK pass, CHIEF ticket, and human approval string are still required. - `tx_hash: dry_run` mistaken for a fill: it is dry-run evidence only.

## References - Bridge: `pumpgrok scout pipeline --candidates` (JSON plus PIPELINE-EVIDENCE block) - Desk report schema: PIPELINE-EVIDENCE block (token, log window, record type, analyzer, audit flags, narrative, checker, total score, desk action, sources) - Pin note and provenance: `docs/VENDOR_PIN.md`; oracle license: `src/pumpgrok/engine/LICENSE-grokbot-pumpfun`

Intended uses

  • Use Grokbot Pipeline when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.