chore: align manifest with canonical Pinata schema#3
Merged
Conversation
Cross-referenced PinataCloud/agent-templates. Two corrections: - Drop the template.version field I added in #2. The canonical manifest schema (documented inline in openclaw/basic/useful-assistant/manifest.json's _docs block) has no template.version. None of the shipped templates use it. Track template revisions through git tags instead. - Add the canonical "$schema" reference at the top of manifest.json. Every recent template (web-master, moonpay-defi-portfolio, moonpay-prediction-trader, useful-assistant) includes https://agents.pinata.cloud/schemas/manifest.v1.json — gives editors and CI a real schema to validate against. CI updated: enforce $schema is set, drop the template.version regex, and bound template.tags to ≤10 (per schema doc). CONTRIBUTING.md versioning section rewritten — no version field to bump, just tag releases. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #2. I cross-referenced
PinataCloud/agent-templates(specificallyweb-master,moonpay-defi-portfolio,moonpay-prediction-trader, and the schema docs embedded inuseful-assistant/manifest.json) and found two issues with what #2 produced:template.version: "1.0.0"template.version. Not in the schema_docsblock."$schema"field"$schema": "https://agents.pinata.cloud/schemas/manifest.v1.json".The
authorName/authorUrl/authorLogoUrlfields stay —useful-assistant's_docsblock calls thempartnerName/partnerUrl/partnerLogoUrl, but every actual shipped template (incl. the two MoonPay ones) usesauthor*. Soauthor*is the de facto canonical form.Changes
manifest.json: add$schema, removetemplate.version..github/workflows/validate.yml: enforce$schemamatches the canonical URL, drop thetemplate.versionregex check, boundtemplate.tagsto ≤10 (per the schema docs).CONTRIBUTING.md: rewrite the Versioning section — no template version field exists, so just track revisions via git tags. Same semver bump guidance.Out of scope but worth flagging
The schema also supports
tasks(cron-scheduled prompts injected as user messages).workspace/TOOLS.mdalready declaresdigestHourUtc: 14as the daily-digest hour, but nothing actually fires it — the heartbeat only runs on idle compute, not on schedule. WiringdigestHourUtcto a manifesttasksentry would be a real follow-up. Not doing it here to keep this PR scoped to the schema-correctness fix.Test plan
$schema(it should — every other template has it)tasksfollow-up before submission🤖 Generated with Claude Code