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

@firstpick/pi-extension-wiki-tools

v0.1.3

Published

Pi tools and skill for scaffolding local wiki extension packages from repository templates.

Readme

pi-extension-wiki-tools

Pi extension + skill for creating local wiki/documentation extension packages from the repository wiki templates.

Registered skill

  • wiki-tools — routes wiki package creation/update/validation work to the tools below.

Registered commands

  • /wiki-templates — lists available template directories.
  • /wiki-create <repo-url-or-topic> [--repo-url URL] [--target-dir DIR] [--doc-format markdown|asciidoc|html] [--dry-run] [--overwrite] [--yes] [--agent-review] [--no-agent-review] — interactively creates a new local wiki package. In UI mode it prompts for missing input, previews inferred values, lets you choose dry-run/create, validates after writing, and by default queues an agent review/tuning pass. If the first argument is a repository URL, names and the setup command are inferred from that URL. Generic repo names like documentation, docs, and wiki use the repository owner as the topic.
  • /wiki-update <repo-url-or-topic> --target-dir DIR [--overwrite] [--apply] — previews or applies a template refresh. Defaults to dry-run; --apply writes files.
  • /wiki-validate <target-dir> — validates a generated wiki package.

Commands also accept a JSON object, for example:

/wiki-create https://github.com/example/example-wiki.git
/wiki-create https://github.com/example/example-wiki.git --yes --no-agent-review
/wiki-create {"repoUrl":"https://github.com/example/example-wiki.git"}

Registered tools

  • list_wiki_templates — lists available template directories from:
    • WIKI_TEMPLATES_DIR
    • <cwd>/templates
    • this package's bundled templates/
    • the monorepo sibling ../templates
  • create_wiki — creates a new pi-extension-<topic>-wiki-local package from templates/local-wiki-extension; use docFormat for non-Markdown corpora. Tune searchStopWordsCode / termWeightsCode during the per-wiki review from observed corpus search behavior.
  • update_wiki — previews or applies template refreshes for an existing wiki package. Defaults to dry-run.
  • validate_wiki — checks required package files, Pi metadata, bundled skill files, and unreplaced placeholders.

Example

{
  "topicName": "Example",
  "repoUrl": "https://github.com/example/example-wiki.git",
  "docsPath": "~/.examplewiki"
}

This creates:

pi-extension-example-wiki-local/
├── index.ts
├── package.json
├── LICENSE
├── README.md
└── skills/example-local/SKILL.md

Generated tool names use the <extensionId>_wiki_* convention, for example example_wiki_search, example_wiki_extract, and example_wiki_smoke_test. Each generated package includes wiki-specific setup/status/smoke-test commands, including /<extensionId>-wiki-local-setup, which shallow-clones or updates the configured repository into the local docs path. Parser formats currently supported by the template are markdown, asciidoc, and html.

Safety

create_wiki and /wiki-create refuse to write into an existing target unless overwrite: true / --overwrite is set. /wiki-create is safe by default in interactive UI mode because it previews before writing. update_wiki defaults to dryRun: true; use the dry-run plan before overwriting customized package files.

Evaluation expectations

Before considering a generated wiki package complete, test accuracy (relevant top search results, correct titles/headings, source-faithful extracts, smoke-test findings), effectiveness (setup/status/smoke-test behavior, missing-docs failure, prompt routing, diagnostics), and token output (compact search, bounded extract/read defaults, truncation or omitted-section reporting). Tune query expansions plus corpus-derived stopwords/downweights when broad terms over-select results.