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

@keppylab/describe

v1.0.3

Published

describe - Speak systems into existence. Transform infrastructure from configuration to conversation.

Downloads

7

Readme

describe•

npm version

Watch me build a complete RAG system in 7 prompts:

1. "Find me filesystem and database servers"
2. "Install them"
3. "Create an embedding schema"
4. "Read my documents"
5. "Index them"
6. "Make it searchable"
7. "Give me a terminal interface"

Result: Working RAG system. No config files. No documentation. Just conversation.

What Is This?

describe transforms infrastructure from something you configure to something you converse with.

The old way took hours. The new way takes minutes. The difference isn't speed—it's that you never leave the conversation.

See It In Action

Build a GitHub PR Analyzer (5 prompts)

"Install github and code-analysis servers"
"Connect to my repo"
"Analyze open PRs for complexity"
"Flag potential issues"
"Show me the results"

Create a SQL Chat Interface (4 prompts)

"Install sqlite server"
"Connect to my database"
"Let me query it in plain English"
"Show results as tables"

Turn CSVs into an API (6 prompts)

"Install filesystem and data servers"
"Read all CSVs from ~/data"
"Create REST endpoints for each"
"Add search functionality"
"Add JSON export"
"Start the server"

Quick Start

npm install -g @keppylab/describe

Add to Claude Desktop config:

{
  "describe": {
    "command": "npx",
    "args": ["-y", "@keppylab/describe"]
  }
}

Restart Claude. Start describing.

The Paradigm Shift

Before: Learn tools → Configure tools → Build with tools

After: Describe what you want → Get it running → Iterate by talking

This isn't just about saving time. It's about who can build systems:

  • A researcher can build a knowledge base
  • A designer can create data pipelines
  • A student can build analysis tools

The barrier isn't syntax anymore. It's imagination.

Examples That Will Break Your Brain

Self-Modifying Systems

Human: My RAG system is too slow
Claude: I see it's scanning all documents on each query. Let me add caching...
*modifies the running system*
Claude: Try now - should be 10x faster

Conversational Debugging

Human: Something's wrong with the search
Claude: I see the index is corrupted. Let me rebuild it...
*fixes itself*
Claude: Fixed. Try your search again.

Infrastructure That Explains Itself

Human: How does this work?
Claude: Let me show you the data flow...
*generates visualization of the running system*
Claude: Your query goes through these steps...

Installation

Requirements: Node.js 18+, Python 3.9+, Claude Desktop/claude code

Platforms: macOS, Windows, Linux

Details: See installation guide

CLI Mode: Power users, see CLI documentation

Philosophy

We're not building better tools. We're removing the need to think about tools at all.

Infrastructure should be a conversation, not a configuration.

Status

Now: v1.0 - Full conversational infrastructure
Next: Self-assembling systems, infrastructure that dreams


The best interface is no interface. The best configuration is conversation.

GitHubTwitterDiscord