Missing Central Registry/Manifest for Quickstarts Discoverability

[Ashutosh0x]

Similar to anthropic-cookbook having registry.yaml and claude-plugins having plugin.json (manifests), anthropic-quickstarts lacks a central machine-readable index.

This omission makes it difficult for external tools, GUIs, or scripts to auto-discover available quickstarts, check metadata (like tags or compatibility), and validate structure.

Proposal:
Add a registry.yaml or quickstarts.json at the root, listing all subdirectories and their metadata (tags, description, author).

CC: @dhollman (relevant for ecosystem standardization/discoverability across plugins/cookbooks/quickstarts)

[Ashutosh0x]

To move this forward, I've drafted a potential registry.yaml structure based on the existing anthropic-cookbook schema. This would allow tools to programmatically list and categorize the quickstarts.

# registry.yaml proposal
recipes: 
  - name: Browser Use Demo
    path: browser-use-demo
    description: Control a web browser using Claude 3.5 Sonnet to perform complex navigation and extraction tasks.
    categories: [Browser, Computer Use]
  - name: Computer Use Demo
    path: computer-use-demo
    description: The official reference implementation for Claude's ability to interact with a desktop environment.
    categories: [Computer Use, OS]
  - name: Autonomous Coding
    path: autonomous-coding
    description: Examples of Claude performing end-to-end coding tasks autonomously.
    categories: [Coding, Agents]
  - name: Financial Data Analyst
    path: financial-data-analyst
    description: Multi-step financial analysis using tool-calling to fetch and process market data.
    categories: [Financial, Data Analysis]
  - name: Customer Support Agent
    path: customer-support-agent
    description: A template for building intelligent customer support workflows.
    categories: [Support, Agents]

Standardizing on the recipes key (same as cookbook) would make cross-repo discovery even easier. Would this structure work for the team?