run-pipeline
Skill71 starsChanged 36 days agoMITView on GitHub
Run, resume, audit, or interpret the repository's two-stage equity-screening pipeline, including Stage-1 quick BUY lists, Stage-2 full reports, reuse, and failures.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- harness/harness-skillstheir own version, first seen Nov 1, 2026
- neurospin-projects/2026_bdrabczuk_champollion_mcptheir own version, first seen Nov 1, 2026
- ai-analyst-lab/ai-analysttheir own version, first seen Sep 10, 2026
- Duckz289/Pipeline-to-proposal-Plugin-STANDARDtheir own version, first seen Jul 27, 2026
- bohewu/agents_pipelinetheir own version, first seen Jul 11, 2026
- AlanSyue/my-skillstheir own version, first seen Feb 26, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- ai-analyst-lab/ai-analyst★ 304same name
- harness/harness-skills★ 134same name
- AlanSyue/my-skills★ 2same name
- Duckz289/Pipeline-to-proposal-Plugin-STANDARD★ 2same name
- bohewu/agents_pipeline★ 1same name
- neurospin-projects/2026_bdrabczuk_champollion_mcp★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-agentSkill
- analyze-tickerSkill
- diagnose-runSkill
- maintain-agent-metadataSkill
- run-testsSkill
- add-agentSkill
- analyze-tickerSkill
- diagnose-runSkill
- run-testsSkill
- validation-batchSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the relevant script paths first.
- Very specific: line 17
Verify state from the dated BUY list, full reports (no _quick suffix), stage summary, and any failure/timeout records in scratch/.
- Distinctive: line 26
Read the defaults from their owners, not copied values in guidance.
- Distinctive: line 31
When changing this workflow, inspect reuse, completeness, watchdog, failure, and marker paths together, then run focused pipeline tests and …
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run or interpret the screening pipeline
scripts/run_pipeline.sh owns the two stages: quick Stage 1 writes the dated
BUY list; full Stage 2 consumes it. Same-mode reuse means quick reports never
satisfy Stage 2, and reconciliation treats quick BUYs as non-investable.
- Read the relevant script paths first; confirm start stage, date, freshness, strictness, and forced reuse behavior.
- Report Stage-1 BUY-list count separately from Stage-2 attempted, reused,
completed, and failed work.
results/.pipeline_last_run.jsonrecords only the Stage-1 BUY-list count. - Verify state from the dated BUY list, full reports (no
_quicksuffix), stage summary, and any failure/timeout records inscratch/. - Require a current, publishable full report for a purchase. On interruption, state the verified status and resume the appropriate stage.
The per-ticker timeout settings feed scripts/pipeline_signals.sh, which passes an
absolute epoch deadline to the child. src/llm_runtime/run_deadline.py translates
it to a monotonic analysis deadline with a publication reserve; src/main.py
binds it around analysis rather than final rendering, persistence or shutdown.
Read the defaults from their owners, not copied values in guidance. Do not inject
an artificial pipeline deadline into a manual run. Distinguish budget admission
failure from watchdog signals and exit records; a truncated retry ladder is a
bounded-work diagnostic, not a promise of completion or evidence of provider failure.
When changing this workflow, inspect reuse, completeness, watchdog, failure, and marker paths together, then run focused pipeline tests and static checks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

