v1.0.8

Skill Flow v1.0.8 Release Notes

Date: 2026-03-25
Version: v1.0.8

Summary

v1.0.8 is a reliability release for source import and managed cleanup.

This release removes low-signal duplicate warnings from skill-flow add, prevents failed imports from deleting existing checkouts, and hardens uninstall / prune / redeploy flows so cleanup stays inside recorded managed roots even after target paths change.

Highlights

1. add no longer shows duplicate mirror warnings

Generated mirror directories such as .agents/skills/* can legitimately contain the same content as canonical source/skills/* entries.

skill-flow add still de-duplicates those entries, but it no longer surfaces the repetitive warning spam when the generated mirror copy is skipped.

2. Failed imports no longer risk existing source checkouts

Source fetch now lands in a temporary checkout first and only moves into the managed source directory after the snapshot is validated.

This prevents failed add attempts from removing an already existing managed checkout path.

3. Managed cleanup is now root-safe

Uninstall, config bootstrap pruning, and deployment application now enforce two cleanup rules:

• never delete the managed root directory itself
• never delete paths outside the managed source or target root

This closes the main accidental-deletion paths when lock state or deployment paths are stale or corrupted.

4. Cleanup still works after target roots move

Deployment records now preserve the managed target root that was active when the deployment was created.

That means normal cleanup can still remove an existing deployment even if the user later changes SKILL_FLOW_TARGET_* to a different location.

User-visible Behavior Changes

Add flow

• duplicate generated-skill warnings are hidden from add output
• existing managed source checkouts are protected from failed import cleanup

Cleanup flows

• uninstall refuses to remove unmanaged paths
• config bootstrap prune skips unmanaged deployment paths instead of deleting them
• deployments created under an older target root can still be cleaned up later

Verification

Commands run:

npm run build
npm test

v1.0.7

Skill Flow v1.0.7 Release Notes

Date: 2026-03-24
Version: v1.0.7

Summary

v1.0.7 turns source installation into a guided flow instead of a one-shot command.

This release adds an interactive add experience with skill and agent selection, reuses the same install flow from find, and tightens config so selection state and layout stay stable in more real-world cases.

Highlights

1. skill-flow add is now a guided install flow

skill-flow add <source> no longer has to commit immediately with one default selection.

The new flow prepares the source first, then lets the user:

• review discovered skills
• filter and select which skills to enable
• filter and select which agent targets to project to
• see an installation summary before apply
• cancel and roll back the prepared source cleanly

Visible loading states were also added so slower source discovery and target detection are easier to understand.

2. Scripted installs can now preselect skills and agents

The CLI now supports:

• --skill <id>
• --agent <target>
• --yes
• --all

This makes it possible to drive the new add flow non-interactively while still using the same validation and projection path as the interactive UI.

3. find now installs through the same flow as add

Installing a result from skill-flow find <query> now opens the same add flow instead of using a separate install path.

This removes behavior drift between the two commands and gives find installs the same selection, summary, warning, and cancellation behavior as direct adds.

4. config now restores local-only selections correctly

skill-flow now persists selected skill IDs separately from enabled target bindings.

This fixes a real state problem: if a source keeps selected skills but currently has no enabled agents, config can still restore that selection accurately instead of treating it as empty.

5. config UI is quieter and more stable

The config interface was aligned with the add flow presentation:

• shared skill flow badge header
• dot-based selection markers
• clearer Select Agents and Select Skills labels
• local checkout path shown in metadata when available
• terminal resize now refreshes pane layout correctly
• low-signal top status text stays hidden by default

User-visible Behavior Changes

Add flow

• multi-skill and multi-agent selection is now built into skill-flow add
• Esc or q cancels the prepared install instead of leaving partial imported state behind
• ambiguous --skill selectors and unavailable --agent targets now fail before projection

Find flow

• installing from find now uses the same guided install flow as direct adds

Config UI

• sources with no enabled agents can still reopen with their selected skills intact
• the interface reacts correctly to terminal resize
• metadata includes local checkout path when available

Verification

Commands run:

npm run build
npm test

Result:

15 test files passing
137 tests passing

v1.0.6

Skill Flow v1.0.6 Release Notes

Date: 2026-03-23
Version: v1.0.6

Summary

v1.0.6 improves source import predictability and reduces noise in the config interface.

This release tightens add --path behavior, makes generated follow-up commands cleaner, and simplifies the top bar in skill-flow config so users only see information that affects current decisions.

Highlights

1. add --path behavior is now more predictable

skill-flow add now keeps requested path handling consistent across stored source state, default selection, and follow-up workflows.

This reduces ambiguity when importing a repository with a scoped subpath and makes later actions reuse the same path intent more reliably.

2. Scoped imports now explain partial default selection

When add uses a path that narrows the default selection instead of redefining the source itself, skill-flow now emits an explicit preselection warning.

This makes the result clearer:

• the source group is still imported as a full managed source
• the initial selected skills can still be scoped by the requested path

3. find follow-up commands are cleaner

Generated follow-up commands from find no longer include redundant --path . output for root-scoped skills.

This keeps the suggested command focused on meaningful arguments only.

4. config top bar is now quieter and more intentional

The top bar in skill-flow config was simplified to remove repeated action hints and low-signal steady-state labels.

New behavior:

• default steady state shows only Skill Flow
• Changes: N appears only when there are unsaved changes
• Status: ... appears only for active or failed operations
• the Skill Flow title remains visually stable instead of inheriting transient status colors

User-visible Behavior Changes

Add flow

• path-scoped imports are easier to reason about
• preselection warnings make partial default selections explicit
• generated follow-up commands are less noisy

Config UI

• top bar no longer repeats bottom action hints
• stable states no longer show Clean, Saved, or Updated
• only actionable or exceptional state remains visible

Verification

Commands run:

npm run build
npm test

Result:

12 test files passing
116 tests passing

v1.0.5

Changed

• Added skill-flow add <slug> --from clawhub support.
• Aligned CLI --version output with package.json.
• Clarified import-path behavior in the workflow documentation.

Fixed

• Fixed SSH GitHub locators like git@github.com:owner/repo.git being normalized into invalid HTTPS clone URLs.
• Fixed GitHub tree URL imports so --path is resolved relative to the tree location.
• Fixed repair-state reporting negative removed deployment counts when rebuilding state.

Verification

• npm run build
• npm test
• Real CLI smoke tests for:
  • npm run dev -- --version
  • npm run dev -- add find-skills-skill --from clawhub
  • npm run dev -- add https://github.com/JimLiu/baoyu-skills/tree/main/skills --path baoyu-translate

v1.0.4

Skill Flow v1.0.4 Release Notes

Date: 2026-03-22
Version: v1.0.4

Summary

v1.0.4 turns skill-flow into a unified ingestion and bootstrap workflow.

This release focuses on one practical problem: users already have skills spread across agent directories, but the old flow still treated add, config, update, and startup checks as separate concerns. v2.0.0 closes that gap.

Highlights

1. Local sources are now first-class

skill-flow now supports local sources explicitly instead of treating them like a Git-shaped special case.

New storage layout:

~/.skillflow/source/local/<source-id>/

This is also where unmanaged external skills are adopted when config detects them.

2. config now bootstraps on startup

Opening skill-flow config now does real startup work before entering the main UI:

detect targets
  -> scan known agent roots
  -> import unmanaged skills
  -> refresh inventory
  -> normalize bindings
  -> audit projections
  -> enter config UI

The UI renders immediately and shows a boot log while this work runs.

3. Existing agent skills can be adopted into managed state

If skill-flow sees unmanaged skills under known agent skills/ roots, it can import them into managed local storage.

Important rule:

• already-managed projections are skipped
• symlinked skills are recognized
• symlinks that already point into ~/.skillflow/source/* are treated as managed state and are not imported again

4. find no longer blocks before UI render

skill-flow find <query> now enters the UI first, then runs the search. This avoids the old "nothing is happening" delay during slower searches.

5. Update behavior is now deterministic

Each source now preserves its selection intent:

• all
• partial

This means when a source gains new skills during update, skill-flow can decide consistently whether those new skills should be auto-selected.

User-visible Behavior Changes

Group naming

Display labels now show source context directly:

• local: <name>@local
• git: <repo>@<owner>
• clawhub: <slug>@clawhub

These are display labels only. Stable source IDs remain persistence-oriented.

Config startup

You will now see visible boot progress before the normal config panes appear.

External skill adoption

Existing unmanaged skills can now appear in config after bootstrap, provided they are not already managed by the current state.

Real-state Validation Notes

This release was validated against a real user environment.

Observed result:

• bootstrap correctly detects already-managed symlinked agent skills
• those skills are skipped instead of being duplicated
• no false re-import occurred in the real ~/.skillflow state

Verification

Commands run:

npm run build
npm test

Result:

57/57 tests passing

Upgrade Notes

No manual migration command is required.

Recommended first run after upgrade:

skill-flow config

This allows the new bootstrap flow to reconcile current state, detect unmanaged external skills, and audit existing projections.

v1.0.3

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Full Changelog: v1.0.1...v1.0.2

v1.0.1

更新内容

• 优化项目描述和文档
• 重命名为 skill-flow
• 添加 npm 安装方式
• 精简 README 结构，突出核心价值

v1.0.0

Initial release of skill-flow.

Highlights:

• Rename project from skill-manager to skill-flow
• Standardize CLI name, state directory, and env vars to skill-flow / .skillflow / SKILL_FLOW_*
• Remove mistaken v1.3.2 release and republish as v1.0.0
• Verified with successful build and test run before publish