parallel-worktrees

Skills · Install · Use · Evals

Skills

Click a card for details.

The manifest, services and bar widgets that work across several monitors, panels and the UI kit, IPC, settings, and what the plugin marketplace review asks for (no Qt text fields: text input goes through the bundled LineEdit.qml). It reads the installed sources first (/usr/share/omarchy/shell/) and treats them as the truth, so it keeps working as Omarchy changes.

SKILL.md · /plugin install omarchy-plugin@dan4a-skills

Comes with wt, a script that creates task worktrees, hands a task off to a new session (in Herdr) and removes worktrees once their branch is merged, including squash merges, from a Claude Code SessionEnd hook. In Herdr it also closes a merged child's idle session with its workspace, and the repo's workspace after its last worktree.

SKILL.md · /plugin install parallel-worktrees@dan4a-skills

Tabs in the current workspace with names of an emoji type and a short topic (💡 idea, 🔧 task, 🔍 research), a self-contained brief for each agent, follow-ups sent to a topic's existing tab, and a 2–3 line report back to the session that opened them. Outside Herdr it writes the briefs to paste instead.

SKILL.md · /plugin install herdr-tabs@dan4a-skills

What it is, a screenshot, install and use on the first screen; only what GitHub renders natively (tables as panels, alerts, <details>, Mermaid diagrams and xychart-beta charts built from the repo's data, <picture> for light and dark images); badges only for real state, no live third-party widgets; and a render check with gh api markdown before calling it done.

SKILL.md · /plugin install github-readme@dan4a-skills

Every skill here is tested this way, and this skill shares how: evals.json in skill-creator's format with checks that can be decided from the transcript and the end state, a sandbox.sh per skill (fake CLIs that log calls and remember what they created, bare git remotes, a home of its own), a bundled run-evals that runs each prompt with and without the skill in Claude Code, isolated from your settings, then grading and comparing the two.

SKILL.md · /plugin install skill-evals@dan4a-skills

Install

Any agent, with the skills CLI:

npx skills add dDan4a/agent-skills                         # pick from the list
npx skills add dDan4a/agent-skills --skill omarchy-plugin  # just this one

Claude Code, as a plugin marketplace:

/plugin marketplace add dDan4a/agent-skills
/plugin install omarchy-plugin@dan4a-skills
/plugin install parallel-worktrees@dan4a-skills
/plugin install herdr-tabs@dan4a-skills
/plugin install github-readme@dan4a-skills
/plugin install skill-evals@dan4a-skills

Update an installed plugin with claude plugin marketplace update dan4a-skills && claude plugin update <name>@dan4a-skills, then /reload-plugins.

By hand: copy skills/<name>/ into your agent's skills directory, for example ~/.claude/skills/, ~/.codex/skills/ or ~/.gemini/skills/.

Use

Ask for what you want; the agent loads the skill when it fits:

Make an Omarchy bar widget that shows my GitHub notifications, with a panel listing them.

Start a task in api to fix the login timeout, in its own worktree and session.

Three ideas, split them into tabs: SQLite or JSON for the plugin's history, what the AUR asks for now, and the typo in notes.

Make this README look nicer and add a chart of the benchmark.

Add evals to my commit-style skill and run them with and without it.

Evals

Share of checks passed per skill, Claude Opus 5.5, one run per eval (2026-10-17). Each skill has two bars drawn over each other: the full one is with the skill, the inner one without.

xychart-beta
  title "Checks passed, %: with the skill (back) and without (front)"
  x-axis ["omarchy-plugin", "parallel-worktrees", "herdr-tabs", "github-readme", "skill-evals"]
  y-axis "%" 0 --> 100
  bar [100, 100, 100, 100, 100]
  bar [56, 73, 21, 77, 76]

Every skill has evals in skills/<name>/evals/: evals.json (prompts and the checks a run must pass, in the skill-creator format) and sandbox.sh, which builds a throwaway home, repos or plugins for each prompt. skill-evals explains how to write them and ships the runner, which runs every prompt with and without the skill in Claude Code, isolated from your own settings and files:

MODEL=claude-opus-5-5 scripts/run-evals parallel-worktrees /tmp/evals/parallel-worktrees/iteration-1

(scripts/run-evals here is a shortcut for skills/skill-evals/scripts/run-evals skills/<name> ....) Then grade the runs against the expectations, as skill-evals describes.

License

MIT