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

@malloy-publisher/skills

v0.1.7

Published

Agent skills for Malloy and the Malloy Publisher

Readme

@malloy-publisher/skills

The agent skills that ship with Malloy Publisher, as files you can install. They are task-specific guides for writing Malloy, building and reviewing models, exploring data, and authoring HTML data apps.

Publisher already serves these skills over MCP, as prompts, including each skill's reference/ files. This package exists for the cases MCP does not cover: a host that reads skill files from disk (Claude Code and the Publisher plugin), a scaffolder that installs them into a new project, or any tool that wants the files themselves rather than prompt text.

Install

npm install @malloy-publisher/skills

Copy the skills into a project

import { cpSync } from "node:fs";
import { skillsDir } from "@malloy-publisher/skills";

cpSync(skillsDir, ".claude/skills", { recursive: true });

Copy the files rather than symlinking them. npm drops symlinks from a tarball, and a symlink into node_modules breaks the moment the tree is pruned or the package is hoisted somewhere else.

List what is available

import { listSkills } from "@malloy-publisher/skills";

for (const skill of listSkills()) {
   console.log(skill.name, skill.description, skill.dir);
}

listSkills() reads each skill's frontmatter from disk, so it cannot drift from the files it describes.

What is in it

Each skill is a directory holding a SKILL.md, and some also carry a reference/ directory that the skill points to for detail it does not inline. Start with malloy-getting-started. Use malloy-modeling to build or change a model, malloy-analysis to explore and answer questions, and malloy-review to check Malloy for correctness.

A few skills (malloy-modeling, malloy-publish, malloy-document, malloy-getting-started, and the malloy index) are written for a Publisher host and name Publisher's malloy_* MCP tools directly. The rest describe Malloy itself and refer to tools by bare name (get_context, execute_query, search_malloy_docs), because the prefix depends on the host. search_database_schema maps the same way if a shared skill starts using it. On Publisher those are malloy_getContext, malloy_executeQuery, malloy_searchDocs, and malloy_searchDatabaseSchema.

Versioning

This package versions on its own line, separately from @malloy-publisher/server, sdk, and app. A skill edit does not need a server release.

The MCP prompt channel is a separate story: the server compiles the skill bodies into its own bundle at build time, so installing a newer version of this package does not change what an already-built server serves over MCP.

Contributing

The skills live at skills/ in the Publisher repo, and this package copies that directory in when it is packed. Edit them there.