Add OutreachAgent - #14
Conversation
|
@pagefarms is attempting to deploy a commit to the assafbar-gmailcom's projects Team on Vercel. A member of the Team first needs to authorize it. |
Greptile SummaryThis PR adds the OutreachAgent directory listing and attempts to record it in the changelog.
Confidence Score: 4/5This PR should not merge until the malformed changelog entry is separated into a valid JSON object. The changed changelog cannot be parsed by the statically rendered changelog page, so the repository build fails on the new content. Files Needing Attention: content/changelog.json
|
| Filename | Overview |
|---|---|
| content/agents/outreachagent.json | Adds a complete, unverified OutreachAgent listing with API-only access and outbound-email capabilities. |
| content/changelog.json | Adds the listing announcement without closing and separating it from the existing entry, breaking JSON parsing. |
Comments Outside Diff (1)
-
content/changelog.json, line 2-10 (link)Malformed changelog object boundary
When the changelog page is built, these adjacent properties leave
content/changelog.jsonsyntactically invalid, causingJSON.parseto throw and the Next.js build to fail.
Reviews (1): Last reviewed commit: "Merge branch 'main' into feat/add-outrea..." | Re-trigger Greptile
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
What kind of change?
content/agents/<slug>.jsonadded)For new listings
@outreachagent/sdk-tsat version 0.1.0. This entry declares API access only; it intentionally does not claim MCP access because@outreachagent/mcpis not currently published.Checklist
npx tsx scripts/validate-content.tspasses locally (362 agents, 20 categories, 0 violations)content/changelog.json"verified": false(maintainers verify & flip)Additional validation
npm test -- --run: 21/21 tests passedcontent/agents/outreachagent.jsonand the changelog entry