npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sperax/tool-slack

v0.2.2

Published

Send messages, search conversations, and manage Slack channels — an agent tool for SperaxOS.

Readme

@sperax/tool-slack

Send messages, search conversations, and manage Slack channels

Slack is an agent tool from SperaxOS, packaged headless so you can call it from any agent framework. It ships two things: the manifest — a JSON-Schema function definition a model can call — and the executor that runs the call against the real API.

There is no UI layer and no framework lock-in. It works anywhere TypeScript runs.

Install

npm install @sperax/tool-slack

Usage

Call it directly

import { slackExecutor } from '@sperax/tool-slack';

const result = await slackExecutor.invoke('postMessage', {"channel":"<channel>","text":"<text>"}, {
  messageId: 'msg-1',
});

console.log(result.content); // prose summary written for the model to read
console.log(result.state);   // typed data payload for your own UI

Give it to a model

import Anthropic from '@anthropic-ai/sdk';
import { SlackManifest, slackExecutor } from '@sperax/tool-slack';

const client = new Anthropic();

const response = await client.messages.create({
  model: 'claude-opus-4-8',
  max_tokens: 1024,
  messages: [{ role: 'user', content: 'Ask something this tool can answer' }],
  tools: SlackManifest.api.map((api) => ({
    name: api.name,
    description: api.description,
    input_schema: api.parameters,
  })),
});

for (const block of response.content) {
  if (block.type !== 'tool_use') continue;
  const result = await slackExecutor.invoke(block.name, block.input, { messageId: response.id });
  console.log(result.content);
}

SlackManifest.api is already in JSON-Schema form, so it maps onto any tool-calling API — Anthropic, OpenAI, the Vercel AI SDK, or an MCP server — without translation.

Every executor returns a BuiltinToolResult{ success, content, state }. content is prose written for the model to read; state is the typed data payload for your own code. Executors never throw: a failed call comes back as { success: false, content: '<reason>' }, so a network blip degrades the answer instead of crashing the agent loop.

Configuration — required

This tool needs a backend you control. It will not work on a bare npm install alone.

The upstream API requires a secret key. That key is deliberately not bundled here — shipping it in an npm package would leak it to every consumer. Instead the executor calls a SperaxOS /webapi/* route, which holds the key server-side and injects it. That route is session-authenticated, so the public deployment at https://chat.sperax.io (the default origin) answers 401 to anonymous callers.

To use this tool you need one of:

  • a SperaxOS deployment of your own, or
  • any HTTP endpoint that implements the same request shape and supplies the key.

Point the package at it before importing the tool — the URL is resolved once, when the module first loads:

SPERAX_API_BASE_URL=https://my-speraxos.example.com

or in code:

import { configureSperaxApi } from '@sperax/agent-tools-core';

configureSperaxApi({ baseUrl: 'https://my-speraxos.example.com' });

// import the tool only after configuring, so the path resolves against your origin
const { slackExecutor } = await import('@sperax/tool-slack');

Inside a browser that already serves those routes at its own origin, requests stay same-origin and no configuration is needed.

If you want a tool that runs with zero setup, use one of the standalone tools — those call public APIs directly and need no key, no origin, and no backend.

Tool identifier

sperax-slack

API reference

postMessage

Post a message to a Slack channel. Requires user confirmation.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | channel | string | yes | Channel name or ID to post to | | text | string | yes | Message text (supports Slack mrkdwn formatting) |

sendDirectMessage

Send a direct message to a Slack user. Requires user confirmation.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | text | string | yes | Message text | | userId | string | yes | User ID or username to send the DM to |

replyToThread

Reply to an existing message thread. Requires user confirmation.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | channel | string | yes | Channel where the thread exists | | text | string | yes | Reply text | | threadTs | string | yes | Timestamp of the parent message |

searchMessages

Search for messages across the Slack workspace.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | count | integer | no | Maximum number of results | | query | string | yes | Search query string |

listChannels

List channels in the Slack workspace.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | excludeArchived | boolean | no | Exclude archived channels | | limit | integer | no | Maximum number of channels to return |

getChannelInfo

Get details about a specific Slack channel.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | channel | string | yes | Channel name or ID |

createChannel

Create a new Slack channel.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | isPrivate | boolean | no | Whether the channel is private | | name | string | yes | Channel name (lowercase, no spaces) |

archiveChannel

Archive a Slack channel. Requires user confirmation.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | channel | string | yes | Channel name or ID to archive |

setTopic

Set or update a channel's topic.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | channel | string | yes | Channel name or ID | | topic | string | yes | New topic text |

listMembers

List members of a specific Slack channel.

| Parameter | Type | Required | Description | | --- | --- | --- | --- | | channel | string | yes | Channel name or ID | | limit | integer | no | Maximum number of members to return |

Types

Shared types come from @sperax/agent-tools-core: BuiltinToolManifest, BuiltinToolResult, BuiltinToolContext, and the BaseExecutor class every tool executor extends.

Related

License

Apache-2.0