Templates new

Templates let you reuse, share and adapt project workflows for Ellf. They’re typically a repo or directory containing the project setup and overview of plans, tasks, actions, agents and services to create, as well as the required assets and custom recipe code.

The ellf-template module makes it easy to import and export templates – just point it at a directory or repo link and let Ellf do the rest. If decisions or resources are needed to adapt the template to your use case, your coding agent will ask follow-up questions.

✳︎Claude Code: Importing a project template from GitHub
› /ellf-template

Set up this project using the sample data: https://github.com/explosion/ellf-templates/tree/main/github-docs-issues

Template directory

Click on a template to view more details and the files, or copy-paste the URL to import it via your coding assistant. You can also ask it to adapt the template to your use case or different data. Alternatively, the template documents all commands to set up the project manually if you prefer. To contribute a template you’ve built, get in touch!

Only use templates from trusted sources and review them before giving your coding agent access to run code and populate your Ellf account on your behalf.

Read more

Templates Repo

Collection of open-source templates

Template Module

Import and export project templates

Creating custom templates

Using the ellf-template command, you can also export any project in your Ellf account as a template – for example, to make it easy to repeat end-to-end workflows or share them with others. The project will be documented in a consistent format that can later be imported automatically or manually.

Each template will have a README.md with an overview of the resources like tasks or actions that should be created, assets to upload to the cluster, including sample data to get started, and what needs to be provided or configured by the user when importing a template. During import, the agent will first consult this file.

✳︎Claude Code: Exporting a template for a project
› /ellf-template

Export my support tickets project as a template to this directory and include some sample data.

Example: Project template directory structure
📂 template
├─ 📄 README.md            # template overview and instructions
├─ 📂 assets               # optional assets and sample data
│  ├─ 📁 input             # input data, e.g. data to annotate
│  ├─ 📄 instructions.md   # annotation instructions
│  ├─ 📄 labels.json       # label schemes
│  └─ 📄 …                 # any other assets, e.g. patterns or configs
├─ 📁 config               # any configuration settings, e.g. for Prodigy
├─ 📂 plans                # project plans to create
│  └─ 📄 project_plan.md   # individual plan (with placeholders for links)
├─ 📂 recipes              # custom recipe packages used by project
│  └─ 📁 recipe_one        # individual standalone recipe package
└─ 📁 …                    # any other relevant resources, scripts etc.

Note on links in project plans

By default, Ellf will also include your project plans in the template. If the plan contains cross-reference links to resources in the platform, like assets or jobs, those will be replaced by a placeholder like @@Assets/Support Tickets@@ (instead of the original UUIDs, which might not be valid when re-using the template). When importing a template, Ellf will upload and set up all resources in the new project and then update the placeholders so the links work as expected.