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

@flytedesk/claude-plugins

v0.5.0

Published

Flytedesk Claude Code plugins: SSP / ad-ops domain knowledge for engineers working on the ad platform.

Readme

Flytedesk Claude Plugins

Claude Code plugins carrying Flytedesk-specific engineering knowledge — SSP/ad-ops workflows, domain conventions, and anything else that's faster to teach an agent once than to re-explain in every session.

Plugins

| Plugin | Purpose | |---|---| | ad-ops | SSP ad unit placement diagnosis and configuration (masthead, sticky bottom, interstitial, in-content/ICV). |

Install

claude plugin marketplace add github:Flytedesk/claude-plugins
claude plugin install ad-ops@flytedesk-plugins

Or declare in a project's .claude/settings.json:

{
  "plugins": ["ad-ops@flytedesk-plugins"]
}

Editing a plugin — bump the version

Every edit to <plugin>/skills/**/SKILL.md or any other plugin asset must bump <plugin>/.claude-plugin/plugin.json's version in the same commit. Plugin caches are keyed by version directory (~/.claude/plugins/cache/flytedesk-plugins/<plugin>/<version>/) — if the version doesn't move, installed copies keep reading the stale cached content even after the push lands. Patch-bump for wording/content fixes, minor for new skills, major for breaking structure changes.

Design notes

  • One SKILL.md per skill, YAML frontmatter (name, description) + a plain markdown body. See ad-ops/skills/ad-placement/SKILL.md for the format — same shape as Flytedesk/flytedesk-skills.
  • Unlike flytedesk-skills (a plain skills folder meant to be copied/submoduled into a project), this repo is a proper Claude Code plugin marketplace (.claude-plugin/marketplace.json at the root, one subfolder per plugin) — install it once per machine/account rather than copying files into each project.