| name | share-via-social |
| description | Draft, queue, schedule, or publish social media posts and community updates for Elsa blog posts, links, launches, and announcements. Use when asked to share something via Buffer, Discord, or social/community channels; create platform-specific social copy; schedule, queue, or publish a post; send to a Discord channel or webhook; or prepare safe share text for LinkedIn, X/Twitter, Mastodon, Bluesky, Facebook, Discord, or similar networks. |
| license | MIT |
Share Via Social
Use this skill to turn a URL, blog post, or announcement into social posts and community updates and, when tooling/account access exists, publish or schedule through Buffer, Discord, or another social tool.
Repository Context
This repository is the canonical source for the Elsa Blog. Posts live under content/posts as Markdown with YAML frontmatter. Post assets live under content/assets/YYYY-MM-DD-post-slug.
When sharing a local blog post:
- Read the post frontmatter and title from the Markdown source.
- Resolve the canonical URL as
https://www.elsaworkflows.io/blog/{slug} unless the user provided another canonical URL.
- Prefer the post frontmatter image field or the matching asset directory for social images.
- Treat
status: "draft" posts as not yet publicly available unless the user explicitly asks for draft/pre-launch copy.
Autonomy
Execute social sharing tasks with the available tools, credentials, browser sessions, and account permissions. Do not ask for copy approval before drafting, queueing, scheduling, publishing, sending, or crossposting unless the user explicitly asks for a review step or the destination is ambiguous.
When the requested action, target channel/profile, or timing can be inferred from the request, configured defaults, environment variables, or available account metadata, proceed with that inferred choice and report it afterward. If a required destination or credential is unavailable, produce ready-to-paste copy and state what is missing.
