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

credibility-engine

v1.0.0

Published

Your personal credibility advisor for Claude Code

Readme

Credibility Engine

Your personal credibility advisor, built for Claude Code.

Credibility Engine is for writers, coaches, consultants, and creators who want to build authority in their space. Once you set up your profile, the engine knows your positioning, your audience, and what moves the credibility needle for your specific context — so you are never stuck on what to create next.


What you get

  • A personalised content strategy tied to your credibility goals, not a generic framework
  • Specific recommendations for what to create next, scored against your schedule, your content balance, and your authority-to-income path
  • Production-ready outlines you can execute in your own voice — the engine never writes your content for you
  • A recurring workflow: log what you completed, get a reflection on your content patterns, and evolve your profile as your positioning sharpens

What it looks like

Here is what /cred:onboard looks like:

This takes 10–15 minutes. No forms, no fields to fill in — just a conversation.

At the end you'll have:
1. A credibility profile that loads automatically at the start of every session
2. A positioning summary ready to hand to a VA or ghostwriter

Let's start.

Who are you, and what do you do? Tell me in your own words — as if you were explaining
it to someone you just met at an industry event.

Here is what /cred:next looks like:

Here's what to create next:

1. **Why Most Leadership Coaches Focus on the Wrong Metric** — LinkedIn Long-form
   Your consulting clients consistently mention "ROI on coaching" as their main objection —
   this reframes the conversation and positions you as the answer before they even enquire.

2. **The 90-Day Credibility Audit: What I Check in Every New Client Engagement** — Newsletter
   Fills your Thursday newsletter slot and directly demonstrates your diagnostic framework
   to the B2B HR audience you're building trust with.

3. **One Question That Changes How Executives Think About Their Online Presence** — LinkedIn Post
   Short-form authority content is underrepresented in your last five posts — this format
   corrects the balance while targeting your primary platform.

Want to go deeper on any of these, or ready to create? Run /cred:create-content [number] to start.

What you need

Claude Code — that is it.


How to install

Open your terminal and run:

npx credibility-engine

Then open any folder in Claude Code and run /cred:onboard. Onboarding takes about 10–15 minutes — it is a conversation, not a form.


Commands

Getting Started

| Command | What it does | |---------|--------------| | /cred:onboard | First-time setup wizard. Captures your profile, voice, and positioning. Takes 10–15 minutes. | | /cred:settings | View and change your model profile (quality / balanced / budget). | | /cred:profile | View your credibility profile or update a specific field. |

Strategy and Planning

| Command | What it does | |---------|--------------| | /cred:strategy | Generate your platform focus, 3–6 month credibility trajectory, and weekly content schedule. | | /cred:next | See your top 3 content recommendations, ranked by schedule gaps, credibility goals, and content balance. | | /cred:backlog | View your prioritised content queue and weekly on-track status. | | /cred:idea | Quick-capture a content idea to your backlog. |

Creating Content

| Command | What it does | |---------|--------------| | /cred:create-content | Generate a detailed content outline for a specific piece. Specify a backlog item number or topic. | | /cred:repurpose | Adapt an existing piece of content for a different platform, with format-specific structural guidance. | | /cred:brief | Generate a production brief ready to hand to a videographer, designer, or ghostwriter. |

Managing Your Practice

| Command | What it does | |---------|--------------| | /cred:standup | Log what you completed since last time and get an updated view of what is due this week. | | /cred:reflect | Periodic review that analyses your recent content and proposes targeted profile enrichments. Run every 4–8 weeks. |

Troubleshooting

| Command | What it does | |---------|--------------| | /cred:check | Verify your installation and diagnose any issues. |


Troubleshooting

If something is not working, run /cred:check.

It checks that all required files are in place — agents, commands, knowledge base, and your profile — and prints a clear status for each. If anything is missing, it tells you exactly what to do to fix it.