dag
Skill0 starsChanged 52 days agoMITView on GitHub
Show the event DAG (which agent ran, what it produced, which findings led to which fixes) of the current or last ArcheFlow run. <example>User: "/archeflow:dag"</example> <example>User: "/archeflow:dag 2026-04-06-jwt-auth"</example>
In this repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/archeflow.mdcCursor rule
- archeflow-reviewSkill
- archeflow-runSkill
- archeflow-sprintSkill
- act-phaseSkill
- autonomous-modeSkill
- check-phaseSkill
- cost-trackingSkill
- custom-archetypesSkill
- domainsSkill
- git-integrationSkill
- initSkill
- memorySkill
- multi-projectSkill
- presenceSkill
- progressSkill
- replaySkill
- reportSkill
- reviewSkill
- runSkill
- scanSkill
- scoreSkill
- shadow-detectionSkill
- sprintSkill
- statusSkill
- templatesSkill
- using-archeflowSkill
- workflow-designSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Run ID: the argument, else the newest .archeflow/events/*.jsonl (ignore index.jsonl).
- Very specific: line 12
Run <archeflow-root>/lib/archeflow-dag.sh .archeflow/events/<run_id>.jsonl --no-color and show its output unchanged.
- Very specific: line 13
No event file for the ID: say "No events found for run <run_id>."
≈ “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
ArcheFlow Run DAG
- Run ID: the argument, else the newest
.archeflow/events/*.jsonl(ignoreindex.jsonl). Only accept IDs made of letters, digits,.,_,-. - Run
<archeflow-root>/lib/archeflow-dag.sh .archeflow/events/<run_id>.jsonl --no-colorand show its output unchanged. - No event file for the ID: say "No events found for run
<run_id>."
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.