| name | recent-content-inventory |
| description | Inventory recent <BRAND> content from YouTube, X, docs PRs, changelog, and the <BRAND> blog for later customer-channel matching. Use this when the user asks what recent <BRAND> content exists, asks to match content to customer channels, or needs a structured content inventory artifact. |
Recent Content Inventory
Collect recent public/customer-safe content and normalize it into a temporary inventory that an agent can use while creating customer-channel share recommendations.
Sources
Start with these sources:
- YouTube: the feed at
$YOUTUBE_FEED_URL (for example https://www.youtube.com/feeds/videos.xml?channel_id=YOUR_CHANNEL_ID)
- X: direct X API v2 using
X_API_KEY as a bearer token in cloud agents; fall back to X_AI_BEARER_TOKEN only if explicitly needed. Include original posts, quote posts, and useful reposts amplified by , especially team/customer articles.
- Docs: recent merged PRs in
your-org/docs, plus changed docs paths
- Changelog:
https://app.your-brand.example/client_version?include_changelogs=true, matching the in-product changelog source
- Blog: RSS feed at
https://www.your-brand.example/blog/feed.xml
Do not use Typefully for this workflow. Typefully is for drafting/scheduling/managing posts, not source-of-truth content inventory.
Output
Write temporary artifacts under /tmp/customer-channel-share-recommendations/:
/tmp/customer-channel-share-recommendations/content-inventory-<start-YYYY-MM-DD>-to-<end-YYYY-MM-DD>.json
/tmp/customer-channel-share-recommendations/content-inventory-<start-YYYY-MM-DD>-to-<end-YYYY-MM-DD>.md
The inventory is run context, not a durable artifact. Keep final selected links and source-status notes in the share recommendations report instead of storing the full inventory in .
Scheduled workflows must not commit or persist the temporary inventory unless the user explicitly asks for a durable report.
