GitHub, import and listing problems
What each GitHub sync, pull request, import, listing and claim refusal means, and the one thing to do next for each.
The installation belongs to another organisation
Code: installation_bound
That GitHub App installation is already connected to a different Deftro organisation. An owner or admin there must Unbind it on their GitHub page first.
GitHub is not set up here
Code: github_app_not_configured
This Deftro site has no GitHub App configured, so nobody can fix it from their account. Report it on Feedback.
The repository is already linked
Code: link_exists
That repository is already linked to this project. Use the existing link under Linked Repositories.
No pull request link
Code: pr_back_disabled
The artifact has no linked repository with PR-back turned on. An owner or admin turns on PR-back for its link on the organisation's GitHub page.
The GitHub App needs write permission
Code: app_permission_missing
Opening a pull request needs the App's write permission for contents and pull requests. Press Configure on GitHub and accept the permissions.
The repository changed since this version
Code: repo_diverged
The skill's files on GitHub changed after this version was synced. Resolve it in the repository, or publish a new version first.
Only GitHub links work
Code: unsupported_source
Paste a plain https://github.com/<owner>/<repo> link, optionally to a folder.
The source changed since you previewed it
Code: upstream_moved
A new commit landed between your preview and your import. Press Re-preview, check the result, then import.
No skill was found
Code: no_skills
There is no folder with a SKILL.md at that link. Link to the folder that holds it.
The author has claimed it
Code: listing_claimed
The repository's author claimed the listing, so they publish it now. Find it under their account.
We could not confirm you own the repository
Code: claim_not_proven
Connect a GitHub account that administers the repository in Settings > Integrations (write access alone is not enough). Or install the Deftro GitHub App, from Import from GitHub, on the GitHub account that owns the repository. Then press Claim this listing again.
The repository is private
Code: private_source
Skills from a private GitHub repository cannot be imported as public, or into a skill that is already public. Import them as private, project or organisation skills, or under a different name.
A skill imported or synced from a private repository stays that way, whichever way it came in: it can never be made public later, and no public share link can open it. Choosing Public for it answers the same code. Private, shared, project and organisation stay available.
The installed version does not match
Code: pin_mismatch
A fingerprint in your bv.lock does not match that version on Deftro, usually because the file was edited by hand. Reinstall it with deftro install <handle>/<slug>@<version>.
Checked against the product on .
Bring skills in from GitHub
Import skills from your repositories, sync organisation repositories into Review with the GitHub App, import a public skill, or list and claim GitHub skills.Use the deftro command-line tool
Run deftro with npx to sign in, install pinned skill versions into your agent's folders, keep them in sync, and publish your own.You can't see or do that
Why Deftro answers "not found" for things you may not see, and what a conflict means when something already exists or an organisation rule stops a change.