Skip to content

Getting started for contributors ​

You have an idea for a skill, agent, or prompt, and you want it signed, released, and listed on Tara. This page walks through that whole path with the ph tara command line. First, install Phillip and sign in to Tara with ph tara login. If you haven't installed it yet, see Installation.

The Tara Portal also has a wizard for creating resources, an editor for new versions, and a place to upload packages. Go to the Contribute section, click Create resource, then choose Use the wizard or Upload a package. In the same section, you track the submissions you've made, like the ph tara submissions command. In the wizard and the upload page you choose the owner (yourself or an organization) and the visibility. Both ways go through the same automated checks, so use whichever is more convenient.

Step 1 of the wizard: type, owner and visibility.

Choose a resource type and where to publish ​

Tara has the resource types skill, agent, kit, prompt, and harness. See Six resource types. Every resource has an owner, and you choose it when you publish: your personal store, an organization you belong to, or (for platform staff) the official store.

PersonalOrganizationOfficial
Full name<your-handle>/<name>, for example an/skill-notes<org>/<name>, for example acme/skill-notesaiforge/<name>
Who publishesYouOwner, Admin, and Member by default; only Owner and Admin if the organization sets "Admins only". Viewers neverPlatform staff
How to chooseThe default, or no org in the manifestph tara publish --org <slug>, or metadata.forge.org: <slug>metadata.forge.org: aiforge
Visibilityprivate (default) or publicinternal (default) or publicAlways public
ReviewNone; the scanner decidesNone; the scanner decidesPlatform staff review each version
ContentScripts, hooks, and MCP allowed (public: Markdown and configuration only)The sameScripts, hooks, and MCP allowed

The path is personal, then organization, then public. Try a resource in your personal store, share it with your team with ph tara contribute <name> --org <slug> (it copies the resource and records who contributed it and where it came from), and make it public with ph tara visibility <name> public when it is ready for everyone. A bare name means aiforge/<name>, then your current organization, then your own store.

Use ph tara new --org <your-org> to start a resource for an organization, or leave --org out for your personal store. If you can't publish to your organization, an Owner or Admin may have limited publishing to admins in Settings, then General. You can still publish personally and ask an Admin to contribute it.

After release, a resource has its own page with docs, the install command, and download counts.

From idea to released resource ​

The path of a resource when you contribute. On your machine: ph tara new creates it from a template, ph tara check validates it, ph tara publish submits it to Tara. On Tara: automated checks, approval, Tara signs, then an immutable release. If changes are needed, the approver requests them and you return to the check step with a new version.On your machineCreate from templateph tara newCheckph tara checkSubmit to Taraph tara publishOn TaraAuto checksecrets, manifest,runnable code,malware scanApproverreads it,then approvesTara signsEd25519 key,at approvalReleaseimmutable version,signedenters the queueRequest changes

Swipe sideways to see the whole diagram.

To make changes, fetch the package with ph tara pull, raise the version with ph tara bump, then check and submit again. A submitted version never changes.
  1. Create the resource from a template. The name has the form <type>-<name>; the owner is chosen when you publish, not in the name:

    bash
    ph tara new agent agent-java-review --description "Review Java code against our conventions"

    The command creates a directory with plugin.json, README.md, CHANGELOG.md, and a scaffold for the type. Add --org <slug> to write the organization into the manifest, or leave it out for your personal store.

  2. Edit the content: write the agent or skill, update README.md, and add a CHANGELOG.md entry for the version you're about to submit. How to write them is in Write skills and agents.

  3. Check before you submit. This command runs the same chain of rules that Tara uses and saves nothing:

    bash
    ph tara check ./agent-java-review

    Fix every line that reports an error. Warnings don't block, but read them. The main rules cover the name, manifest, structure by type, documentation, dependencies, and secret scanning.

  4. Publish to Tara. With no option the resource goes to your personal store; use --org <slug> for an organization, and --visibility to choose the scope of a new resource:

    bash
    ph tara publish ./agent-java-review

    Tara scans the package and releases it at once if nothing blocks it: no review queue, except for the official store. A new personal resource starts as private and an organization resource as internal.

  5. Track the submission:

    bash
    ph tara submissions                           # your submissions and their status
    ph tara status agent-java-review@1.0.0    # check results, reason for sending back
  6. When you need to make changes, pull the source, bump the version, and submit again. A submitted version is immutable, so each change must be a new version:

    bash
    ph tara pull agent-java-review@1.0.0 --dir ./agent-java-review
    ph tara bump ./agent-java-review 1.0.1 --changelog "Address feedback"
    ph tara check ./agent-java-review
    ph tara publish ./agent-java-review

How to number versions is in Versioning rules.

What state is your submission in? ​

Status in the CLIMeaningWhat you do
submitted, checkingTara received the package and is running the automated rule chainWait a few seconds to a few minutes
checks failedA rule at error level failedRead ph tara status, fix it, and submit a new version
awaiting review, changes requestedOfficial store only: waiting for, or returned by, platform staffWait, or fix it according to the reason and submit a new version
publishedPassed the checks, signed, and visible to whoever can see the resourceNothing more to do
deprecated, yankedThe version is no longer recommended, or it has been yankedSubmit a fixed version if needed

The checks are described in Review criteria.

Roles and signing ​

Roles belong to the organization. An Owner or Admin changes roles in the Admin section of the Portal, or with ph org members set-role <login> <owner|admin|member|viewer>, and sets who can publish to the organization in Settings, then General. Official resources (aiforge/<name>) are published and reviewed by PhillipCLI platform staff; reviewing needs a browser sign-in session, and personal tokens can't approve.

When a version is released, Tara digitally signs its manifest, which includes the name, version, sha256, owner, channel (official, org, user, or community), and release time. On every install, Phillip verifies this signature, so a package modified after release is rejected. If a version has a serious problem, it's yanked (yank) and Tara re-signs the yank list. Details are in Version locking and digital signatures.

For a personal resource, you change the visibility with ph tara visibility <name> public|private and yank a faulty version yourself with ph tara yank. For an organization resource, an Owner or Admin does it. If someone else suspects a resource has a problem, they use ph tara report, and Tara rescans it right away.

Read more ​