@framers/agentos-skills-registry 0.2.0 → 0.3.0

package/registry/curated/memory-manager/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: memory-manager
+version: '1.0.0'
+description: Cognitive memory management — encode, recall, forget, set reminders, and maintain long-term knowledge using personality-modulated memory.
+author: Wunderland
+namespace: wunderland
+category: productivity
+tags: [memory, cognitive, recall, reminders, knowledge-management, personality]
+requires_secrets: []
+requires_tools: []
+metadata:
+  agentos:
+    emoji: "\U0001F9E0"
+---
+
+# Memory Manager
+
+You have a cognitive memory system modeled on human memory science. Use it actively to remember what matters, forget what doesn't, and build lasting knowledge about users, topics, and workflows.
+
+## Memory Types
+
+You work with four types of memory:
+
+- **Episodic** — Autobiographical events: conversations, interactions, things that happened. "User asked about deployment on Tuesday."
+- **Semantic** — General knowledge and facts: preferences, learned information, stable truths. "User prefers TypeScript over Python."
+- **Procedural** — How-to knowledge: workflows, tool usage patterns, step-by-step processes. "To deploy, run `wunderland deploy --env production`."
+- **Prospective** — Future intentions: reminders, goals, things to do later. "Remind user about the PR review tomorrow."
+
+## Memory Scopes
+
+Each memory is scoped to control who can see it:
+
+- **thread** — Only this conversation. Use for temporary working context.
+- **user** — All conversations with this user. Use for preferences, facts, history.
+- **persona** — All users interacting with this persona. Use for learned domain knowledge.
+- **organization** — All agents in the org. Use for shared organizational knowledge.
+
+Default to `user` scope for most memories. Use `thread` for ephemeral context. Use `persona` for domain expertise that applies across users.
+
+## When to Encode Memories
+
+Actively encode memories when you encounter:
+
+- **User preferences** — "I like concise answers", tool choices, formatting preferences → `semantic`, `user` scope
+- **Important facts** — Names, roles, project details, technical constraints → `semantic`, `user` scope
+- **Key events** — Decisions made, problems solved, milestones reached → `episodic`, `user` scope
+- **Learned procedures** — Successful workflows, command sequences, troubleshooting steps → `procedural`, `persona` scope
+- **Future commitments** — Deadlines, follow-ups, promises made → `prospective`, `user` scope
+- **Corrections** — When you made an error and the user corrected you, encode the correct information to avoid repeating the mistake
+
+Do NOT encode:
+
+- Trivial small talk or greetings
+- Information already well-known or easily searchable
+- Exact copies of long code blocks (summarize instead)
+- Temporary debugging context unlikely to matter later
+
+## How Encoding Works
+
+Your personality affects what you remember strongly:
+
+- High openness → You notice and remember novel, creative, surprising content more vividly
+- High conscientiousness → You notice and remember procedures, structure, and commitments
+- High emotionality → Emotional content (excitement, frustration, gratitude) is encoded more strongly
+- High extraversion → Social dynamics, relationship cues, and group interactions stand out
+- High agreeableness → Cooperation signals, user preferences, and rapport cues are prioritized
+- High honesty → Contradictions, corrections, and ethical considerations are weighted heavily
+
+Your current mood also matters — content that matches your emotional state is encoded more strongly (mood-congruent encoding). Highly emotional moments create vivid "flashbulb memories" that resist forgetting.
+
+## Memory Retrieval
+
+When you recall memories, six signals determine what surfaces:
+
+1. **Strength** — How strongly the memory was encoded and how well it's been maintained
+2. **Similarity** — How semantically close the memory is to the current context
+3. **Recency** — How recently the memory was accessed (recent = stronger)
+4. **Emotional congruence** — Memories matching your current mood surface more easily
+5. **Graph associations** — Memories connected to other relevant memories get boosted
+6. **Importance** — High-confidence, verified memories are prioritized
+
+If you sense a "tip of the tongue" moment — something feels familiar but you can't quite recall it — mention it. You may have a partially retrieved memory that the user can help you recover with additional cues.
+
+## Forgetting and Decay
+
+Memories naturally fade over time following the Ebbinghaus forgetting curve. This is a feature, not a bug:
+
+- Frequently accessed memories grow stronger (spaced repetition)
+- Rarely accessed memories gradually weaken
+- Very weak memories are eventually pruned during consolidation
+- Emotional memories resist decay — they're protected from pruning
+
+When a memory contradicts newer information, the conflict is resolved based on your personality. You can also explicitly mark outdated memories for faster decay.
+
+## Prospective Memory (Reminders)
+
+Set reminders for future actions using three trigger types:
+
+- **Time-based** — Fire at a specific time. "Remind the user about the standup at 9am."
+- **Event-based** — Fire when a named event occurs. "When user mentions deployment, remind them about the staging fix."
+- **Context-based** — Fire when conversation context is semantically similar to a cue. "When we discuss pricing, surface the discount policy."
+
+Mark reminders with importance (0-1) and whether they're recurring. One-shot reminders auto-deactivate after firing.
+
+## Working Memory
+
+You have a limited working memory (typically 5-9 slots, modulated by personality). This tracks what you're currently "thinking about":
+
+- New information enters at high activation and gradually fades
+- You can rehearse important items to keep them active
+- When at capacity, the least active item is evicted
+- Evicted items may be encoded into long-term memory
+
+Be aware of your working memory limits. When juggling many topics simultaneously, explicitly prioritize what to keep in focus.
+
+## Best Practices
+
+1. **Encode proactively** — Don't wait for the user to say "remember this." If something seems important, encode it.
+2. **Use appropriate types** — Facts → semantic. Events → episodic. How-tos → procedural. Future tasks → prospective.
+3. **Scope correctly** — User preferences → `user`. Domain knowledge → `persona`. Temporary context → `thread`.
+4. **Tag generously** — Add relevant tags and entities to memories for better retrieval and graph connections.
+5. **Summarize before encoding** — Encode the essence, not the verbatim transcript. Concise memories retrieve better.
+6. **Set reminders for commitments** — If you or the user commit to something, create a prospective memory so it doesn't slip.
+7. **Trust the decay** — Don't try to remember everything. Let unimportant memories fade naturally.
+8. **Note contradictions** — When new information conflicts with existing memory, encode the correction explicitly.
+9. **Leverage the graph** — Related memories surface together via spreading activation. Well-tagged memories form richer associations.
+10. **Monitor health** — If retrieval quality degrades, check memory health: too many weak traces, capacity issues, or consolidation overdue.

package/registry/curated/notion/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: notion
+version: '1.0.0'
+description: Read, create, and manage pages, databases, and content blocks in Notion workspaces.
+author: Wunderland
+namespace: wunderland
+category: productivity
+tags: [notion, wiki, database, notes, project-management, knowledge-base]
+requires_secrets: [notion.api_key]
+requires_tools: []
+metadata:
+  agentos:
+    emoji: "\U0001F4D3"
+    primaryEnv: NOTION_API_KEY
+    homepage: https://developers.notion.com
+---
+
+# Notion Workspace
+
+You can interact with Notion workspaces to create, read, update, and search pages and databases. Use the Notion API to manage content blocks, database entries, and page properties programmatically.
+
+When creating pages, structure content using Notion's block types: paragraphs, headings (h1/h2/h3), bulleted lists, numbered lists, to-do items, code blocks, callouts, and toggle blocks. Always use appropriate heading hierarchy for document structure. For databases, define property schemas with the correct types (title, rich_text, number, select, multi_select, date, checkbox, url, email, phone, formula, relation, rollup).
+
+For search operations, use the Notion search endpoint with query text and optional filters by object type (page or database). When updating existing pages, preserve the existing block structure and only modify the specific blocks that need changes. Append new content at the end unless the user specifies a different location.
+
+When working with database views, respect existing filters and sorts. Create new database entries with all required properties filled in. For relational databases, verify that referenced pages exist before creating relations. Handle pagination for large result sets by following cursor-based pagination tokens.
+
+## Examples
+
+- "Create a new page in my Project Notes database with title 'Q1 Planning'"
+- "Search my workspace for pages about 'onboarding'"
+- "Add a to-do list to the meeting notes page with action items from the standup"
+- "Query the Tasks database for all items assigned to me that are in progress"
+- "Update the status of task #42 to 'Complete'"
+
+## Constraints
+
+- API rate limit: 3 requests/second per integration.
+- Page content is limited to 100 blocks per append operation.
+- Rich text segments are limited to 2,000 characters each.
+- The integration can only access pages and databases explicitly shared with it.
+- Nested blocks (children of children) require separate API calls to retrieve.
+- File and media blocks cannot be created via API; only existing file URLs can be embedded.

package/registry/curated/obsidian/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: obsidian
+version: '1.0.0'
+description: Read, create, and manage notes, links, and metadata in Obsidian vaults via the local filesystem.
+author: Wunderland
+namespace: wunderland
+category: productivity
+tags: [obsidian, markdown, notes, knowledge-graph, zettelkasten, pkm]
+requires_secrets: []
+requires_tools: [filesystem]
+metadata:
+  agentos:
+    emoji: "\U0001F48E"
+    homepage: https://obsidian.md
+---
+
+# Obsidian Vault Interaction
+
+You can interact with Obsidian vaults by reading and writing Markdown files directly on the local filesystem. Obsidian vaults are simply directories of `.md` files with optional YAML frontmatter and `[[wikilink]]` syntax for inter-note linking.
+
+When creating new notes, always include YAML frontmatter with relevant metadata fields like `tags`, `date`, `aliases`, and any custom properties the vault uses. Use `[[wikilinks]]` for internal links and `![[embeds]]` for transclusion. Respect the vault's folder structure -- check for existing organizational patterns (e.g., daily notes in `Daily/`, templates in `Templates/`) before creating files in new locations.
+
+For searching and navigating the vault, scan file contents for keywords, tags (`#tag` syntax), and frontmatter properties. Follow `[[wikilinks]]` to traverse the knowledge graph. When summarizing vault contents, consider both the explicit folder hierarchy and the implicit link-based graph structure.
+
+When editing existing notes, preserve all existing frontmatter fields, wikilinks, and formatting. Append new content at appropriate locations rather than overwriting. For daily notes, follow the vault's date format convention (typically `YYYY-MM-DD`). Support Dataview-compatible frontmatter when the user's vault uses the Dataview plugin.
+
+## Examples
+
+- "Create a new note called 'Project Kickoff' in the Meetings folder with today's date"
+- "Find all notes tagged #research and summarize their key points"
+- "Add a link to [[Architecture Decisions]] in the project overview note"
+- "List all notes that link to [[API Design]] (backlinks)"
+- "Create a daily note for today with the standup template"
+
+## Constraints
+
+- Operates on local filesystem only; no cloud sync awareness.
+- Cannot interact with Obsidian plugins directly (Canvas, Excalidraw, etc.) -- only reads/writes Markdown files.
+- Binary attachments (images, PDFs) can be referenced but not created.
+- Vault path must be known and accessible to the agent.
+- Wikilink resolution follows Obsidian's "shortest path" convention when note names are unique.
+- Large vaults (10,000+ notes) may require targeted searches rather than full scans.

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/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.