Skip to content

Resource format ​

This page describes the plugin.json of every resource on Tara, the metadata.forge block, the package structure for each type, and the model catalog. For a step-by-step walkthrough, see Write skills and agents.

plugin.json ​

The file lives at .claude-plugin/plugin.json. Its fields follow the Claude Code plugin standard, plus Tara's own rules.

FieldRequiredDescription
nameYesResource name; see naming rules
versionYesSemver MAJOR.MINOR.PATCH
descriptionYesShort description, non-empty
author.nameYesAuthor or team name
displayNameNoDisplay name
licenseNoLicense
keywordsNoSearch keywords
dependenciesHarness: yesList of dependencies; see the section below
hooks, mcpServersNoDeclared directly. Usually placed in hooks/hooks.json and .mcp.json
metadata.forgeYesPlatform-specific data

Claude Code treats version, description, and author.name as optional, but Tara requires all three.

dependencies ​

Each entry is an object { "name", "version" } or a string "name". You can depend only on resources that are on Tara, not on another marketplace. An official resource can also depend only on official resources.

json
"dependencies": [
  { "name": "agent-dev", "version": "~1.1.0" },
  { "name": "skill-sdlc", "version": "^1.2.0" }
]

Version constraints can be written as ^1.2, ~1.2.0, =1.2.0 (or 1.2.0), >=1.0 <2.0, and ^1.0 || ^2.0. Tara warns if a constraint is missing. How Tara locks versions is in Version locking and digital signatures.

metadata.forge ​

Claude Code ignores this block. Only Tara and Phillip read it.

FieldRequiredTypeDescription
schemaYesnumberFormat version, currently 1
typeYesstringskill, agent, kit, prompt, or harness
orgOfficial and organization resourcesstringNamespace of the store: aiforge for the official catalog, or the slug of your own organization for its private store. If omitted, this is a community resource in the submitter's namespace
centerNostringDeprecated, replaced by org. Still read, with a warning: rnd means aiforge, any other value means the submitter's organization
ownersYesarray of emailsPeople responsible for maintenance, at least one
rolesNoarray of stringsMatching job roles: PO, BA, UIUX, SA, PM, Dev, Reviewer, Test, Security, DevOps, Docs, Builder
enginesYesarray of stringsclaude-code, or phillip (only for Phillip plugin kits)
statusYesstringactive or deprecated
replacedByNostringName of the replacement resource when deprecated
modelNostringDefault model alias for a harness, which must be in the catalog
docsNo*arrayBundled docs; see the section below. *Kits and harnesses must have install and usage
phillipPlugin kitsobjectPlugin declaration for Phillip
guardrailsPolicy kitsobjectGuardrails policy package declaration

roles helps with search and suggestions only. It doesn't grant permissions.

docs ​

json
"docs": [
  { "type": "install", "path": "docs/cai-dat.md", "title": "Installation guide" },
  { "type": "usage", "path": "docs/su-dung.pdf" }
]
FieldDescription
typeinstall, usage, configuration, troubleshooting, or other
pathPath in the package
titleDisplay title; if omitted, the type name is used

Tara currently accepts md (up to 2 MB) and pdf (up to 20 MB, with a signature check on the file header). Types and formats are Tara configuration, so they may differ in your organization. Call GET /v1/document-policy to see them. Docs are separate from the install package, stored per version, can't be edited, and are covered by the digital signature. To read them, run ph tara docs <name>.

phillip ​

This block is for kits with engines: ["phillip"]. The detailed contracts are in Plugin contracts.

FieldRequiredDescription
providesYesscm, notify, or tracker
apiYesContract version, currently 1
entryYesPath to the ESM module in the package
capabilitiesNoscm has task, report, sync (empty means task); notify has send; tracker has task
matchesscmHost of the origin remote that the kit serves. notify and tracker don't use this field
credential.labelYesCredential name shown to the user
credential.help, url, env, optionalNoInstructions, the token creation page, a suggested environment variable, and permission to run without a secret
settings.<name>Nodefault, env, required, help. A tracker kit must have settings.project with required: true

guardrails ​

FieldValue
schema1
levelcompany or project
policyPath to the rules file in the package

Naming rules ​

text
<type>-<name>

Names are kebab-case, at most 64 characters, and start with the type prefix: skill-, agent-, kit-, prompt-, or harness-. A name must not contain the word claude or anthropic, or a reserved platform word (component names, official). Older names with an extra code in the middle, such as agent-tta-java-review, stay valid, but new names don't need one.

The namespace is not part of the name. The full name is <org>/<name>, in the style of an npm scope, for example acme/skill-review. A bare name such as skill-review means aiforge/skill-review. When Tara resolves a bare name, it looks only in aiforge, then in the caller's own organization, and never in another organization. This stops anyone from capturing a bare name with a community resource of their own. A community resource of another organization has to be addressed by its full name; if a bare name matches nothing but such a resource exists, Tara answers 404 with a hint, for example did you mean beta/skill-foo?. A bare dependency in a package's manifest resolves against aiforge, then the depending package's own organization. To depend on a resource of another organization, write its full name.

Channels ​

metadata.forge.org decides the channel of a resource.

org in the manifestChannelWho reviewsContent
aiforgeofficialPlatform staffCan include scripts, hooks, MCP
The submitter's organization slugorg (the organization's private store)An Admin or Owner of the organizationCan include scripts, hooks, MCP
Not setcommunityNo one; the automated scanner decidesMarkdown and configuration only, starts as private

A community resource lives in the submitter's own namespace. The legacy center field is still read: rnd becomes aiforge, any other value becomes the submitter's organization, and Tara adds a deprecation finding.

Structure by type ​

TypeAdditionally required
All typesREADME.md, and CHANGELOG.md with a ## <version> section; no CLAUDE.md at the root
agentAt least one agents/<name>.md
skill, promptAt least one skills/<name>/SKILL.md
kitAt least one of: .mcp.json, hooks/hooks.json, metadata.forge.phillip, metadata.forge.guardrails
harnesstemplate/CLAUDE.md and dependencies

Model catalog ​

A model isn't an install package. It's an entry in the catalog with the following fields.

FieldDescription
aliasShort kebab-case name, for example sonnet-std
engineThe engine, for example claude-code
modelModel identifier sent to the engine
taskreasoning, code, or light
purposeShort description of what it's for
rolesMatching job roles
statusactive (can be chosen for new use) or deprecated (being phased out)
recommendedThe model suggested by default for the task. A deprecated model can't be the recommendation

To choose a model for a project, run ph model use <alias>.

Further reading ​