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

almond-cmdline

v1.8.0-beta.1

Published

CLI Almond Virtual Assistant

Downloads

12

Readme

Almond

End User Programmable Virtual Assistants

This repository contains the command line version of Almond, the end user programmable assistant.

It is a full featured version, although it is mainly useful for development and testing.

Almond is part of Open Thing Platform, a research project led by prof. Monica Lam, from Stanford University. You can find more information at https://thingpedia.stanford.edu/about.

Installing from the node package manager

npm install -g almond-cmdline

You can then run it with almond from the command line.

Installing from source

The code depends on nodejs (>= 6.10), cvc4 (any version, although >= 1.5 is recommended). Acquire the dependencies with:

git submodule update --init --recursive

Then you can install the dependencies with a standard npm install, or with yarn install.

NOTE: npm >= 5 is known NOT to work. For best results, use the npm that came with node 6.10 LTS, or use yarn.

Usage

Start Almond with node ./main.js

Follow the instructions to complete set up. You can then type a sentence to instruct your virtual assistant.

Special commands are available using \. For the full list, use \?. To quit, use \q or Ctrl-D (EOF).

Setting up OAuth-based devices

To set up a device that uses OAuth, say

\d start-oauth <kind>

where <kind> is the identifier of the device you want, e.g. \d start-oauth com.twitter.

Copy the resulting URL in your browser and authenticate. The browser will redirect you to a broken page under http://127.0.0.1:3000. Copy that and type:

\d complete-oauth <url>

Enabling developer mode

If you're a Thingpedia developer using Command Line Almond for testing, you can enable developer mode with the following commands:

\= developer-key "<your Thingpedia developer key>"
\= developer-dir "<absolute path to a directory containing your Thingpedia devices>"

Note that quotes are significant, so the commands look like:

\= developer-key "123456789...ABCDEF"
\= developer-dir "/home/bob/Projects/thingpedia-devices"

If, say, inside the "thingpedia-devices" directory is a subdirectory called com.foo containing a manifest.tt file, that device will be loaded from the local path instead of Thingpedia.

If you don't specify a developer-dir but you specify a developer-key, Almond will access unapproved devices from your account, and download them automatically.

Troubleshooting

My devices don't see the latest updates

Almond uses a cached version of any Thingpedia device, which is periodically updated. You can force an update with:

\d update <device-id>

(e.g. \d update com.foo).

You can also remove the cache directory entirely with:

rm -fr ~/.cache/almond-cmdline

At the next restart, Almond will download the code again from Thingpedia.