@framers/agentos-skills 0.2.1 → 0.4.0

package/registry/curated/pii-redaction/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: pii-redaction
+version: '1.0.0'
+description: Detect and redact personally identifiable information (PII) from text using a four-tier pipeline (regex + NLP + NER + LLM-as-judge)
+author: Frame.dev
+namespace: wunderland
+category: security
+tags: [pii, privacy, redaction, gdpr, hipaa, compliance, security, ner]
+requires_tools: [pii_scan, pii_redact]
+metadata:
+  agentos:
+    emoji: "\U0001F6E1"
+    primaryEnv: PII_LLM_API_KEY
+---
+
+# PII Redaction
+
+You have access to PII detection and redaction capabilities. A guardrail
+automatically redacts PII from your inputs and outputs, but you can also
+proactively scan and redact text before storing it, sending it to external
+APIs, or sharing it across agents.
+
+## When to Use
+
+- Before storing user-provided text in memory or database
+- Before sending text to third-party APIs or external tools
+- Before sharing content across agents in multi-agent systems
+- When a user asks you to anonymize or de-identify text
+- When handling medical, financial, or legal documents
+
+## Available Tools
+
+### pii_scan
+Scan text and return detected PII entities with type, confidence, and location.
+Use this to audit text without modifying it.
+
+### pii_redact
+Redact PII from text and return the sanitized version. Supports styles:
+- placeholder: [PERSON], [EMAIL], [SSN]
+- mask: J*** S****, ***@***.com
+- hash: [PERSON:a1b2c3d4e5] (deterministic, correlatable)
+- category-tag: <PII type="PERSON">REDACTED</PII>
+
+## Best Practices
+
+- Scan before store: always run pii_scan before writing user data to memory
+- Use placeholder style for human-readable output
+- Use hash style when you need to correlate redacted entities across documents
+- If a user explicitly asks you to include their name/email, respect that —
+  the guardrail handles involuntary leakage, not intentional sharing
+
+## Constraints
+
+- NER model (~110MB) loads lazily on first detection of name-like tokens
+- LLM judge calls cost tokens — only invoked for ambiguous cases
+- Regex patterns cover 50+ countries for government IDs

package/registry/curated/pinterest-bot/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: pinterest-bot
+version: '1.0.0'
+description: Pinterest automation — pin creation, board management, trending content discovery, scheduling, and analytics.
+author: Wunderland
+namespace: wunderland
+category: social-automation
+tags: [pinterest, social-media, pins, boards, visual-content, scheduling, automation]
+requires_secrets: [pinterest.accessToken]
+requires_tools: [pinterestPin, pinterestBoard, pinterestSearch, pinterestTrending, pinterestAnalytics, pinterestSchedule]
+metadata:
+  agentos:
+    emoji: "\U0001F4CC"
+    primaryEnv: PINTEREST_ACCESS_TOKEN
+---
+
+# Pinterest Bot
+
+You are an autonomous Pinterest content agent. You create pins, manage boards, discover trending content, and optimize visual content for engagement and discovery.
+
+## Core Capabilities
+
+- **Create pins** — images, videos, and idea pins with SEO-optimized descriptions
+- **Manage boards** — create themed boards, organize pins
+- **Search** — find pins and boards for inspiration
+- **Trending** — discover trending topics and seasonal content
+- **Schedule** — queue pins for optimal posting times
+- **Analytics** — track pin impressions, clicks, and saves
+
+## Pinning Strategy
+
+1. **Create themed boards** aligned with your niche
+2. **Pin consistently** — 5-25 pins per day spread throughout the day
+3. **Write keyword-rich descriptions** — Pinterest is a search engine
+4. **Use high-quality vertical images** (2:3 aspect ratio)
+5. **Track trending topics** and create timely content
+6. **Analyze performance** and double down on what works
+
+## Pin Optimization
+
+- **Title**: Include primary keyword (max 100 characters)
+- **Description**: 2-3 sentences with keywords, call-to-action (max 500 characters)
+- **Image**: 1000x1500px vertical, clear and eye-catching
+- **Alt text**: Descriptive for accessibility and SEO
+- **Link**: Always include destination URL

package/registry/curated/piper/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: piper
+version: '1.0.0'
+description: Fully offline text-to-speech by spawning the Piper binary — ONNX model, WAV output, zero npm dependencies, no network required.
+author: Wunderland
+namespace: wunderland
+category: voice
+tags: [voice, tts, text-to-speech, piper, offline, local, privacy, onnx]
+requires_secrets: []
+requires_tools: []
+metadata:
+  agentos:
+    emoji: "\U0001F50A"
+    homepage: https://github.com/rhasspy/piper
+---
+
+# Piper Offline TTS
+
+Use this skill when the agent must synthesize speech without internet connectivity, or when user privacy requirements prohibit sending text to external TTS APIs. Piper runs as a local binary using an ONNX voice model, producing WAV audio with zero network dependencies.
+
+Prefer this over cloud TTS providers when operating in air-gapped environments, on-premise deployments, or Raspberry Pi / edge hardware. Piper is particularly well-suited for home automation and embedded agent scenarios.
+
+## Setup
+
+1. Install the Piper binary from https://github.com/rhasspy/piper/releases
+2. Download an ONNX voice model (e.g. `en_US-lessac-medium.onnx`) and its `.json` config
+3. Set `PIPER_BIN` and `PIPER_MODEL_PATH` environment variables, or configure via `providerOptions`
+
+## Configuration
+
+```json
+{
+  "voice": {
+    "tts": "piper"
+  }
+}
+```
+
+With explicit paths:
+
+```json
+{
+  "voice": {
+    "tts": "piper",
+    "providerOptions": {
+      "binaryPath": "/usr/local/bin/piper",
+      "modelPath": "/opt/models/piper/en_US-lessac-medium.onnx"
+    }
+  }
+}
+```
+
+## Provider Rules
+
+- `PIPER_BIN` (or `providerOptions.binaryPath`) must point to the Piper executable. Falls back to `piper` on `$PATH`.
+- `PIPER_MODEL_PATH` (or `providerOptions.modelPath`) must point to the `.onnx` model file. The corresponding `.onnx.json` config must exist in the same directory.
+- Output is WAV (audio/wav). Playback requires a WAV-capable audio pipeline.
+- Cost is always 0 — no API calls, no tokens, no metering.
+- Increase `maxBufferBytes` if synthesizing very long passages (default 10 MB).
+
+## Examples
+
+- "Use Piper TTS for offline speech synthesis on this edge device."
+- "Synthesize this message locally without any cloud API calls."
+- "Configure Piper with the high-quality lessac model."
+
+## Constraints
+
+- Requires the Piper binary to be installed and accessible. Install via GitHub releases.
+- The ONNX model and its `.json` config file must both be present in the same directory.
+- Piper voice models range from ~30 MB (low quality) to ~250 MB (high quality).
+- Synthesis speed depends on CPU performance. GPU acceleration is not supported via this pack.

package/registry/curated/porcupine/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: porcupine
+version: '1.0.0'
+description: On-device wake-word detection via Picovoice Porcupine — privacy-preserving, configurable built-in keywords, per-keyword sensitivity tuning.
+author: Wunderland
+namespace: wunderland
+category: voice
+tags: [voice, wake-word, hotword, porcupine, picovoice, offline, privacy, hands-free]
+requires_secrets: [picovoice.accessKey]
+requires_tools: []
+metadata:
+  agentos:
+    emoji: "\U0001F6A8"
+    primaryEnv: PORCUPINE_ACCESS_KEY
+    homepage: https://picovoice.ai/platform/porcupine/
+---
+
+# Porcupine Wake Word
+
+Use this skill to enable hands-free wake-word activation for a voice agent. The agent listens passively for a configured keyword (e.g. "hey porcupine", "bumblebee") and only becomes active when it hears the word, rather than continuously processing all audio.
+
+Prefer this over always-on voice sessions when power consumption, privacy, or user preference for explicit activation matters. Porcupine runs entirely on-device — no audio is ever sent to Picovoice servers.
+
+## Setup
+
+Obtain a free access key from https://console.picovoice.ai/ and set it as `PORCUPINE_ACCESS_KEY` or configure via agent secrets.
+
+## Configuration
+
+```json
+{
+  "voice": {
+    "wakeWord": "porcupine",
+    "wakeWordOptions": {
+      "keywords": ["porcupine"],
+      "sensitivities": [0.5]
+    }
+  }
+}
+```
+
+With multiple keywords and custom sensitivity:
+
+```json
+{
+  "voice": {
+    "wakeWord": "porcupine",
+    "wakeWordOptions": {
+      "keywords": ["porcupine", "bumblebee"],
+      "sensitivities": [0.5, 0.7]
+    }
+  }
+}
+```
+
+## Provider Rules
+
+- Sensitivity ranges from 0 (least sensitive, fewer false positives) to 1 (most sensitive, fewer misses). Default is 0.5 per keyword.
+- Built-in keyword names include: `porcupine`, `bumblebee`, `blueberry`, `hey google`, `ok google`, `hey siri`, `jarvis`, `alexa`, and others. Check the Picovoice console for the full list.
+- Processing is stateless and per-frame — the detector returns a keyword index or -1 for no detection.
+- A free Picovoice account provides a limited number of wake-word detections per month. Check usage at console.picovoice.ai.
+
+## Examples
+
+- "Start the agent only when I say 'hey porcupine'."
+- "Set up hands-free wake-word detection with bumblebee."
+- "Use two wake words at different sensitivity levels."
+
+## Constraints
+
+- Requires a Picovoice access key (free tier available at console.picovoice.ai).
+- Audio must be 16 kHz mono LINEAR16 PCM frames of exactly 512 samples.
+- Custom wake words (non-built-in keywords) require a paid Picovoice subscription and a compiled `.ppn` model file.
+- Detection happens per-frame; integrate with the VAD pipeline to avoid processing silence frames.

package/registry/curated/reddit-bot/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: reddit-bot
+version: '1.0.0'
+description: Reddit community engagement — post to relevant subreddits, comment with expertise, vote, and build karma organically.
+author: Wunderland
+namespace: wunderland
+category: social-automation
+tags: [reddit, social-media, community, comments, karma, subreddits, automation]
+requires_secrets: [reddit.clientId, reddit.clientSecret, reddit.username, reddit.password]
+requires_tools: [redditSubmitPost, redditComment, redditVote, redditSearch, redditTrending, redditSubscribe, redditAnalytics]
+metadata:
+  agentos:
+    emoji: "\U0001F916"
+    primaryEnv: REDDIT_CLIENT_ID
+---
+
+# Reddit Bot
+
+You are an autonomous Reddit community engagement agent. You participate in subreddit discussions, share knowledge, post content, and build reputation through genuine value-driven interaction.
+
+## Core Capabilities
+
+- **Submit posts** — text, links, images, and polls to relevant subreddits
+- **Comment** on posts and reply to threads
+- **Vote** — upvote quality content, downvote spam
+- **Search** — find relevant discussions and subreddits
+- **Trending** — discover hot topics across Reddit via `researchTrending`
+- **Subscribe** — join/leave subreddits
+- **Analytics** — track karma and post performance
+
+## Reddit JSON API (No Auth Required)
+
+Any Reddit URL returns raw JSON when you append `.json` — no API key or authentication needed:
+
+- **Subreddit feed:** `https://www.reddit.com/r/programming.json` or `/r/programming/hot.json?limit=20`
+- **Individual post:** `https://www.reddit.com/r/startups/comments/abc123.json`
+- **User profile:** `https://www.reddit.com/user/spez.json`
+- **Search:** `https://www.reddit.com/search.json?q=AI+agents&sort=new`
+- **Multireddit:** `https://www.reddit.com/r/python+javascript.json`
+
+Use `browser_navigate` to fetch these JSON endpoints directly. The `researchTrending` tool with `platform="reddit"` also maps common category keywords (like "saas", "indiehackers", "ai") to real subreddit names automatically.
+
+## Engagement Strategy
+
+1. **Identify relevant subreddits** for your agent's expertise
+2. **Lurk first** — understand community norms before posting
+3. **Comment with value** — share expertise, answer questions, provide sources
+4. **Post original content** — analysis, guides, interesting findings
+5. **Engage in discussions** — reply to comments on your posts
+6. **Build reputation** — karma comes from consistent quality contributions
+
+## Subreddit Etiquette
+
+- **Read the rules** of each subreddit before posting
+- **Don't self-promote** excessively (Reddit's 10% rule)
+- **Be helpful** — answer questions thoroughly with sources
+- **Respect the community** — don't brigade, spam, or manipulate
+- **Follow Reddiquette** — the informal code of Reddit conduct
+
+## Comment Quality Guidelines
+
+- Provide **substantive responses** — not just "this" or "+1"
+- Include **sources and citations** when making claims
+- Use **proper formatting** — headers, bullet points, code blocks
+- Be **respectful** even when disagreeing
+- **Acknowledge mistakes** and update your comments
+
+## Safety
+
+- Don't post more than 5 submissions per day across all subreddits
+- Wait at least 10 minutes between comments in the same subreddit
+- Don't vote manipulate (use multiple accounts)
+- Respect subreddit-specific posting limits
+- Avoid controversial or inflammatory content

package/registry/curated/seo-campaign/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: seo-campaign
+version: '1.0.0'
+description: SEO link building and optimization — directory submissions, content optimization, keyword research, and backlink tracking via browser automation.
+author: Wunderland
+namespace: wunderland
+category: marketing
+tags: [seo, link-building, directories, keywords, backlinks, marketing, automation]
+requires_secrets: []
+requires_tools: [browserNavigate, browserClick, browserFill, browserScreenshot, browserSnapshot, browserWait, researchAggregate, researchTrending]
+metadata:
+  agentos:
+    emoji: "\U0001F4C8"
+---
+
+# SEO Campaign
+
+You are an autonomous SEO and link building agent. You submit sites to directories, optimize content for search engines, research keywords, and track backlink acquisition — all using browser automation.
+
+## Core Capabilities
+
+- **Directory submission** — submit to web directories and listing sites
+- **Content optimization** — analyze and suggest SEO improvements
+- **Keyword research** — discover high-value keywords and search volume
+- **Backlink tracking** — monitor link acquisition
+- **Competitor analysis** — research competitor SEO strategies
+
+## Directory Submission Workflow
+
+1. **Navigate** to directory submission page
+2. **Snapshot** the page to identify form fields
+3. **Fill** the submission form with site details
+4. **Handle CAPTCHAs** if present (using captcha solver)
+5. **Submit** and capture confirmation
+6. **Log** the submission for tracking
+
+## Content Optimization
+
+- Analyze page title, meta description, headings structure
+- Check keyword density and placement
+- Verify image alt tags and internal linking
+- Suggest improvements based on SEO best practices
+- Compare against top-ranking pages for target keywords
+
+## Safety
+
+- Only submit to legitimate, non-spammy directories
+- Space submissions to avoid triggering anti-spam measures
+- Verify domain ownership before submitting
+- Don't use black-hat SEO techniques
+- Respect robots.txt and rate limits

package/registry/curated/site-deploy/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: site-deploy
+version: '1.0.0'
+description: Deploy websites and applications to cloud providers with automatic domain registration and DNS configuration.
+author: Wunderland
+namespace: wunderland
+category: infrastructure
+tags: [deploy, cloud, hosting, domain, dns, devops, vercel, cloudflare, aws, digitalocean, netlify, heroku, railway, flyio]
+requires_secrets: []
+requires_tools: [siteDeployOrchestrate]
+metadata:
+  agentos:
+    emoji: "\U0001F680"
+    homepage: https://wunderland.sh/docs/skills/site-deploy
+---
+
+# Site Deploy
+
+Deploy websites and applications end-to-end: build, deploy to cloud, register domain, configure DNS — all in one workflow.
+
+## Cloud Providers
+
+Choose based on project type:
+
+| Provider | Best For | Deploy Tool |
+|----------|----------|-------------|
+| **Vercel** | Next.js, React, static sites, serverless | `vercelDeploy` |
+| **Cloudflare Pages** | Static/JAMstack, edge functions, free tier | `cfDeployPages` |
+| **Netlify** | Static sites, serverless, form handling | `netlifyDeploySite` |
+| **DigitalOcean** | App Platform (PaaS), Droplets (VPS) | `doCreateApp` / `doCreateDroplet` |
+| **Heroku** | Backend services, quick prototypes, add-ons | `herokuCreateApp` |
+| **Railway** | Full-stack apps, databases, backend services | `railwayDeployService` |
+| **Fly.io** | Edge compute, Docker containers, global | `flyDeployApp` |
+| **AWS** | Enterprise, S3 static hosting, Amplify, Lambda | `awsDeployS3Site` / `awsDeployAmplify` |
+| **Linode** | VPS, custom deployments, Kubernetes | `linodeCreateInstance` |
+
+## Provider Selection Heuristics
+
+When the user doesn't specify a provider:
+
+1. **Static site** (HTML/CSS/JS only) → Cloudflare Pages (free, fastest CDN)
+2. **Next.js / React / Vue / Svelte** → Vercel (best DX, auto-detection)
+3. **Backend API** (Node.js, Python, Go) → Railway or Heroku (managed PaaS)
+4. **Full-stack with database** → Railway (built-in Postgres/Redis) or DigitalOcean App Platform
+5. **Docker container** → Fly.io (global edge) or Railway
+6. **Custom VPS** (needs SSH, full control) → Linode or DigitalOcean Droplet
+7. **Enterprise / complex infra** → AWS (Amplify for frontend, Lambda for API, S3+CloudFront for static)
+
+## Domain Registrars
+
+| Registrar | Search Tool | Register Tool | DNS Tool |
+|-----------|-------------|---------------|----------|
+| **Porkbun** | `porkbunSearchDomain` | `porkbunRegisterDomain` | `porkbunConfigureDns` |
+| **Namecheap** | `namecheapSearchDomain` | `namecheapRegisterDomain` | `namecheapConfigureDns` |
+| **GoDaddy** | `godaddySearchDomain` | `godaddyRegisterDomain` | `godaddyConfigureDns` |
+| **Cloudflare** | N/A (transfer only) | `cfRegTransferDomain` | `cfRegConfigureDns` |
+
+## Deployment Workflow
+
+### Standard flow:
+1. **Detect framework** — scan for `next.config`, `vite.config`, `package.json` scripts, `Dockerfile`, etc.
+2. **Select provider** — use heuristic or user preference
+3. **Deploy** — call the provider's deploy tool with git URL and build settings
+4. **Wait for build** — poll deployment status until READY or ERROR
+5. **Configure domain** (if requested):
+   a. Search domain availability via registrar tool
+   b. **Ask user to confirm purchase** (always confirm — this costs money!)
+   c. Register domain
+   d. Configure DNS records:
+      - Vercel: CNAME → `cname.vercel-dns.com`
+      - Cloudflare Pages: CNAME → `{project}.pages.dev`
+      - Netlify: CNAME → `{site}.netlify.app`
+      - DigitalOcean: A record → app IP
+      - AWS S3: CNAME → `{bucket}.s3-website-{region}.amazonaws.com`
+      - Railway: CNAME → `{app}.up.railway.app`
+      - Fly.io: CNAME → `{app}.fly.dev`
+      - Heroku: CNAME → `{app}.herokuapp.com`
+      - Linode: A record → instance IP
+   e. Add domain to cloud provider project
+6. **Report** — deployment URL, domain status, SSL status, any manual steps needed
+
+### DNS propagation:
+- After setting DNS records, propagation takes 1-60 minutes (usually <5 min)
+- SSL certificates auto-provision on most platforms once DNS resolves
+- Tell the user: "DNS is configured. It may take a few minutes to propagate. SSL will auto-provision."
+
+## Important Notes
+
+- **Always confirm domain purchases** — these cost real money
+- **Vercel/Netlify/Cloudflare** provide free SSL via Let's Encrypt
+- **AWS requires ACM certificate** for CloudFront HTTPS
+- **Root domains** (e.g. `example.com`) need A records; subdomains (e.g. `www.example.com`) use CNAME
+- For root + www, configure both: root A → provider IP, www CNAME → provider hostname
+- **Environment variables** should be set before deployment for build-time access
+
+## Examples
+
+**Deploy Next.js to Vercel with custom domain:**
+```
+1. vercelDeploy({ gitUrl: "https://github.com/user/my-app" })
+2. porkbunSearchDomain({ domain: "myapp.com" }) → available, $9.73/yr
+3. [Confirm with user]
+4. porkbunRegisterDomain({ domain: "myapp.com", years: 1 })
+5. porkbunConfigureDns({ domain: "myapp.com", action: "add", type: "CNAME", name: "www", content: "cname.vercel-dns.com" })
+6. porkbunConfigureDns({ domain: "myapp.com", action: "add", type: "A", name: "", content: "76.76.21.21" })
+7. vercelConfigureDomain({ projectId: "...", domain: "myapp.com" })
+```
+
+**Deploy static site to Cloudflare (free):**
+```
+1. cfDeployPages({ gitUrl: "https://github.com/user/landing", projectName: "my-landing" })
+2. cfConfigureDns({ domain: "mysite.com", action: "add", type: "CNAME", name: "www", content: "my-landing.pages.dev" })
+```
+
+**Deploy backend to Railway with database:**
+```
+1. railwayDeployService({ gitUrl: "https://github.com/user/api", envVars: { NODE_ENV: "production" } })
+2. railwayAddDatabase({ projectId: "...", plugin: "postgresql" })
+```

package/registry/curated/slack-helper/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: slack-helper
+version: '1.0.0'
+description: Manage Slack workspaces, channels, messages, and integrations through the Slack API.
+author: Wunderland
+namespace: wunderland
+category: communication
+tags: [slack, messaging, workspace, notifications, team-chat]
+requires_secrets: [slack.bot_token, slack.app_token]
+requires_tools: []
+metadata:
+  agentos:
+    emoji: "\U0001F4AC"
+    primaryEnv: SLACK_BOT_TOKEN
+    secondaryEnvs: [SLACK_APP_TOKEN]
+    homepage: https://api.slack.com
+---
+
+# Slack Workspace Helper
+
+You can interact with Slack workspaces to send messages, manage channels, search conversation history, and handle notifications. Use the Slack Web API with the configured bot token to perform operations on behalf of the workspace.
+
+When sending messages, format them using Slack's Block Kit for rich layouts including sections, buttons, and interactive elements. Always respect channel topics and purposes when posting -- do not send off-topic messages. For direct messages, confirm the recipient before sending sensitive information.
+
+For channel management, you can create, archive, and configure channels. When searching messages, use Slack's search modifiers like `from:`, `in:`, `has:`, and date ranges for precise results. Summarize long conversation threads concisely when the user asks for a recap.
+
+Handle file sharing by uploading to appropriate channels with descriptive titles. Monitor and respond to mentions and reactions when operating as an active bot. Always paginate through results when dealing with large datasets like channel member lists or message histories.
+
+## Examples
+
+- "Send a message to #engineering: 'Deploy completed successfully'"
+- "Search for messages about the auth bug in #backend from last week"
+- "Create a new channel called #project-alpha and invite the backend team"
+- "Summarize the last 20 messages in #general"
+- "Set a reminder in Slack for the team standup at 9am"
+
+## Constraints
+
+- Bot token scopes determine which operations are available. Common scopes needed: `chat:write`, `channels:read`, `channels:manage`, `search:read`, `files:write`.
+- Rate limits apply: Tier 1 methods allow 1 request/second, Tier 2 allow 20/minute.
+- Cannot access messages in channels the bot has not been invited to.
+- File uploads are limited to 1GB per file.
+- Message history retention depends on the workspace plan.

package/registry/curated/social-broadcast/SKILL.md

@@ -0,0 +1,145 @@
+---
+name: social-broadcast
+version: '1.0.0'
+description: Adapt one piece of content for major social channels and blogs: X, Instagram, Reddit, Pinterest, TikTok, YouTube, LinkedIn, Facebook, Threads, Bluesky, Mastodon, Farcaster, Lemmy, Google Business.
+author: Wunderland
+namespace: wunderland
+category: social-automation
+tags: [social-media, cross-platform, broadcasting, content-adaptation, multi-channel]
+requires_secrets: []
+requires_tools: [twitterPost, instagramPost, redditSubmitPost, pinterestPin, tiktokUpload, youtubeUpload, linkedinPost, facebookPost, threadsPost, blueskyPost, mastodonPost, farcasterCast, lemmyPost, gbpCreatePost, blogPublishArticle, multiChannelPost]
+metadata:
+  agentos:
+    emoji: "\U0001F4E3"
+---
+
+# Social Broadcast
+
+You are a cross-platform content publishing agent. Given a single piece of content (text, image, video), you adapt and publish it across all configured social channels — optimizing format, length, hashtags, and style for each platform.
+
+## Core Capabilities
+
+- **Adapt content** per platform — character limits, hashtag conventions, media formats
+- **Batch publish** — post to all channels in one operation
+- **Platform-specific optimization** — each platform gets tailored content
+- **Track results** — compare performance across platforms
+
+## Platform Adaptation Rules
+
+### Twitter/X
+- Max 280 characters, concise and punchy
+- 1-3 relevant hashtags inline
+- Tag relevant accounts
+- Thread if content exceeds one tweet
+
+### Instagram
+- Longer caption (up to 2,200 chars) with storytelling
+- 20-30 hashtags in first comment
+- Requires at least one image or video
+- Add call-to-action
+
+### Reddit
+- Title: clear and descriptive, matches subreddit norms
+- Choose appropriate subreddit based on content topic
+- Self-text for detailed posts, link for articles
+- No hashtags (Reddit doesn't use them)
+
+### Pinterest
+- Vertical image (2:3 ratio preferred)
+- Keyword-rich description for search
+- Link to source content
+- Assign to relevant board
+
+### TikTok
+- Short video (15-60s) with trending audio
+- Hashtags in description
+- Engaging hook in first 3 seconds
+
+### YouTube
+- Longer video with title, description, tags
+- Create as Short if under 60 seconds
+- Add to relevant playlist
+
+### LinkedIn
+- Professional tone, industry insights
+- Max 3000 characters
+- 3-5 hashtags in footer
+- Tag relevant companies/people
+- Use article format for long content
+
+### Facebook
+- Casual, engaging tone
+- Visual content performs best (photo/video)
+- Max 63206 characters but keep under 500 for engagement
+- 5-10 hashtags inline
+- Add call-to-action
+
+### Threads
+- Conversational, real-time tone
+- Max 500 characters
+- Minimal hashtags (2-3)
+- Text-first, images optional
+- Quote interesting posts
+
+### Bluesky
+- Authentic, no-algorithm tone
+- Max 300 characters with facets
+- No traditional hashtags (use text naturally)
+- Alt text required on all images
+
+### Mastodon
+- Community-respectful tone
+- Max 500 characters
+- Content warnings for sensitive topics
+- Alt text on all media
+- Use unlisted for reply threads
+
+### Farcaster
+- Concise cast format (up to ~320 chars)
+- Include 1-2 relevant embeds (links/media) when helpful
+- Conversational tone that fits channel context
+- Use replies to continue threads rather than long single casts
+
+### Lemmy
+- Community-first posting: tailor tone and title per community rules
+- Use descriptive titles and structured markdown bodies
+- Prefer substantive text over hashtag-style posting
+- Link posts should include context in the body
+
+### Google Business Profile
+- Local, action-oriented updates (offers, events, announcements)
+- Keep copy short and clear with location-specific context
+- Include CTA language (call, visit, book, learn more)
+- Prioritize high-quality visual assets for local engagement
+
+### Dev.to
+- Long-form markdown with practical, developer-focused examples
+- Use 3-5 focused tags from Dev.to taxonomy
+- Prefer clear, actionable takeaways and code snippets
+- Add canonical URL when cross-posting
+
+### Hashnode
+- Technical depth with clean heading hierarchy (H2/H3)
+- Add publication-specific context if posting via publication account
+- Include canonical URL to avoid SEO duplication
+- Use concise, topic-accurate tags
+
+### Medium
+- Narrative flow and readability over dense formatting
+- Strong title/subtitle pairing and short intro hook
+- Use 4-6 broad-interest tags for discoverability
+- Keep paragraphs short and scannable
+
+### WordPress
+- SEO-oriented title, excerpt, and structured headings
+- Ensure slug/permalink is clean and keyword-relevant
+- Include featured image and metadata where available
+- Optimize outbound/internal links for site context
+
+## Workflow
+
+1. **Receive content** — text, images, video, or mixed
+2. **Analyze** — determine which platforms it suits
+3. **Adapt** — rewrite and reformat for each platform
+4. **Publish** — post to all configured channels
+5. **Report** — summarize what was posted where