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

@naganpm/fetch-prompts

v1.0.6

Published

Fetch prompts from GitLab repository

Readme

fetch-prompts

Fetch prompts from a public GitLab repository.

Quick Start

Simple - no authentication required!

npx -y @naganpm/fetch-prompts

This downloads all .md prompt files from https://gitlab.com/prompts4/prompt-manager into a local prompts/ folder.


Alternative: For Private Repos

If the GitLab repo becomes private, users will need:

  1. Access to the GitLab repo (ask owner to add you as member)
  2. A GitLab personal access token

Step 1: Get Added to GitLab Repo

Ask the repo owner to add you at: https://gitlab.com/prompts4/prompt-manager/-/project_members

Step 2: Create GitLab Token

  1. Go to: https://gitlab.com/-/profile/personal_access_tokens
  2. Create token with scopes: read_api, read_repository
  3. Copy your token (starts with glpat-)

Step 3: Run with Token

GITLAB_TOKEN=glpat-your-token-here npx -y @naganpm/fetch-prompts

Or export it first:

export GITLAB_TOKEN=glpat-your-token-here
npx -y @naganpm/fetch-prompts

For Repo Owner: Adding Users (Private Repos Only)

To grant someone access to fetch prompts:

  1. Go to: https://gitlab.com/prompts4/prompt-manager/-/project_members
  2. Click "Invite members"
  3. Add their GitLab username or email
  4. Set role to "Reporter" (read-only access)
  5. Click "Invite"

They can then create their own token and use the npx command above.

Setup (For Development)

If you want to fork/modify this package:

  1. Edit bin/index.js to point to your GitLab repo:

    const GITLAB_PROJECT = 'your-group/your-project';
    const GITLAB_BRANCH = 'main';
    const PROMPTS_PATH = 'prompts';
  2. Create .env for local testing:

    # Copy the example
    cp .env.example .env
       
    # Edit .env and add your GitLab token
    GITLAB_TOKEN=glpat-xxxxxxxxxxxx

    Create a token at: https://gitlab.com/-/profile/personal_access_tokens Required scopes: read_api, read_repository

  3. Prepare your GitLab repo with a prompts/ folder containing .md files:

    your-gitlab-repo/
    └── prompts/
        ├── assessments-result-feed.md
        └── other-prompt.md
  4. Test locally:

# Install dependencies
npm install

# Make bin/index.js executable
chmod +x bin/index.js

# Create .env with your token (for private repos)
cp .env.example .env
# Edit .env and add your GITLAB_TOKEN

# Test locally
npm link
npx -y @naganpm/fetch-prompts

# Or run directly
node bin/index.js

GitLab Repository Structure

Your GitLab repo should have:

prompts/
├── assessments-result-feed.md
├── another-route.md
└── more-prompts.md

All .md files in the prompts/ folder will be downloaded.