Import resources from GitHub or GitLab
If a skill, agent, or plugin already lives in a GitHub or GitLab repository, you don't have to repackage it. Paste the repository, and Tara finds what is inside, scans it, and publishes the items you pick.
In the Portal, go to Contribute › Create resource › Import from GitHub or GitLab. From the terminal:
ph tara import github acme/tools # your personal store (default)
ph tara import github acme/tools@v1.2/skills --to acme # a folder at a tag, into the organization acme
ph tara import github https://github.com/acme/tools --only skill-review,sql-helper --yes
ph tara import https://gitlab.com/acme/platform/tools/-/tree/main/skills --to acme # GitLab, a folder on a branchph tara import <source> works for both. import github <source> and import gitlab <source> still work as aliases, because the source itself decides the provider.
What you can paste
owner/repo, owner/repo@ref (a branch, tag, or commit), owner/repo/folder, owner/repo@ref/folder, or a GitHub URL.
For GitLab, paste the project URL: https://gitlab.com/group/subgroup/project, a folder or branch such as https://gitlab.com/group/project/-/tree/v1.2/skills, a file link (/-/blob/), or git@host:group/project.git. The group path may include subgroups. Any host other than github.com is treated as GitLab, and it must be gitlab.com or a host your operator allowed. Otherwise Tara refuses it with host_not_allowed and never calls it.
Tara turns the ref into a commit first and reads exactly that commit, so what you review is what gets imported. The commit, path, and license are recorded in the package.
What Tara finds
| In the repository | Becomes |
|---|---|
A plugin (.claude-plugin/plugin.json, or local entries of a marketplace.json) | A kit if it has hooks or MCP servers, otherwise a skill, agent, or prompt |
A skill folder (with SKILL.md) | A skill |
An agent (.claude/agents/*.md) | An agent |
A command (.claude/commands/*.md) | A skill of kind prompt |
.mcp.json | A kit |
You see the list and choose which items to import. Names are <owner>/<kind>-<name>, where the owner is the target: your handle, or the organization's slug.
Where it goes
- Your personal store (default, private). Use
--personal, or leave--toout. - Your organization, with
--to <org>. You need permission to publish there. Items are visible to the organization's members.
You can't import into the official catalog (aiforge/). A private repository goes only into the organization whose GitHub App installation contains it, never into a personal store, and it is never public. Imported items start private or internal. Making one public follows the community rules, and an unlicensed item can never be public.
Public repositories need no sign-in to GitHub or GitLab. For a private repository, Tara reads it with the organization's installation, and only if the repository is in that installation. On GitLab the same rule uses the organization's GitLab connection: a private repository is read only if it is inside the connected group, only for someone who can publish to that organization, and it goes only into that organization.
The scan and the license
Every item is built into a normal package and goes through the same checks as an upload (malware, rules, and model review as configured). If it passes, it is released at once, with no manual review. Each item reports one result:
| Result | Meaning |
|---|---|
published | Imported as a new version |
unchanged | The content is the same as the last import, so nothing was created |
scan_failed | A check found a problem. The findings are listed |
rejected | Malware was found |
blocked_license | The license doesn't allow it here |
failed | Something else went wrong |
Importing again creates a new version only if the item's content changed. A name already taken by something that didn't come from this repository is refused.
License policy. Tara respects the repository's license:
| License | Where it can go |
|---|---|
| MIT, Apache-2.0, BSD-2/3, ISC, Unlicense, CC0, 0BSD, MPL-2.0, CC-BY-4.0, and the GPL, LGPL, and AGPL family | Any target. The license text is kept in the package |
| No license (the default on GitHub and GitLab is all rights reserved) | Your personal store only, private, like a clone |
| Proprietary or "all rights reserved", non-commercial, no-derivatives, BUSL, SSPL, or text Tara can't recognize | Blocked everywhere |
A repository you own needs no license when you import it into your personal store (your GitHub login equals your handle), or into the organization whose GitHub installation or GitLab group contains it. For GitLab, a personal store never gets this exemption, because a GitLab namespace isn't tied to a handle.
Limits
Tara downloads the repository as an archive (on GitLab too, at the pinned commit), up to 50 MiB, keeps up to 10,000 files and 200 MiB, and allows 10 MiB per file, within 2 minutes. It skips symlinks, special files, oversized files, and unsafe paths, and reports them. The rest still imports.