Add recipe validation tests

- Add js-yaml for YAML parsing in tests
- Validate recipe schema matches Goose requirements:
  - Required fields: title, description
  - Content fields: instructions or prompt
  - Activities array present
- Test-specific validations:
  - x-news-digest mentions x_timeline_digest tool
  - x-conversations mentions x_conversations tool
  - Content filtering rules in instructions

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: nearestnabors

README.md

@@ -7,6 +7,7 @@ An MCP server that provides Twitter integration with rich UI components for [Goo
 Social media companies weaponize interfaces against humans (infinite scroll, notification anxiety, algorithmic rage bait). Agents are immune to psychological manipulation—they just execute.
 
 ASSA reclaims the social web by:
+
 - **Daily Digest**: Know what happened on Twitter without opening the app
 - **Post with Approval**: Agent drafts, you review a rich preview, then approve
 
@@ -30,6 +31,7 @@ ASSA reclaims the social web by:
 1. **Get your Arcade API key** at [arcade.dev](https://arcade.dev)
 
 2. Clone and install:
+
    ```bash
    git clone https://github.com/YOUR_USERNAME/assa-mcp
    cd assa-mcp
@@ -50,15 +52,17 @@ extensions:
     command: node
     args: ["/path/to/assa-mcp/dist/index.js"]
     env:
-      ARCADE_API_KEY: your_api_key_here      # <-- Required!
-      ARCADE_USER_ID: you@example.com        # <-- Required! Your Arcade account email
+      ARCADE_API_KEY: your_api_key_here # <-- Required!
+      ARCADE_USER_ID: you@example.com # <-- Required! Your Arcade account email
 ```
 
 **Important:**
+
 - `ARCADE_API_KEY` - Required. Get yours at [arcade.dev](https://arcade.dev)
 - `ARCADE_USER_ID` - Required. Must match the email address of your Arcade account. This is used to link OAuth authorizations to your account.
 
 #### Alternative: CLI setup
+
 ```bash
 goose configure
 # Select "Add Extension"
@@ -71,42 +75,46 @@ goose configure
 ## Usage
 
 ### Check Twitter Activity
+
 ```
 Check my Twitter mentions from the last 24 hours
 ```
 
 ### Get Timeline Digest
+
 ```
 Show me a digest of my Twitter timeline from the past 24 hours
 ```
 
 **Note:** Timeline digest requires Chrome running with remote debugging. See [Timeline Digest Setup](#timeline-digest-setup) below.
 
 ### Post a Tweet
+
 ```
 Post a tweet: "Just shipped a new feature! 🚀"
 ```
 
 ### Reply to Someone
+
 ```
 Reply to @anthropic_devs saying I'll share slides after the talk
 ```
 
 ## Tools
 
-| Tool | Description |
-|------|-------------|
-| `x_auth_status` | Check authentication, show connect button if needed |
-| `x_conversations` | Show unreplied mentions as a conversation inbox |
-| `x_dismiss_conversation` | Dismiss a conversation (reappears on new activity) |
-| `x_draft_tweet` | Create draft with preview |
-| `x_post_tweet` | Post after approval |
-| `x_timeline_digest` | Fetch and summarize your Following timeline (past 24h) |
-| `x_show_tweet` | Display a single tweet as a rich card with reply option |
+| Tool                     | Description                                             |
+| ------------------------ | ------------------------------------------------------- |
+| `x_auth_status`          | Check authentication, show connect button if needed     |
+| `x_conversations`        | Show unreplied mentions as a conversation inbox         |
+| `x_dismiss_conversation` | Dismiss a conversation (reappears on new activity)      |
+| `x_draft_tweet`          | Create draft with preview                               |
+| `x_post_tweet`           | Post after approval                                     |
+| `x_timeline_digest`      | Fetch and summarize your Following timeline (past 24h)  |
+| `x_show_tweet`           | Display a single tweet as a rich card with reply option |
 
 ## Timeline Digest Setup
 
-The timeline digest feature scrapes your Twitter Following timeline using your existing browser session. This is free (no API costs) and uses your logged-in state.
+The timeline digest feature accesses your X "Following" timeline using your existing browser session and Playwright. This is free (no API costs) and uses your logged-in state. (An API would be more robust, but X chooses to only make timeline API functionality available to industrial developers who can afford extortionate fees. So here we are, as hobbyists.)
 
 ### Prerequisites
 
@@ -118,72 +126,71 @@ The timeline digest feature scrapes your Twitter Following timeline using your e
 Before using timeline digest, start Chrome with the remote debugging port:
 
 **Mac:**
+
 ```bash
 /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
 ```
 
 **Windows:**
+
 ```bash
 "C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222
 ```
 
 **Linux:**
+
 ```bash
 google-chrome --remote-debugging-port=9222
 ```
 
-Then make sure you're logged into Twitter/X in that browser window.
+Then make sure you're logged into Twitter/X in that browser window. (I keep one open and minimized on startup.)
 
 ### Goose Recipes
 
 ASSA includes two recipes for scheduled automation:
 
-| Recipe | Description |
-|--------|-------------|
-| `x-news-digest.yaml` | Daily digest of your Following timeline (requires Chrome with remote debugging) |
-| `x-conversations.yaml` | Check and respond to mentions/conversations |
+| Recipe                 | Description                                                                     |
+| ---------------------- | ------------------------------------------------------------------------------- |
+| `x-news-digest.yaml`   | Daily digest of your Following timeline (requires Chrome with remote debugging) |
+| `x-conversations.yaml` | Check and respond to mentions/conversations                                     |
 
 #### Import a Recipe
 
-**Option 1: Generate a Deep Link**
+**Option 1: Follow a Deep Link**
 
 ```bash
 goose recipe deeplink recipes/x-news-digest.yaml
 goose recipe deeplink recipes/x-conversations.yaml
 ```
 
-This outputs a `goose://recipe?config=...` URL. Paste it in a browser to import into Goose Desktop.
+This outputs a `goose://recipe?config=...` URL. Paste it in a browser to preview what it will output in Goose Desktop.
 
 **Option 2: Import in Goose Desktop**
 
 1. Open **Goose Desktop**
 2. Click **Recipes** in the sidebar
-3. Click **Import** or browse for file
-4. Select a recipe from `recipes/`
+3. Click **Import Recipe** or browse for file
+4. Either past the link generated in Option 1 in the **Recipe Deeplink** input box, or choose a recipe from the `recipes/` folder in the **Recipe File** input field.
 
 **Option 3: Run via CLI**
 
+The outputs are in Markdown, enjoy!
+
 ```bash
 goose run --recipe recipes/x-news-digest.yaml
-goose run --recipe recipes/x-conversations.yaml
 ```
 
-#### Schedule a Recipe
+(Not recommended for `x-conversations.yaml`, which return nothing because MCP Apps are iframes.)
 
-After importing, schedule recipes to run automatically:
+#### Schedule a Recipe
 
-1. Open **Goose Desktop**
-2. Click **Scheduler** in the sidebar
-3. Click **Add** or **+**
-4. Select a recipe (e.g., "X News Digest")
-5. Set your preferred schedule
+After importing, on the **Recipes** screen:
 
-**Cron schedule examples:**
-- `0 9 * * *` — 9 AM daily
-- `0 9 * * 1-5` — 9 AM weekdays only
-- `0 9,18 * * *` — 9 AM and 6 PM daily
+1. Click the little clock icon next the the recipe you want to automate.
+2. In the **Add Schedule** modal, select the frequency and time you want the recipe to run.
+3. Click **Save**
 
-**Note:** The X News Digest requires Chrome running with `--remote-debugging-port=9222`.
+**Note:** X News Digest requires Chrome running with `--remote-debugging-port=9222`.
 
 ## Development
 
@@ -358,6 +365,7 @@ ASSA MCP Server
 Built for [MCP Connect 2026](https://mcpconnect.dev) by RL.
 
 Uses:
+
 - [Model Context Protocol](https://modelcontextprotocol.io)
 - [MCP-UI](https://mcpui.dev)
 - [Goose](https://github.com/block/goose)

bun.lock

@@ -35,10 +35,12 @@
   "devDependencies": {
     "@biomejs/biome": "^2.3.13",
     "@types/bun": "^1.2.0",
+    "@types/js-yaml": "^4.0.9",
     "@types/node": "^20.11.0",
     "@types/react": "^19.0.0",
     "@types/react-dom": "^19.0.0",
     "@vitejs/plugin-react": "^4.3.4",
+    "js-yaml": "^4.1.1",
     "tsx": "^4.7.0",
     "typescript": "^5.3.3",
     "ultracite": "^7.1.1",