Releases: VintLin/skill-flow
Releases · VintLin/skill-flow
v1.3.9
RELEASE v1.3.9
Summary
v1.3.9improves Skill management in the macOS desktop app.- Compared with
v1.3.8, users can rename Skill groups, import supported links from the home page, and filter groups through a redesigned sidebar.
Highlights
1. Skill groups are easier to manage
- Skill groups can now be renamed from the desktop UI instead of always using the original repository name.
- Rename state is preserved across source refreshes and detail enrichment updates.
- Failure and empty-name states use localized desktop feedback.
2. Home import and filtering are more direct
- Supported import links pasted on the home page can hand off directly to import preview.
- GitHub and GitLab locator handling is more tolerant, including subgroup-style GitLab paths.
- The home sidebar now filters by status, source type, tags, agent applicability, and project scope.
3. Sidebar and titlebar polish
- Sidebar sections start collapsed, show one-line horizontal chips when collapsed, and wrap chips when expanded.
- The sidebar can fully collapse; when it is hidden, the home grid can use the reclaimed width.
- The macOS header is integrated into the sidebar area with clickable app controls and traffic-light alignment that survives window resize and full-screen transitions.
User-visible changes
- The Chinese status filter now uses
置顶instead of常用. - Only tag filter chips use
#; other sidebar options use plain labels. - The Skill Flow logo and title have more space from the macOS system buttons.
- Dev macOS packaging can reuse a matching bundled Node runtime instead of downloading it again.
Release Artifacts
skill-flow-1.3.9.tgzSkill-Flow-arm64.dmgSkill-Flow-arm64.zipSkill-Flow-x86_64.dmgSkill-Flow-x86_64.zipSkill-Flow-universal.dmgSkill-Flow-universal.zipsha256.txt
v1.3.8
RELEASE v1.3.8
Summary
v1.3.8fixes local import handling in the desktop app and tightens Hermes Agent presentation.- Compared with
v1.3.7, local skill folders are easier to import from pasted paths, and skill names in import cards now follow the metadata users maintain inSKILL.md.
Highlights
1. Local import paths are more tolerant
- The desktop import page now accepts local paths wrapped in single or double quotes.
- Paths with spaces can be pasted directly without triggering provider or selector errors.
- Local import preview and apply now use stable relative skill paths for nested skills, avoiding ambiguous selector failures.
2. Skill card names follow skill metadata
- Local import cards prefer
SKILL.mdfrontmatternamefor the visible skill name. - Fallback display names now follow the order:
SKILL.mdname, folder name,agents/openai.yamldisplay_name, then Markdown heading. - This avoids mixing English Markdown headings with localized skill names in the same local import set.
3. Hermes Agent desktop icon rendering is corrected
- Hermes Agent now renders through the same bundled icon path as other desktop agent icons.
- Group cards and target controls display the Hermes Agent icon consistently.
- Desktop icon coverage includes regression tests for Hermes Agent rendering.
User-visible changes
- Users can paste local skill folder paths such as
'/path/with spaces/skills'into the import page. - Local import cards show the intended
SKILL.mdskill names instead of falling back to mixed Markdown headings. - Hermes Agent target rows and cards show the expected icon.
- The CLI command surface and bridge protocol stay unchanged.
Release Artifacts
skill-flow-1.3.8.tgzSkill-Flow-arm64.dmgSkill-Flow-arm64.zipSkill-Flow-x86_64.dmgSkill-Flow-x86_64.zipSkill-Flow-universal.dmgSkill-Flow-universal.zipsha256.txt
v1.3.7
RELEASE v1.3.7
Summary
v1.3.7adds first-class Hermes Agent support to Skill Flow.- Compared with
v1.3.6, selected skills can now be deployed directly to Hermes Agent's writable skills directory instead of requiring a custom agent entry.
Highlights
1. Hermes Agent is now a built-in target
- Hermes Agent appears in the built-in target catalog with the label
Hermes Agent. - Skill Flow writes Hermes deployments to
~/.hermes/skills/, matching Hermes Agent's local skills source of truth. - The target can still be overridden with
SKILL_FLOW_TARGET_HERMES_AGENTwhen a different skills root is needed.
2. Desktop presentation is aligned
- The macOS desktop app now includes Hermes Agent in the default agent display order.
- Hermes Agent has a dedicated bundled icon, label, and short label in desktop target lists.
- Settings and target display flows treat Hermes Agent like the other built-in agents.
3. Hermes-oriented source layouts are detected
- Skill Flow now recognizes
.hermes/skillsinside source repositories when scanning for skill definitions. - This makes Hermes-ready repositories easier to import without moving files into a different agent-specific folder first.
User-visible changes
- Users can select Hermes Agent as a normal target when applying a skill group.
- Existing custom Hermes Agent entries are no longer necessary for the standard
~/.hermes/skills/setup. - The CLI command surface and bridge protocol stay unchanged.
- External Hermes skill directories remain a Hermes configuration feature; Skill Flow's built-in target writes to the local Hermes skills directory.
Release Artifacts
skill-flow-1.3.7.tgzSkill-Flow-arm64.dmgSkill-Flow-arm64.zipSkill-Flow-x86_64.dmgSkill-Flow-x86_64.zipSkill-Flow-universal.dmgSkill-Flow-universal.zipsha256.txt
v1.3.6
RELEASE v1.3.6
Summary
v1.3.6is a desktop packaging release focused on making Finder launch independent from shell-managed Node.js paths.- Compared with
v1.3.5, the macOS desktop app now bundles its own Node.js runtime for the bridge helper and tightens update feedback in desktop settings and project scope controls.
Highlights
1. Finder launch no longer depends on shell PATH
- Desktop release bundles now include Node.js
v22.22.2inside the app bundle. - The bridge helper uses the bundled runtime before falling back to system Node.
- This fixes the common
asdf/nvmcase where terminal launch works but double-click launch reports a missing Node.js dependency.
2. Release packaging validates the bundled runtime
- The macOS packager downloads official Node.js macOS runtime archives and verifies SHA256 before staging.
- Artifact validation now checks that every packaged app architecture has a matching bundled Node runtime.
3. External tool requirements stay explicit
gitremains required for non-GitHub Git sources.npxremains required for skills.sh imports; the bundled runtime is only for the desktop bridge helper.
4. Application Update behavior is clearer
- Update checks now use the GitHub Releases latest redirect instead of the GitHub API endpoint.
- The settings screen now distinguishes local builds that are newer than the latest published release.
- The app no longer runs a silent update check on startup; checks run when users press the update action.
5. Project scope refresh is explicit
- The macOS home scope switcher now includes a compact refresh action next to
Global. - Refreshing projects re-runs the desktop list query and applies the latest detected project scope state.
- The refresh action uses the same loading, success, and failure toast pattern as skill group updates.
User-visible changes
- Double-click launching Skill Flow on macOS works for users whose Node.js is installed through
asdfornvm. - Desktop packages are larger because they include Node.js runtime files.
- Application Update no longer reports an older GitHub release as the current app version when using a newer local build.
- Users can refresh the detected project list directly from the macOS home scope bar.
- The CLI command surface and bridge protocol stay unchanged.
Release Artifacts
skill-flow-1.3.6.tgzSkill-Flow-arm64.dmgSkill-Flow-arm64.zipSkill-Flow-x86_64.dmgSkill-Flow-x86_64.zipSkill-Flow-universal.dmgSkill-Flow-universal.zipsha256.txt
v1.3.5
RELEASE v1.3.5
Summary
v1.3.5is a patch release focused on repairing the npm publish path afterv1.3.4still exposed broken registry metadata.- Compared with
v1.3.4, it keeps the same CLI and runtime behavior, but changes how the publish artifact is staged and validated before release.
Highlights
1. npm registry metadata now matches the shipped package
- The CLI release flow now publishes from a dedicated staging directory whose
package.jsononly contains public runtime dependencies. - This closes the mismatch where the tarball was correct but the npm registry metadata still pointed at unpublished
@skill-flow/*workspace packages.
2. Direct source-package publishing is blocked
- A publish guard now stops accidental
npm publishruns fromapps/cliwhen the source manifest still contains internal workspace dependencies. - The intended release entrypoint is the staged publish command, which makes the publish path explicit instead of relying on temporary manifest rewriting.
3. Release verification is tighter
- npm packaging tests now verify both the packed tarball and the staged publish manifest.
- This makes it harder to ship another release where local
npm packsucceeds but the public install path is still broken.
User-visible changes
npm install -g skill-flowis repaired through a new release instead of relying on the already-publishedv1.3.4metadata.- Fresh npm installs and upgrades no longer ask the public registry for internal
@skill-flow/*packages. - The CLI command surface and runtime behavior stay the same; this release only repairs the publish path.
Release Artifacts
skill-flow-1.3.5.tgzSkill-Flow-arm64.dmgSkill-Flow-arm64.zipSkill-Flow-x86_64.dmgSkill-Flow-x86_64.zipSkill-Flow-universal.dmgSkill-Flow-universal.zipsha256.txt
v1.3.4
RELEASE v1.3.4
Summary
v1.3.4is a patch release focused on repairing the npm installation path for the CLI.- Compared with
v1.3.3, it keeps the target and desktop improvements from the previous release, but changes how the published CLI package is assembled so npm users can install and upgrade successfully again.
Highlights
1. Global npm installs work again
- The published
skill-flowpackage now bundles the internal runtime code it needs instead of asking npm to fetch unpublished internal workspace packages. - This removes the
E404failure path that blockednpm install -g skill-flowfor new users and upgrades.
2. More reliable release packaging
- The CLI release flow now rewrites the publish-time manifest so only public runtime dependencies remain in the tarball.
- Additional release verification now checks workspace version alignment and npm package output before publishing.
3. Existing workflows stay the same
- The CLI command surface, TUI behavior, and the built-in target improvements delivered in
v1.3.3are unchanged. - From a user perspective, the main difference is that installing or upgrading from npm is reliable again.
User-visible changes
npm install -g skill-flowno longer fails because npm cannot find internal@skill-flow/*packages.- Fresh installs and upgrades from npm behave more like a normal single-package CLI install.
- Release quality is easier to trust because the published tarball is now self-contained enough for the supported install path.
Release Artifacts
skill-flow-1.3.4.tgzSkill-Flow-arm64.dmgSkill-Flow-arm64.zipSkill-Flow-x86_64.dmgSkill-Flow-x86_64.zipSkill-Flow-universal.dmgSkill-Flow-universal.zipsha256.txt
v1.3.3
RELEASE v1.3.3
Summary
v1.3.3is a patch release focused on broadening target coverage and making built-in and custom agent handling behave as one coherent system.- Compared with
v1.3.2, it adds first-classTraesupport, aligns bridge/runtime/settings target metadata, and fixes a desktop tag editing edge case when a group has no tags yet.
Highlights
1. First-class Trae target support
Traeis now available as a built-in deployment target in the CLI, shared target definitions, desktop UI, and documented target list.- The desktop app also ships a dedicated
Traeicon and label mapping so target presentation stays consistent with other built-in agents.
2. Unified built-in and custom target handling
- Bridge responses, runtime coordination, TUI flows, shared preferences, and desktop settings now use the same target metadata model.
- Custom targets now persist more predictably alongside built-in targets, including display order, visibility, labels, and documented mount paths.
- This reduces drift between CLI, desktop, and stored preference state when teams mix standard agents with locally defined custom ones.
3. Cleaner desktop tag editing behavior
- Editable group cards now keep the add affordance visible when the tag list is empty.
- Regression coverage was added so compact tag input and add-button behavior stay locked down.
User-visible changes
- You can deploy skills directly to
Traeusing the same built-in target flow as other supported agents. - Custom agents and built-in agents are presented more consistently across CLI, bridge, TUI, and desktop settings surfaces.
- Desktop tag editing no longer gets stuck without an obvious add action when a group starts with zero tags.
Release Artifacts
skill-flow-1.3.3.tgz
v1.3.2
RELEASE v1.3.2
Summary
v1.3.2is a patch release focused on source import stability and npm package completeness.- Compared with
v1.3.1, it adds GitLab archive fallback coverage, keeps legacy lock files from blocking add preview, and makes the published CLI package carry its user-facing docs and license files.
Highlights
1. More reliable GitLab import flows
- Git-based source imports now support a GitLab archive fallback path in the shared runtime.
- GUI import flows follow the same behavior, so GitLab sources are less likely to fail when a direct clone path is unavailable.
2. Safer preview handling for existing state
- Add preview now tolerates legacy lock files instead of treating them as a hard failure.
- This keeps state preparation and projection checks working for users carrying forward older local data.
3. Cleaner npm package output
- The published CLI package now includes
README.md,README.zh.md, andLICENSE. - Release helper scripts now prepare and restore those package files during pack flows so npm output stays aligned with the repository.
User-visible changes
- GitLab-based imports behave more predictably in desktop and shared runtime flows.
- Existing local state with older lock files is less likely to interrupt add preview.
- npm consumers get bundled usage docs and license files directly inside the published CLI package.
Release Artifacts
skill-flow-1.3.2.tgz
v1.3.1
RELEASE v1.3.1
Summary
v1.3.1is a desktop-focused patch release that tightens project navigation, unifies group card presentation, and cleans up tag interactions.- It also refreshes the release metadata consumed by the desktop update flow.
Highlights
1. Clearer project scope entry
- Home now exposes project scope more directly from the header flow.
- Menu bar icon handling is covered more thoroughly so scope-related states stay easier to distinguish.
2. Unified group card presentation
- Desktop group cards now follow one presentation profile model across Home, menu, and import contexts.
- Compact layouts, loading behavior, and supporting chrome now stay aligned instead of drifting by context.
3. Cleaner tag and settings interactions
- Tag presentation is lighter and more compact, with hover-based add behavior that keeps dense layouts cleaner.
- Settings update checks now stay aligned with the current published release metadata.
User-visible changes
- Project scope is easier to reach and reason about from the desktop home flow.
- Group cards look and behave more consistently across desktop surfaces.
- Tags and update-related desktop behavior feel cleaner and more predictable.
Release Artifacts
Skill-Flow-arm64.dmgSkill-Flow-arm64.zipSkill-Flow-x86_64.dmgSkill-Flow-x86_64.zipSkill-Flow-universal.dmgSkill-Flow-universal.zipsha256.txt
v1.3.0
RELEASE v1.3.0
Summary
v1.3.0focuses on making the macOS desktop app feel more project-aware and more comfortable to use day to day.- You can now work with skills in a project-specific context, return to recent projects faster, and navigate desktop detail pages with smoother behavior.
- This release also improves how local skill groups are identified, so import and browsing flows are easier to understand.
Highlights
1. Project-specific desktop workflows
- The macOS desktop app now supports project scope, so you can move between a global view and a specific project without mixing their drafts or selections.
- Home now includes clearer project scope controls and quick project pills, making it easier to understand which context you are working in.
- Project-specific skills are mounted into the expected documented paths, so desktop behavior stays aligned with the existing workspace layout.
2. Faster return to active work
- Home now surfaces recent projects, including OpenCode workspaces when they are detected.
- This makes the desktop app more useful as a daily entry point instead of forcing you to re-enter project context each time.
3. Better local-source clarity
- Local skill groups now show clearer source metadata and preview details.
- If a group is already installed locally, the desktop app no longer encourages a redundant import action.
- These changes make it easier to understand what is already available on disk before taking action.
4. Smoother browsing and detail reading
- Group cards, tags, toolbars, settings controls, and detail navigation now have more consistent interaction feedback.
- Detail pages load markdown more smoothly, keep state more reliably during refreshes, and feel less disruptive when you switch between groups.
- Home scrolling, tag filtering, and detail sidebar transitions are more stable during repeated use.
User-visible changes
- You can keep separate desktop drafts and workflow state for different projects.
- Returning to a recent project takes fewer steps.
- Local groups are easier to recognize before importing or opening them.
- Reading long detail content is smoother and more predictable.
Release Artifacts
Skill-Flow-arm64.dmgSkill-Flow-arm64.zipSkill-Flow-x86_64.dmgSkill-Flow-x86_64.zipSkill-Flow-universal.dmgSkill-Flow-universal.zipsha256.txt