loongflow
Skill480 starsChanged 10 months agoApache-2.0View on GitHub
PEES (Plan-Execute-Evaluate-Summary) iterative problem-solving methodology with LoongFlow engine for complex tasks. Use when tasks need structured iteration, optimization, evolution, or when user mentions loongflow/PEES/PES.
- Reads credentials
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skill-creatorSkill
- code-analysisSkill
- file-processingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when the user wants to iteratively improve a solution — optimization, evolution, structured retries with learning, or any …
- Distinctive: line 12
Before starting, analyze the task and advise the user on which mode to use.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LoongFlow — PEES Iterative Problem Solving
Use this skill when the user wants to iteratively improve a solution — optimization, evolution, structured retries with learning, or any task that benefits from multiple rounds of refinement rather than a one-shot attempt.
Step 1: Analyze and Advise
Before starting, analyze the task and advise the user on which mode to use. Present both options clearly:
Native PEES (recommended for simple tasks):
- Best for: single-file fixes, small features, bug fixes, focused improvements
- How it works: You run Plan-Execute-Evaluate-Summary iterations yourself within this conversation
- Pros: Fast, no setup, no external dependencies, transparent workspace with full history
- Cons: Limited to ~5 iterations, single-threaded, no population-based evolution
LoongFlow Engine (recommended for complex tasks):
- Best for: optimization problems, multi-file projects, tasks needing many iterations (50+), population-based evolution with diversity preservation
- How it works: Downloads the LoongFlow framework, creates a
general_agenttask, runs evolutionary optimization in the background, monitors via cron - Pros: Powerful evolutionary engine with multi-island model, Boltzmann selection, MAP-Elites diversity, checkpointing, cost tracking
- Cons: Requires
ANTHROPIC_API_KEYandANTHROPIC_BASE_URL, setup time, runs as background process - Source: https://github.com/baidu-baige/LoongFlow
Ask the user which mode they prefer before proceeding.
Step 2: Follow the Mode Guide
Once the user chooses, read the corresponding reference file for detailed instructions:
- Native PEES → Read
references/native-pees.mdand follow it - LoongFlow Engine → Read
references/engine-mode.mdand follow it
Architecture Reference
LoongFlow supports three tiers for agent projects:
| Tier | Description | Best For |
| Simple | ReAct loop + persistent memory | Chatbots, tool calling, format conversion |
| Standard | ReAct + self-evaluation + iterative improvement | Code review, document generation, data analysis |
| Advanced | PEES evolution loop with loongflow-memory | Math optimization, algorithm design, NP-hard problems |
Complexity Assessment
Task Analysis
├── Only needs conversation + simple tools? → SIMPLE
├── Needs file operations or code generation?
│ ├── Has numerical evaluation metric? → ADVANCED
│ └── No numerical metric? → STANDARD
└── Needs iterative optimization?
├── Has clear scoring function? → ADVANCED
└── Qualitative improvement? → STANDARDDoes 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.

