Skip to content

Six resource types ​

Tara holds six resource types, and five of them are plugins that follow the Claude Code standard. Read this page to find out which type fits the work you plan to do.

The six types at a glance ​

TypeName prefixWhat it isMain parts
Skillskill-Knowledge or a procedure that an agent loads on its own when neededskills/<name>/SKILL.md, scripts, templates
Agentagent-A subagent with its own roleagents/<name>.md (system prompt, tools, model)
Promptprompt-A command the user invokesskills/<name>/SKILL.md in command form
Kitkit-A connection or integration.mcp.json, hooks/hooks.json, Phillip plugins, Guardrails policies
Harnessharness-A complete working environment for an organization or projectdependencies on other resources, a template/ directory
ModelaliasA profile for a model that is allowed for useAn entry in the catalog, not an installable package

Built on the Claude Code standard ​

Tara is a plugin marketplace that follows the Claude Code standard. Except for models, every resource has a .claude-plugin/plugin.json, so Claude Code recognizes them like any other plugin. Slash commands, subagents, and skills show up in Claude Code as usual. Version constraints between resources use the standard dependencies syntax. Skills follow the open Skills standard (SKILL.md), so you can reuse them outside the platform. You can also check a resource yourself with claude plugin validate, the same command Tara runs when it receives a submission.

The platform's own data lives in the metadata.forge block of plugin.json, which Claude Code ignores. The detailed fields are in Resource format.

Resource naming ​

Names take the form <type>-<name>, in kebab-case, up to 64 characters, for example agent-reviewer. Names also can't contain words that Anthropic reserves. The full name adds the owner: <owner>/<name>, for example acme/skill-review or an/skill-notes. Because each owner has its own namespace, two owners can both have a skill-review without clashing. Older names with an extra code in the middle, such as agent-tta-java-review, stay valid.

Skills and prompts ​

A skill is a directory that contains a SKILL.md with a description. Claude reads the description and loads the skill on its own when the current work matches. A prompt has the same structure, but you invoke it yourself with a slash command, for example /prompt-release-note:release-note.

To give an agent knowledge or a procedure, choose a skill. To get a named command that you call yourself, choose a prompt. For how to write them, see Write skills and agents.

Agents ​

An agent is a subagent with a role, such as requirements analysis, coding, review, or testing. The agents/<name>.md file has a header that declares the name, description, and the tools it can use, and a body that holds the system instructions. An agent declares dependencies on the skills it needs.

Limit tools by role. Tara warns you at review time about unrestricted tools, such as fully open Bash.

Kits ​

A kit is a connection package, and one kit can combine several forms. The MCP server form is declared in .mcp.json, for example to connect the Knowledge base or to give agents GitHub and GitLab tools. The hook form is declared in hooks/hooks.json, for example a check before a turn ends. The Phillip plugin form is declared in metadata.forge.phillip for the scm, notify, and tracker providers. The Guardrails policy form is declared in metadata.forge.guardrails and holds the safety rules of the platform, an organization, or a project.

Kits never contain credentials

A kit never contains credentials. The user or the service passes tokens in when connecting. The contract and how it is checked are in Write kits.

Harnesses ​

A harness is a distribution: a package that references agents, skills, prompts, and kits by version constraint, plus a template/ directory. Inside it, template/CLAUDE.md holds your organization's conventions. Claude Code doesn't load a CLAUDE.md at the plugin root, so ph init inserts this content into the project's CLAUDE.md, inside a marked block. template/settings.json is the default configuration. It is merged into .claude/settings.json and keeps the values you have already set. There are other template files too, such as .bandum.json.

Installing a harness gives you the complete environment.

bash
ph init harness-rnd-sdlc

Running the command again replaces only the content inside the block that Phillip manages. Anything you wrote outside the block stays as it is. For how to write a harness, see Write harnesses.

Models ​

A model isn't an installable package. It's an entry in Tara's catalog that holds an alias, the real model name, a purpose, and suitable roles. There are three purposes: reasoning for reasoning, design, and review, code for code generation and everyday analysis, and light for quick, simple work.

Each purpose has a recommended model. The ph model use <alias> command writes the model to the project's .claude/settings.json. A deprecated model still shows up, but you shouldn't pick it for new work. See also Choose a model.

Who owns a resource: you, an organization, or PhillipCLI ​

Every resource has an owner, the way a repository does on GitHub. The full name is <owner>/<name>.

OwnerExampleVisibilityWho can see and install it
You (personal store)an/skill-notesprivate (default) or publicOnly you, in every organization you belong to
An organizationacme/skill-notesinternal (default) or publicEvery member of the organization, Viewers included
PhillipCLIaiforge/skill-reviewalways public (official)Everyone

A public resource of a person or an organization carries the Community label and is visible to every PhillipCLI user. User handles and organization slugs share one namespace, so an/ can never be both a person and an organization. Creating an organization whose slug equals someone's handle is refused, and a new user whose handle equals an organization slug gets a suffix, for example an-2.

From personal to organization to public ​

A resource moves outward in three steps, and none of them needs a person to approve it.

  1. Personal. Publish to your own store to try the resource for yourself. This is the default for ph tara publish.
  2. Contribute to an organization. Copy it into <org>/<name> with ph tara contribute <name> --org <org>, or publish straight into the organization with --org. The copy records who contributed it and where it came from, and it is released immediately and signed for the organization. The organization setting Who can publish to this organization decides whether Members or only Admins can do this. Viewers never can.
  3. Make it public. Change the visibility to public. Community rules apply: no executable components, a malware and secret scan, and a model review. For an organization resource only an Owner or Admin can do it. You can't close a public resource again while another public resource depends on it or a project lock pins it.

Two things hold in every step: the automated scanner (malware, secrets, prompt injection), the signature, and version locking are always on, and a version is released as soon as the scanner doesn't block it. Personal and organization resources may contain executable components such as hooks, scripts, and MCP servers, so read what you install. Public resources may not.

Only the official store, aiforge/<name>, has a review step. PhillipCLI platform staff review each version there.

How a name is resolved ​

A bare name such as skill-review is looked up in this order: aiforge/ first, then your current organization, then your own personal store. It never matches another person's or another organization's resource, so nobody can take over a name by publishing a public resource with it. If nothing matches but a public resource with that name exists elsewhere, Tara answers 404 with a hint that lists full names, for example did you mean beta/skill-foo?. A bare name in the dependencies of a package resolves to aiforge/ first and then to the owner of that package.

In plugin.json, metadata.forge.org names the target owner: aiforge or an organization slug. If it is absent, the resource goes to your personal store. --org on ph tara publish overrides it. Each release channel appears in the signature as official, org, user, or community. See Version locking and signing.

Each version has a lifecycle status, from checking to published, then deprecated or yanked (awaiting review exists only in the official store). Phillip asks you to confirm before it installs a community resource into a project. To forbid them entirely, set PHILLIP_TARA_COMMUNITY=deny.

Next steps ​