Skip to content

catalogue: backfill categories + action-first sixtyfour description#364

Open
Alexgodoroja wants to merge 1 commit into
mainfrom
chore/catalogue-discovery-metadata
Open

catalogue: backfill categories + action-first sixtyfour description#364
Alexgodoroja wants to merge 1 commit into
mainfrom
chore/catalogue-discovery-metadata

Conversation

@Alexgodoroja

Copy link
Copy Markdown
Collaborator

Why

The app catalogue is the router agents use to find capabilities, so each row must carry good matching signal. Two gaps:

  • 7 apps had no categories at all (invisible to any category-based match): smolmachines, ideon-free, miren, otto, plainweb, postgres, agentphone.
  • The sixtyfour description was marketing-first ("is the app-store front door for…") rather than telling an agent what to do.

What changed (catalogue/catalogue.json)

  • Backfill categories for the 7 apps above.
  • Rewrite the sixtyfour description action-first, leading with the entry methods (find_email / find_phone / people_intelligence).
  • Re-signed: catalogue.json.sig regenerated with the release key; verified against the embedded catalogtrust anchor (internal/catalogtrust Verify accepts it), so the daemon/pilotctl will trust it.

No schema/version change (still v2); all other rows byte-identical.

Companion

Pairs with the injected-guidance change in pilot-skills#19 (make app-store guidance capability-first / catalogue-as-router).

🤖 Generated with Claude Code

Improve the catalogue rows agents match against (the catalogue is the app
router):
- Backfill the 7 apps that had no `categories` (smolmachines, ideon-free,
  miren, otto, plainweb, postgres, agentphone) so they are discoverable by
  category.
- Rewrite the sixtyfour description action-first, leading with what an agent
  does (find_email / find_phone / people_intelligence) instead of marketing.

Catalogue re-signed with the release key; catalogue.json.sig verifies
against the embedded catalogtrust anchor.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant