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 🙏

© 2024 – Pkg Stats / Ryan Hefner

teambot-hello

v0.0.2

Published

Sample getting started skill for Teambot

Downloads

4

Readme

TEAMBOT-HELLO

Slack Channel

This is a sample hello world skill for Teambot. Its main purpose is to show how easy is skill development for Teambot. There are few rules that the Teambot skill developers need to follow and that's it:

  • The skill entry point is index.js

  • index.js should exports a function that takes 2 arguments:

    • controller
    • middleware

Both arguments comes from Botkit so you have the entire set of Botkit features in place.

  • index.js contains mapping between patterns and methods. In this way when Teambot receives a message that contains the defined pattern, its corresponding method will be called. More detaile can be found in Botkit documentation.
  • In order to have well structured Teambot skill the methods that are mapped to patterns could be in separate file(s).
  • Every file should export function that takes 1 argument - controller
  • Every method that is mapped to a pattern should takes 2 arguments: bot and message