Add Neo Integration Catalog launch blog post

[foot]

Summary

• Draft launch announcement for the first iteration of the Neo Integration Catalog (Atlassian, Datadog, Honeycomb, Linear, PagerDuty, Supabase).
• Authored by neo-team.
• draft: true is set in frontmatter, so this is safe to merge ahead of launch day. Flip to draft: false when ready to publish.
• feature.png and meta.png generated via the /blog-meta-image skill (Neo template). Worth a final preview pass.

Test plan

• Local preview with make serve renders the post correctly
• Spot-check meta.png and feature.png look good
• Final copy review before flipping draft: false

[github-actions]

Social Media Review

content/blog/neo-integration-catalog/index.md

X — FAIL

• Over character limit: 264 chars vs. 255 limit
• Starts with product name: "Neo now has an Integration Catalog." is announcement-first, not setup-first
• Curiosity gap closed: Lists all 6 integrations, explains admin setup, and gives a concrete example — nothing left to read

LinkedIn — FAIL

• Single dense paragraph: LinkedIn requires multiple short paragraphs, not a text block
• Curiosity gap closed: Names all 6 integrations, explains MCP mechanism, and the admin-once model — post answers everything the article covers

Bluesky — missing

No social copy for Bluesky. Suggested copy included below.

---

Suggested copy

X (247/255 chars):

A latency spike shows up in Datadog. You pull up Honeycomb, copy findings into Linear, then check what Pulumi changed. Four tools before you have an answer.

Neo can now do all of that from one task. Here's what the Integration Catalog looks like.

LinkedIn (431/2950 chars):

A latency spike shows up in Datadog. You open four tabs: Honeycomb for traces, Linear to file a ticket, PagerDuty to check on-call, Pulumi to see what changed. That's most of the job before you've even diagnosed anything.

We built the Integration Catalog so Neo can reach those systems from a single task. Six integrations at launch, admin-configured once.

Here's what the workflow looks like and what's coming in the next batch.

Bluesky (255/300 chars):

When a latency spike shows up in Datadog, Neo can now check Honeycomb for traces and file a Linear ticket with the findings. No tab-hopping, no copy-pasting context between tools.

Here's how the Integration Catalog works and what six tools are connected.

---

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

[pulumi-bot]

Your site preview for commit 65029eb is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-18685-65029ebd.s3-website.us-west-2.amazonaws.com

[foot]

@claude please update the social posts in the frontmatter with the suggested copy from the social media review above

[pulumi-bot]

Claude finished @foot's task in 53s —— View job

---

Updated social media copy

• Read the current blog post frontmatter
• Apply suggested X, LinkedIn, and Bluesky copy from the social media review
• Commit and push the changes

All three social fields have been updated in content/blog/neo-integration-catalog/index.md:

• X/Twitter — replaced announcement-first copy with the curiosity-gap hook (247 chars, passes limit)
• LinkedIn — replaced the single dense paragraph with three short paragraphs addressing the FAIL criteria
• Bluesky — added (was missing entirely)
  · Branch

[foot]

/social-review

[github-actions]

Social Media Review

content/blog/neo-integration-catalog/index.md

X — PASS

• 248/255 chars
• Note: .social-check-output.txt reported 272 chars, but actual content is 248 — within the limit

LinkedIn — PASS

• 432/2950 chars
• Mild press-release tone in "We built the Integration Catalog…Six integrations at launch, admin-configured once" — one soft issue, below the fail threshold

Bluesky — PASS

• 256/300 chars
• "Neo can now check Honeycomb…" has light announcement language — one soft issue, below the fail threshold

---

To re-run the social media review after updates, comment: /social-review

[claude]

Docs review — neo-integration-catalog

Solid draft overall: the "what's wrong with my payments stack" scenario is concrete, the catalog is scannable, and the "what's next" section sets expectations honestly. Publishing readiness is in good shape (author, images, social copy, <!--more-->, meta all present). A few items worth a look before flipping draft: false.

Suggestions

Tag redundancy (index.md lines 11–16)

The sibling post content/blog/pulumi-neo/index.md uses only pulumi-neo (not a separate neo tag). Listing both here will split tag pages. Consider dropping neo for consistency:

tags:
    - ai
    - ai-agents
    - features
    - pulumi-neo

H2 phrasing for AEO (lines 41, 66, 74)

What's in the catalog / How it works / What's next are scannable but don't lead with the answer — per the AEO checklist, answer-first phrasing helps AI-search discoverability. Consider, for example: Six integrations in the launch catalog, How the Integration Catalog works, What's coming next: CLI, OAuth, and access controls. The Neo in action: one task, many systems heading is a good model.

Tense slip (line 52)

only sees the tools the vendor chose to expose — present-tense chooses reads better, since vendors continue to decide exposure over time, not as a one-time past event.

Each integration is a vendor-hosted MCP server. Neo calls the integration through a structured tool protocol and only sees the tools the vendor chooses to expose.

Marketing softener (line 72)

Neo skips it gracefully and continues with whatever's available, with no hard failures or broken sessions — gracefully + with whatever's available is a little hand-wavy. Tightening to a concrete outcome reads stronger:

**Neo uses integrations transparently.** When a task runs, the service decrypts the configured credentials and hands them to the agent runtime as MCP server auth. If an integration is misconfigured or its credentials have been rotated, Neo skips that integration and continues with the rest — the session doesn't fail.

Em-dash density

There are ~9 em-dashes in the body. Most are in bulleted term — definition lists, which is fine and idiomatic. No action needed, just flagging so you can confirm it reads as structured rather than stylistic overuse.

Social copy hook repetition (lines 20, 24, 30)

Twitter, LinkedIn, and Bluesky all open with A latency spike.... Not a blocker (each platform sees a different audience), but if you want to A/B the hook, Bluesky in particular could lead with a more distinct angle (e.g., the Linear/PagerDuty combination, or the admin-configured-once point).

Closing emoji (line 88)

Happy building. 👷 — house style generally avoids emojis. Matches tone of a product launch, but worth confirming with the blog editor if you want to keep it.

Publishing readiness

• social: block present (twitter / linkedin / bluesky)
• meta_image set (meta.png, 1200×628, current Neo template)
• feature_image set (feature.png, 1884×1256)
• <!--more--> break present (line 39) after a two-paragraph intro
• Author neo-team exists in data/team/team/ with avatar at static/images/team/neo-team.jpg
• Internal link /blog/pulumi-neo/ resolves
• External links (modelcontextprotocol.io, pulumi-cloud-requests) look correct
• No code examples → no chooser/choosable concern
• No screenshots → no alt-text / grey-border concern
• Title 71 chars with allow_long_title: true set
• meta_desc 138 chars, includes primary terms
• draft: true — intentional per PR description; flip on launch day

---

If you'd like me to take another pass after edits, or apply any of the suggestions above, mention @claude in a comment.

[github-actions]

Social Media Review

content/blog/neo-integration-catalog/index.md

X — PASS

• Character count: 247/255
• Note: "Neo can now do all of that from one task" reads announcement-y; the concrete setup and gap rescue it, but the pointer ("here's what it looks like") is on the soft side

LinkedIn — PASS

• Character count: 485/2950
• Note: "We built the Integration Catalog... Six integrations at launch, admin-configured once" reads like a press release; just one soft issue so it passes, but toning down the launch language would strengthen it

Bluesky — PASS

• Character count: 255/300
• Note: First sentence reveals the core capability (Honeycomb traces + Linear ticket) plus the benefit (no tab-hopping) before the pointer; gap still exists (4 unnamed tools, workflow details) but it's thin

---

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

[github-actions]

Social Media Review

content/blog/neo-integration-catalog/index.md

X — PASS

(Note: social-check-output.txt reports 272 chars, but the actual post text measures 247/255 — within limit. The higher number likely includes YAML indentation.)

LinkedIn — PASS

Bluesky — PASS

---

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

[github-actions]

Social Media Review

content/blog/neo-integration-catalog/index.md

X — PASS

LinkedIn — FAIL

Reasons:

• "Six integrations at launch, admin-configured once" reads like release notes, not curiosity-building
• Curiosity gap partially closed: reader learns what the feature does and how it is configured before clicking

Guidance:

• Replace the middle paragraph with something that names the hard part without revealing the answer

Bluesky — FAIL

Reasons:

• "We built a way for Neo to handle that whole sequence from one task" reveals the solution in the second paragraph
• Reads like a product announcement rather than a gap-and-pointer structure

Guidance:

• Withhold the answer; hint at the tricky part instead

---

Suggested copy

LinkedIn (492/2950 chars):

A latency spike shows up in Datadog. You open four tabs: Honeycomb for traces, Linear to file a ticket, PagerDuty to check on-call, Pulumi to see what changed. That's most of the job before you've even diagnosed anything.

We kept asking whether an agent could handle that whole sequence as a single task. The tricky part wasn't the API connections — it was figuring out the access model for a whole engineering team.

Here's what we built and what the first batch of integrations looks like.

Bluesky (275/300 chars):

A latency spike shows up in Datadog. Traces in Honeycomb, tickets in Linear, on-call in PagerDuty — four tabs before you can even diagnose anything.

We spent a long time on whether one task could cover all of those. The hard part wasn't the APIs. Here's what we figured out.

---

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

[foot]

@claude please update the social posts in the frontmatter with the suggested copy from the social media review above

[pulumi-bot]

Claude finished @foot's task in 55s —— View job

---

Updated social media copy

• Read trigger comment and identify required changes
• Read current blog post frontmatter
• Update LinkedIn copy (FAIL → suggested fix)
• Update Bluesky copy (FAIL → suggested fix)
• Commit and push changes

Applied the suggested copy from the most recent social review (2026-04-24T14:30:54Z):

• LinkedIn — replaced "We built the Integration Catalog…Six integrations at launch" with the curiosity-gap version that withholds the answer and focuses on the access model challenge
• Bluesky — replaced the solution-revealing copy with the "hard part wasn't the APIs" hook that leaves the key question open

X/Twitter was already passing — no changes made there.
· Branch

[aminix]

Nit: can we update the image so it's more obvious what we're integrating with? Maybe like the PG or Datadog logos, same style as below but Neo in the middle