Repository navigation
Troubleshooting
Delivery status — November 22, 2026. Public pre-release 0.15.7 includes plugin-folder handling and the nested-workbench connection fix. Stable is 0.12.3.
Check the installed version and selected VS Code profile. The command is available in pre-release 0.15.7 from Workbench Home and the Command Palette. Select the plugin root containing .claude-plugin/plugin.json. For a manual upload in Claude, choose Save ZIP for Claude and upload the ZIP from Claude's plugin settings.
The affected older preview builds route connection actions to Settings. In preview 0.15.6 and stable 0.12.3, Connect repository and Change connection open the repository wizard.
Save your work, update the intended channel when available, reload the VS Code window, and check SkillJetty's loaded version. If the action still opens Settings, report that version and profile. Do not assume another computer's installation or path applies to this one.
The Workbench folder holds SkillJetty's drafts, builds and recovery. The Local repository is a separate Git root containing your shared skills or ZIPs. The Remote repository is its matching GitHub address.
Preview 0.15.7 can connect an existing repository containing its private workbench as a child. SkillJetty checks whether any workbench files are tracked and confirms the local Git exclusion when needed.
Choose Connect repository, enter the GitHub URL, then select an existing local Git root or confirm Create a local copy. Review the full paths before connecting. A skill/version folder, GitHub tree/ page and the workbench itself are not the local repository root.
The GitHub remote must have an initial commit. For linked worktrees, redirected Git metadata or unsafe transport configuration, use a normal local copy whose exact root and remote can be verified. Do not rewrite an old remote or loosen global Git trust to bypass a warning.
A guided connection saves one complete local/remote pair. An old URL/path preference does not silently replace half of it. Use Change connection to complete the switch. Existing drafts and historical upload receipts keep their original locations and identities.
If another window or Git operation changes the pairing/configuration during setup, SkillJetty stops before activating stale information. Reopen the connection flow and review the current mapping.
The previous connection stays active. A failed copy is not treated as a connected repository. Existing files at the selected destination are not overwritten. Keep the complete error: it distinguishes the original cloning failure from any retained temporary or incomplete material.
Do not delete drafts, receipts or caches to repair a connection. Inspect the reported retained location before deliberate cleanup; an incomplete destination must not be mistaken for a verified local copy.
An existing local copy is checked without pulling its files. Sync repository explicitly downloads updates, protecting local edits and conflicting files. Uploading a package and merging its PR are later, separate actions.
Open skill from repository, GitHub account switching and local package saving remain available. Local editing needs no GitHub sign-in. See Connect and Sync.
The dated sections below preserve earlier incidents and verification. Use the guide above for preview 0.15.7 or stable 0.12.3.
Published and publicly verified on November 3, 2026. Stable remains 0.12.2.
A Both submission now recognizes an unchanged portable skill that GitHub confirms was already merged, even after its review branch was deleted, and continues with the pending plugin. The check matches the repository, target branch, PR and exact uploaded commit. A cached merge result or failed GitHub check is insufficient. Existing packages and receipts are preserved; the old portable upload is not repeated.
After updating, save your work and run Developer: Reload Window in VS Code. Confirm SkillJetty shows Installed pre-release 0.15.5. On Home, open the built plugin with Edit plugin, then Build / Share. To retry the preserved ZIP, set its plugin Version to the already prepared version instead of accepting the next-version suggestion; choose Both skill package and plugin ZIP for a Both retry. Keep unchanged member versions and use Build & upload. Inspect each export's PR result. Plugin export, GitHub upload, PR merge and a Claude directory submission remain separate outcomes. Do not delete work or caches to retry. Local package checks do not prove application runtime behavior.
Automated tests and independent package/native retry checks passed. No actual user plugin was uploaded during verification; live user retry and human usability acceptance remain unverified.
Known separate limitation: reopening a plugin with custom plugin-only release notes can regenerate different notes and refuse to reuse that immutable version. The old ZIP is preserved and nothing uploads. Restore the original release notes explicitly before attempting that same version; do not delete the saved package.
Preview 0.15.4 is published and verified. Stable remains 0.12.2. See Release Notes for verification and its limits.
Home shows your work automatically. Required choices and next actions are visible. Build / Share runs the structural checks and offers build-and-upload directly for a connected repository. Existing files and connections are preserved.
Earlier preview 0.15.3 was published and verified. Stable remains 0.12.2. See Release Notes for the reviewed source/build and actual verification limits.
Start now offers Create a skill and Build a plugin. A skill is its instructions and supporting files; a Claude plugin is a bundle containing one or more skills. Choose the task first, open or create the skill content, check it, then review and save the chosen package. The plugin route keeps plugin output selected and shows its bundle details at review. Optional publisher details and repository locations are collapsed.
Saving a skill or plugin locally does not need GitHub. Repository errors describe upload setup; they do not prevent local creation or packaging. A newly selected workbench does not acquire another folder's repository automatically. Existing accepted repositories retain their exact data boundary. Installing a saved plugin into Claude remains a separate action.
Earlier preview 0.15.2 was published and verified. Stable remains 0.12.2. The public catalog flags and downloaded extension payload were checked against the reviewed build. This does not establish the version loaded on every user computer.
Preview 0.15.0 could reject an existing saved repository setup and remain on “Waiting” after folder selection. The repair restores the ordinary Create/Open → Edit → Check → Submit workflow for explicitly configured, previously connected repositories. Managed-workbench setup remains optional; existing repositories and drafts are not moved or converted.
Use the Git repository root containing .git as the local repository and its root GitHub address as the remote. A skill/version folder and a GitHub tree/ or blob/ page are not repository settings. Do not add setup markers or move existing skills to bypass the error. See the recovery troubleshooting guidance.
A running build, installed profile entry, and public channel are separate states. Stay in the profile you intend to use and check its installed version; a later gallery install can replace a local test package.
Earlier public pre-release 0.15.0 was published and verified. See Release Notes for the exact build and verification evidence. Production remains on its separately verified release; check your installed version in VS Code.
Plugin exports and archiving explains the new workflow and its limits. Earlier dated release evidence below is retained as history.
Stable 0.12.2 and preview 0.13.2 correct the public description, changelog and license branding. The publisher display name is SeñorFarris and product copy uses SkillJetty by DAF-TECH. Those changes do not change the technical Identifier shown in VS Code extension details, which still contains the legacy publisher identifier. The requested identifier correction is therefore not fully fixed.
A supported migration path is still being investigated. No identifier rename, existing-listing transfer, replacement listing or automatic user migration has been completed. Changing a local package's publisher field alone is not a verified migration of installed users, history or release channels. Existing published versions remain available through the existing listing; do not uninstall or delete work in an attempt to repair the field. This wiki will distinguish any approved migration from the branding-copy fixes already delivered.
Current status: the empty DAF-TECH publisher has been created and Marketplace support has been contacted. The owner chose to wait for Microsoft's answer about a supported transfer. No transfer or update/history preservation is guaranteed. The existing listing, stable and preview channels, and visible legacy Identifier remain unchanged; replacement-listing and other identity changes are on hold.
Version note: the preview settings guidance below also applies to 0.13.2, whose runtime matches 0.13.1. Stable 0.12.2 retains 0.12.1 behavior. The new packages correct public branding; they do not change skill contents, repository identity or setup.
These notes apply to preview 0.13.1, not stable 0.12.1 or older preview 0.13.0. Check your installed version before looking for the new fields or commands.
- Where did the repository forms go? Use the workbench gear or SkillJetty: Open Settings. The new workbench setup summary displays choices; the two preview repository fields are edited in Extension Settings. Older versions still use Repository & GitHub settings inside the workbench.
- I saved a path but nothing downloaded. This is expected. Settings describe the destination; run SkillJetty: Pull Skills Repository explicitly to clone or update it. Verification reads state without pulling working files.
-
Blank URL still shows my old repository. An unset setting can retain the old per-work-folder connection. To disconnect deliberately, save an explicit empty
skillBuilder.prerelease.repositoryUrlin Workspace settings. Reset removes the value at that scope and can expose a User value or saved connection again. -
I want upload without a local checkout. Save an explicitly empty
skillBuilder.prerelease.localRepositoryPath; upload may use its temporary download route. Verify, Pull and Open Skill from Repository still need a local path. - A bad setting blocks sharing. Correct the explicit value; SkillJetty must not upload to the previous connection instead. Local editing and Save package on this computer remain available.
- Settings changed during a submission. Review a fresh destination summary before retrying. A stopped fetch may have downloaded Git objects/metadata while leaving checkout HEAD and working files unchanged. Check the receipt before repeating any remote action.
- Project Root changed but the draft is still here. The active draft intentionally keeps its original work folder. Save, close and reopen the workbench. No stable/preview data migration happens automatically.
See the version-specific settings guide. The published-version troubleshooting below remains applicable to the older setup controls.
Start by noting the SkillJetty version and channel shown in VS Code, the action you chose, and the exact visible error. Keep the draft and any upload receipt while investigating.
In the repaired versions, use the visible Workbench folder, Local repository, and Remote repository mapping. Choose Connect repository to select an existing local copy or confirm a new clone. Connection and Sync are separate actions. Older accepted work remains preserved. See Connection and Sync.
Preview 0.15.4 carries the exact existing trust for an accepted repository, including its own Git metadata, into the isolated local clone. App-created local repositories use their recorded ownership. No wildcard or global trust setting is written. Check the configured local Git root and preserve the error/receipt if an untrusted or changed repository is rejected.
Choose the folder containing the skill's own SKILL.md directly. In the published example, this is Skills-Repository/meeting-notes/1.0.0/source/meeting-notes, not Skills-Repository and not meeting-notes/1.0.0. The version directory contains the complete release bundle, while its nested source directory contains the skill itself. See the annotated layout diagrams.
Ignored does not mean disposable. In 0.15.2, unrelated ignored files can remain in the repository during a pull. The extension checks the exact fetched commit for paths that would overwrite an ignored file or directory, and Git also refuses ignored-file overwrites at merge time. Ordinary local changes still require preservation. A private fetch reference keeps another fetch from changing the commit between inspection and merge. No ignored file is deleted to make a pull succeed.
A GitHub sign-in, session or permission error is not by itself evidence of corrupted skill files or a damaged repository.
Choose Change connection or the settings gear, confirm the destination repository and selected account, and sign in again when VS Code requests it. The account must have the repository permissions needed for the action. Git upload credentials and VS Code's GitHub API session are distinct access paths; one working does not prove the other works.
Use Check PRs if an earlier upload may already have succeeded. Avoid repeatedly creating submissions until the saved result has been checked. Do not post access tokens, credentials or unredacted private logs in an issue.
See Release Channels for current verified versions. Historically, stable 0.12.1 overtook preview 0.11.13; preview 0.13.0 repaired that ordering. Preview 0.15.6 is now publicly verified. Refresh extension details and check the installed version/profile if the option is missing. This is independent of GitHub login and skill repository contents.
For the branding-only 0.12.2/0.13.2 update, the stable job was canceled during its catalog wait after the upload bytes were verified; the preview uploaded once and its catalog wait timed out. Read-only checks at 22:17:23 UTC on November 1 confirmed both validated public versions and exact matching packages. Both switch actions were enabled in isolated fixtures. There was no replacement upload. See Release Notes for the package digests and public branding verification.
Upload completion and Marketplace catalog validation are separate stages. For 0.13.1, the single upload completed at 20:40:35 UTC on November 1; the publishing job's catalog wait timed out at 20:45:45 UTC. Read-only verification at 20:47:04 UTC confirmed the validated latest pre-release, matching public package bytes, retained stable version and AI category. The timeout did not require uploading the same version again. This describes release delivery, not installation on your computer.
Stable 0.12.1 fixes a false rejection when replacing a version moves an unchanged file. Git's rename detection could describe changed paths differently before and after committing. The fix compares literal changed paths consistently, while retaining file inventories, index/commit checks and protection for unrelated files.
Published preview 0.13.0 also includes that fix. Check Release Notes and your installed version. Preview 0.11.13 predates this repair.
If the error continues on a fixed version, keep the draft and receipt, check the recorded PR/upload state, and report the exact action and version. The same message can also identify a real change after review; do not bypass the integrity checks or delete repository history.
Confirm that the selected folder is the intended repository and that its remote matches. SkillJetty preserves local changes, ignored files, unexpected branches and trust decisions instead of silently overwriting them. Resolve or preserve your local work before pulling. Use the explicit pull/verification actions and read their result.
Publication can reuse data from the configured local repository, but it still fetches current remote information and checks the submission. Reusing local data does not mean trusting a stale snapshot or publishing unreviewed local edits.
SkillJetty keeps the newer saved file and preserves conflicting workbench edits in local recovery. Read the recovery notice before reloading. Do not assume that a visually unchanged editor means no external changes occurred.
An upload, PR creation, review request, merge and branch deletion are separate results. Keep the saved receipt. Use Check PRs, Create PR or the recorded PR link as appropriate; a PR retry does not require uploading the same files again. A confirmed merge remains recorded if branch cleanup needs another attempt.
Use Activity for current steps, completion results and next actions. Large packages, many files, Git operations and authentication can take different amounts of time. A message being replaced is not proof that its phase succeeded.
For local timing details, run SkillJetty: Show Performance Log from the Command Palette. Stable keeps this command while hiding the workbench log button. Review any output before sharing it and remove sensitive surrounding information.
Open a repository issue with version/channel, action, expected result, actual result, and minimal reproducible steps. State whether an upload or PR already exists. Include only material you are authorized to share; omit credentials, private skills and private repository details.
The managed-workbench setup gate in preview 0.15.0 could make a saved Skills repository look disconnected. A connection record can still exist even when the page says “Setup needed.” Preserve the repository and private preview data; do not recreate the repository, reset it, or fabricate a setup marker.
The 0.15.2 repair verifies the explicitly configured Git root against its saved connection and origin, then resumes its existing private data folder. The Configuration summary separates working files, the local Git repository, GitHub repository and branch. An individual skill is opened/imported from Start; it is not the sharing repository root.
Setup feedback should change from requesting a chooser, to waiting for a selection, to checking the selected folder. Cancellation and errors must unlock the page. An optional notification should never hold this queue. If reporting an issue, include the installed version and the displayed error; save drafts before you choose to reload the editor.
The 0.15.2 pull repair permits unrelated ignored files while rejecting incoming collisions. It inspects and merges the same immutable fetched commit, preserves shared FETCH_HEAD, and aborts if the repository connection, branch or starting HEAD changes during the operation.
SkillJetty by DAF-TECH · Release status · Support