Skip to content

feat: add buffer-api Agent Skill (Buffer GraphQL scheduling for any agent) - #1627

Open
JPeetz wants to merge 2 commits into
anthropics:mainfrom
JPeetz:feat/buffer-api-skill
Open

JPeetz wants to merge 2 commits into
anthropics:mainfrom
JPeetz:feat/buffer-api-skill

Conversation

@JPeetz

@JPeetz JPeetz commented Aug 21, 2026

Copy link
Copy Markdown

Summary

Adds a portable Agent Skill for the Buffer GraphQL API — schedule, manage, and analyze social posts from any AI agent (Claude, Cursor, Codex, OpenClaw, Hermes, n8n).

What it covers

  • Account / organization / channel discovery
  • Post create / schedule (addToQueue / customScheduled) / edit / delete / reorder
  • Image / video / document / link assets (public-URL media), threads, first comments
  • Per-network metadata (Instagram post type + user tags, Pinterest board, threaded posts on Threads/X/Bluesky/Mastodon, LinkedIn/Facebook first comment)
  • Post retrieval + status polling (post(input:) → sent), cursor pagination
  • Ideas, post metrics, daily posting limits, post templates (preview)
  • Hard-won pitfalls: GraphQL-only, custom scalars ≠ ID, post() not getPost, sent not published, utf-8/latin-1, no blob upload, already-queued dedupe

Verification

Tested live against api.buffer.com with a real key: account and channels queries returned correctly; documented the custom-scalar gotcha found during testing.

Skill follows the Agent Skills spec (name + description + license frontmatter, progressive disclosure, bundled scripts).

@98zc5g5jyw-arch

Copy link
Copy Markdown

Babysit review — LGTM ✅

Buffer GraphQL reference is thorough, BUFFER_API_KEY env var (no hardcoded secrets), REST retirement note present. Structure matches repo conventions. Minor: consider noting rate limits for the free tier in api-reference.md.

@98zc5g5jyw-arch 98zc5g5jyw-arch left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed by Hermes Agent. Script quality is good (stdlib-only urllib, no shell=True, no hardcoded keys, timeout + HTTPError handling, UTF-8 encode guard). Blocking issue (same convention as #1628): repo convention requires a LICENSE.txt in every skill directory with 'license: Complete terms in LICENSE.txt' in frontmatter (see claude-api/docx/mcp-builder). This PR declares 'license: MIT' but ships no LICENSE.txt. Please add skills/buffer-api/LICENSE.txt. Non-blocking: description is 701 chars (within 1024 limit) — fine.

@JPeetz

JPeetz commented Aug 26, 2026

Copy link
Copy Markdown
Author

Addressed the review request: added skills/buffer-api/LICENSE.txt (MIT) and updated the frontmatter to license: Complete terms in LICENSE.txt, per the repo convention (matches claude-api/docx/mcp-builder). Pushed in commit 1117837. Also noted the free-tier rate-limits suggestion — happy to add it to api-reference.md if helpful.

JPeetz and others added 2 commits September 5, 2026 17:53
Portable Agent Skill for the Buffer GraphQL API. Schedule/manage/analyze social
posts across Instagram, Threads, LinkedIn, X, Facebook, Google Business,
Mastodon, YouTube, Pinterest, Bluesky from any agent. Covers account/org/channel
discovery, post CRUD + scheduling, public-URL media, per-network metadata
(threads/first-comment/IG post type/Pinterest board), status polling, ideas,
metrics, and hard-won pitfalls (custom scalars, post() not getPost, sent not
published, utf-8/latin-1).

Verified live against api.buffer.com (account + channels returned).
@JPeetz
JPeetz force-pushed the feat/buffer-api-skill branch from 1117837 to 1d851d8 Compare September 5, 2026 16:53
@JPeetz

JPeetz commented Sep 5, 2026

Copy link
Copy Markdown
Author

Rebased on latest upstream/main. The LICENSE.txt fix (commit 1117837) was pushed on Aug 26 — the CHANGES_REQUESTED review predates it. All requested changes are resolved. Could someone re-review? 🙏

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.

3 participants