templates
Skill0 starsChanged 52 days agoMITView on GitHub
ArcheFlow template gallery: save, share and initialise workflows, team presets, archetypes, domains and bundles.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- axomiyaindie/agent-skills-playbooktheir own version, first seen Nov 15, 2026
- georgemarmelstein/sistema-marmelsteintheir own version, first seen Nov 15, 2026
- runa-tic/palimpsesttheir own version, first seen Nov 8, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- razzant/ouroborostheir own version, first seen Oct 25, 2026
- sid-lakhani/agents-configtheir own version, first seen Oct 20, 2026
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- razzant/ouroboros★ 1.6ksame name
- butterbase-ai/butterbase-plugin★ 535same name
- butterbase-ai/butterbase-skills★ 535same name
- xenitV1/Antigravity-Workflows★ 130same name
- VoDaiLocz/kilo-kit-mcp★ 28same name
- georgemarmelstein/sistema-marmelstein★ 17same name
- coder/skills★ 14same name
- The-Utopia-Studio/skills★ 6same name
- SKB3002/agenthub★ 4same name
- wachterjohannes/symfony-skills★ 4same name
15 more not listed
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 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
- dagSkill
- domainsSkill
- git-integrationSkill
- initSkill
- memorySkill
- multi-projectSkill
- presenceSkill
- progressSkill
- replaySkill
- reportSkill
- reviewSkill
- runSkill
- scanSkill
- scoreSkill
- shadow-detectionSkill
- sprintSkill
- statusSkill
- using-archeflowSkill
- workflow-designSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
0
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
- Very specific: line 56
Check requires files exist
“Common” is measured: kept by at least 6 in 10 of the 18 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
Template Gallery -- Shareable ArcheFlow Configurations
Makes ArcheFlow setups portable and reusable across projects.
Template Storage
| Location | Scope | Precedence |
.archeflow/templates/ | Project-local | Higher (checked first) |
~/.archeflow/templates/ | Global (user-wide) | Lower (fallback) |
Subdirectories: workflows/, teams/, archetypes/, domains/, bundles/.
Bundles
A bundle is a complete setup (team + workflow + archetypes + domain) in one directory.
/archeflow:run reads .archeflow/config.yaml (budget, models, git, test_command, workflow:
= fast|standard|thorough) and custom roles; the team and workflow files are documentation of the
setup and are not read by the run.
Manifest (manifest.yaml):
name: my-backend-setup
description: "Backend feature work with a security lens"
domain: code
includes:
team: story-development.yaml
workflow: custom-workflow.yaml
archetypes: [custom-archetype.md]
domain: writing.yaml
requires: []
variables:
max_cycles: 2| Field | Required | Description |
name | Yes | Bundle identifier for archeflow-init.sh <name> |
description | Yes | Human-readable description |
includes | Yes | File types to filenames within bundle |
requires | No | Files that must exist in target project |
variables | No | Key-value defaults, overridable at init |
Operations
<archeflow-root>/lib/archeflow-init.sh <bundle-name> (what /archeflow:init runs)
- Find bundle (project-local, then global)
- Check
requiresfiles exist - Warn before overwriting existing
.archeflow/config - Copy files to
.archeflow/(teams/, workflows/, archetypes/, domains/) - Generate
.archeflow/config.yamlwith variables
<archeflow-root>/lib/archeflow-init.sh --from <project-path>
- Copy teams/, workflows/, archetypes/, domains/, config.yaml, hooks.yaml
- Skip run-specific data: events/, artifacts/, context/, templates/
<archeflow-root>/lib/archeflow-init.sh --save <name>
- Package current
.archeflow/into~/.archeflow/templates/bundles/<name>/ - Auto-generate manifest.yaml
<archeflow-root>/lib/archeflow-init.sh --list
- Show all bundles and individual templates (global + project-local)
Variable Substitution
Variables in manifests are stored in .archeflow/config.yaml after init. Substitution happens at run time, not template time.
Override at init: <archeflow-root>/lib/archeflow-init.sh backend-feature --set max_cycles=3
Individual Templates
Single files can be copied directly without a bundle:
~/.archeflow/templates/workflows/<name>.yaml~/.archeflow/templates/archetypes/<name>.md~/.archeflow/templates/teams/<name>.yaml
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.

