Skip to content

Review criteria ​

Read this page to prepare a submission that passes on the first try, and to understand why it was blocked. It covers two things: what Tara checks automatically on every version, and what the PhillipCLI reviewers read before they approve a version of the official store.

What steps does a submission go through? ​

A submission to your personal store or to an organization goes through these steps in order: submit, automated check, signing, release, then notification. No person approves it. If the scanner doesn't block the version, it is released at once. Only a submission to the official store (aiforge/<name>) also waits for approval by PhillipCLI platform staff, in the Portal under Settings, then Platform, then Official review. A public resource follows the community rules (see the end of this page).

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.

You can see check results at any time with these two commands.

bash
ph tara check ./resource-directory
ph tara status resource-name@1.0.0

Finding severity ​

LevelConsequence
errorBlocks release. Fix it and submit a new version
warningThe reviewer (official store) weighs it and can approve with a note
infoInformation for the reader, such as the list of executable components
malwareThe malware scanner matched. The submission is rejected and the package is deleted immediately

For official resources, many content findings are only warning because a person reads the resource and makes a decision. No one reads personal and organization resources, and public ones even less, so the same finding can become an error, most often when you make a resource public.

What does Tara check automatically? ​

Manifest and structure ​

Tara reads plugin.json and checks that version is valid semver and that description and author.name are present. The metadata.forge block must be complete: schema, type, owners in email format, valid engines, status set to active or deprecated, roles from the allowed list, an org that is aiforge, an organization you belong to, or your own handle (or no org, which means your personal store), and a model that is in the catalog. The name must follow the naming rules for the resource type. See The six resource types.

The directory structure is checked by type. An agent needs agents/*.md. A skill and a prompt need skills/*/SKILL.md. A harness needs template/CLAUDE.md and dependencies. A kit needs at least one connection form. Every type needs README.md and CHANGELOG.md, and CHANGELOG.md must have a ## <version> section for the version you submit.

For dependencies, the referenced resource must exist and be released, the constraint must be valid and satisfiable, and it must not point to another marketplace. Bundled docs must have the right type, format, and size, and a kit or harness must have install and usage.

Claude Code validation ​

Tara runs claude plugin validate --strict on the package. If Claude Code is installed on your machine, run the same command before you submit.

Secrets ​

A package must not contain credentials. Tara scans for common token and key patterns. Store secrets elsewhere (kits receive them through connect), and don't paste real sample tokens into the README.

Executable components ​

Scripts (.sh, .py, .mjs, and so on), the bin/ directory, hooks, MCP servers, and binary files are all listed at info level. Personal and organization resources may contain them, and everyone who installs the resource runs that code, so keep it short and readable and don't download extra code from outside. In the official store a reviewer reads every line. Public resources may not contain executable components at all.

Content ​

Tara inspects content in six groups. Hidden characters include concealed text that a model can read and display-reversing characters. Prompt injection means instructions that tell the agent to ignore rules, hide what it does from the user, or turn off protections. For permissions, Tara looks for tools that request broader permissions than needed and for bypassPermissions. For network destinations, Tara lists the domains in the package and warns about services that receive data anonymously, URL shorteners, and bare IPs. For sensitive data, Tara looks for ID numbers, payment cards, phone numbers, emails, internal domains, and private IPs in the content. Finally, every shell command in the resource is scored by the Guardrails rule set itself.

Tara doesn't publish the details of the patterns. If you get a warning and your content is legitimate, explain it in the README, for example under ## Permissions, so the reader or the reviewer understands.

Malware scan ​

The malware scanner runs on the package, and a match rejects the submission immediately. If malware shows up in an already released version, through a rescan or a user report, Tara removes the package and adds it to the yank list.

What does the official reviewer read? ​

Only the official store has this step. The reviewer is PhillipCLI platform staff, who sign in with a browser session, not with a personal token. They check seven things.

  1. The resource does what it describes, and no more.
  2. They read every line of scripts, hooks, MCP servers, and executable plugins, and network destinations must match the purpose.
  3. Permissions are minimal: tools are limited to what's needed, with no extra permissions requested.
  4. Instructions are clear and consistent, and contain no internal data or secrets.
  5. Dependency version constraints are reasonable.
  6. The version bump matches the change. See Versioning rules.
  7. The README, CHANGELOG, and bundled docs are enough for someone else to install and use the resource.

The outcome is either approval, in which case Tara signs and releases, or a return with a reason. If it's returned, fix it, bump the version, and submit again. Authors can't approve their own submissions.

What does a Guardrails policy package add? ​

A policy package goes through two more checks: the structure of the rule file and the syntax of expressions. The result states whether the policy only tightens or also loosens. See Guardrails tiers.

What are the limits on community resources? ​

A public resource, which carries the Community label, can contain only Markdown and configuration. Tara rejects kits, hooks, mcpServers, executable files, and archives when you publish with --visibility public or change a resource to public, and it adds a model review. To share a kit or executable code, keep it personal, contribute it to your organization, or submit it to the official catalog.

Anyone can report a suspicious resource, and Tara rescans it as soon as it receives the report.

bash
ph tara report resource-name --reason "Describe the problem"

Further reading ​