Tags: edwinhu/workflows
Tags
docs(marimo): say how to install marimo-pair, and why it is not a dep… …endency The marimo skill now routes live-kernel work to an upstream plugin that ships separately, so both the skill and the README carry its two install commands. Not declared in plugin.json dependencies on purpose: a dependency that is not installed stops the whole plugin from loading — observed today when exactly that disabled a sibling plugin — and one skill of sixty-one must not be able to take the other sixty down. Notebook authoring works without marimo-pair. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dz5okvbURhd2bMhw8Jpqp6
feat(marimo): consume marimo-pair as a plugin instead of vendoring it The submodule pinned upstream at an April commit. Upstream is now v0.0.18, has restructured into a plugin, rewritten its discovery/execution scripts (WSL fix) and added a retro-marimo-pair skill. Vendoring it froze all of that. skills/marimo also inlined marimo-pair's CLI, and those examples were already broken against v0.0.18: --url is now required and stdin needs an explicit `-`, so each one exits on a usage error. The mechanics now route to Skill(skill="marimo-pair:marimo-pair"), which owns its own surface. Our own doctrine stays — pixi/uv/uvx plus --watch, background-task not --headless, tailnet binding over SSH forwarding, re-run EVERY cell after a data-only change, and the ctx.screenshot() coroutine caveat. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dz5okvbURhd2bMhw8Jpqp6
fix(librarian): drop the MCP tool its own skill forbids
The dotfiles copy of this agent had drifted ahead by one substantive change:
it no longer declares mcp__consensus__search. The consensus skill says NEVER to
use that tool — the MCP caps results at 3 where the CLI does not — so the agent
here could reach a tool its skill bans. Taking that copy, keeping the
workflows:-namespaced Skill() calls, and anchoring two relative paths to
${CLAUDE_PLUGIN_ROOT}.
consensus, deep-research, google-scholar, nlm and readwise-chat now live here
only; identical copies were loading from a personal skills dir too.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dz5okvbURhd2bMhw8Jpqp6
feat: track the tuicr skill here, as one copy skills/tuicr was a symlink to /home/eh/dotfiles/.claude/skills/tuicr — git stores that as a mode-120000 link holding an absolute path, so committing it would have published a path that resolves on exactly one machine. The 6 real files are tracked instead and the dotfiles original is removed, leaving one copy, consistent with the rest of the spine. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dz5okvbURhd2bMhw8Jpqp6
release: v6.1.0 — one copy of the spine, and two skills stop paying t… …heir body Loads as workflows@skills-dir from ~/.claude/skills/workflows; the seven duplicates in dotfiles are gone. An installed plugin outranks a skills-dir one even when disabled, so workflows@edwinhu-plugins was uninstalled (the marketplace stays registered). The repo's own ~/.claude/skills/<skill> paths dangled once the per-skill symlinks went, and are repointed. docx-typst and docx-repair move their procedure into references/ behind a routing index: on-invoke ~13.2k -> ~3.0k and ~14.5k -> ~2.8k, ~21.9k saved per invocation, with every original code block verified present. Ten descriptions lose prose but not triggers — all 158 quoted phrases preserved, always-on ~9,612 -> ~9,430. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dz5okvbURhd2bMhw8Jpqp6
workflows v6.0.1 The three published descriptions now describe the craft loop instead of the retired beat spine. Documentation only; no executable change from v6.0.0. Full detail in CHANGELOG.md [6.0.1].
workflows v6.0.0 — the craft spine replaces the beat spine BREAKING. The beat/episode architecture is retired: work + beat-* expanded into 63 skill directories is replaced by craft, one loop whose authority is the approved plan's craft:dispatch spec hash. Domain workflows (dev, ds, writing, workshop, workflow-creator) contribute mechanical checks and review lenses, not their own lifecycle. farm-out ships alongside, so the plugin dispatches without an outside install. Retired capabilities: phase-gate-evaluator, approved-artifact-policy, workflow-policy-loader, beat-implement-runner, beat-spine-runner, beat-spine-args, plan-review-composer, tasklist-reconciler. Published in their place: craft-spine-runner. There is no shim — see docs/extension-contracts.md. Full detail in CHANGELOG.md [6.0.0].
PreviousNext