5 minutes
How to Save Workflows as Skills with Eigent
Turn a working Eigent thread, review rules, test commands, or release checklists into a reusable skill any teammate can invoke in future sessions.
What you need
- Eigent desktop app
- An existing working workflow, thread, or runbook to preserve
Best for
- Codified workflows you want Eigent to repeat without re-explaining each time
- Teams that want a reusable skill instead of pasting a long prompt into every session
- Standardizing processes like PR review, release notes, or incident response
Starter Prompt
Create a reusable Eigent skill that [fixes failing CI checks on a GitHub PR / turns PR notes into inline review comments / writes release notes from merged PRs]. Use these sources when creating the skill: - Working example: [say "use this thread," link a merged PR, or paste a good Eigent answer] - Source: [paste a Slack thread, PR review link, runbook URL, or docs URL] - Scripts or commands to reuse: [test command], [preview command], [release command] - Good output: [paste the final answer, changelog entry, or review comment you want future sessions to match]
How it works
- Identify the working workflow to preserve — a thread, checklist, runbook, script, or a good Eigent answer.
- Add the source material to the prompt — paste the Slack thread, link the docs page, or reference the script.
- Ask Eigent to create a named skill from the material, keeping the main instructions concise.
- Invoke the new skill on the next task and refine it with feedback from that run.
More prompts to try
- Turn the workflow we used in this thread into a skill I can reuse next sprint.
- Create a skill from our team's PR review checklist.
- Update this skill to also run the integration test suite before reporting results.
- What source material should I add to make this skill more reliable?
How to use
Stay in the Eigent thread that produced the workflow you want to preserve, or paste the runbook, Slack thread, or checklist you want to codify. Run the starter prompt with the source material filled in. Eigent creates a skill file with instructions, optional scripts, and reference documents. Use the skill in your next session and ask Eigent to update it if anything is missing or incorrect.
Expected output
A named skill with a SKILL.md instructions file, optional reference documents, and any scripts the skill should run. Skills in your global config are available from any repo; skills committed to the repo are available to all contributors.
Limitations
- Skills work best when they start from a working example — abstract descriptions without a concrete reference produce lower-quality skills.
- Very complex workflows may need to be split into two skills rather than crammed into one instruction file.
- Skills that depend on external tools (Slack, Linear, GitHub) need those integrations connected to work reliably.
Related workflows
Keep Documentation Up-to-Date
Use code changes and PR context to draft focused documentation updates — without broad rewrites or s…
Automate Bug Triage
Turn daily bug reports into a prioritized list — check alerts, issues, failed checks, and chat repor…
Review GitHub Pull Requests
Catch regressions, missing tests, and risky behavior changes before human review — automatically on …
