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

@php-workx/skill-tk

v0.1.0

Published

Git-native ticket tracking skill for Claude Code and Codex. Plain markdown tickets with YAML frontmatter, dependency graphs, and plugin system.

Downloads

57

Readme

tk

Git-native ticket tracking skill for Claude Code and Codex. Track issues as plain markdown files alongside your code — no databases, no daemons, just files in .tickets/.

Why Use This?

  • Plain markdown: Tickets are markdown files with YAML frontmatter, directly readable by AI agents without JSON parsing
  • Git-native: Tickets live alongside code, tracked by git, survive compaction and session boundaries
  • Dependency graphs: Track blockers with cycle detection; tk ready shows only unblocked work
  • IDE-friendly: Ticket IDs double as filenames — Ctrl+Click on nw-5c46 in git log opens the ticket
  • Plugin-extensible: Drop tk-<cmd> executables in PATH to extend functionality

Quick Start

tk ready                        # what's unblocked and ready to work on
tk create "Fix login bug" -t bug -p 1
tk show mp-a3x9                 # full ticket with computed context
tk start mp-a3x9                # mark as in progress
tk close mp-a3x9                # done

Install

Prerequisites: ticket CLI installed (brew install ticket).

# Via installer script
git clone --depth 1 https://github.com/php-workx/skill-tk.git
cd skill-tk && bash scripts/install-tk-skill.sh

# Via OpenSkills
npx openskills install php-workx/skill-tk

After install, restart Claude/Codex so the new skill is loaded.

What It Does

The skill teaches Claude/Codex how to use tk for persistent issue tracking:

  1. Session start: tk ready shows actionable work
  2. During work: Create, update, and close tickets as context changes
  3. Session end: Ticket notes preserve state across sessions
  4. After compaction: Tickets survive — they're files in git, not conversation memory

Documentation

| Document | Purpose | |----------|---------| | CLI_REFERENCE.md | All commands, flags, environment variables | | TICKET_CREATION.md | When/how to create tickets, file format | | DEPENDENCIES.md | Dependencies, links, parent-child hierarchy | | WORKFLOWS.md | Session start, epic planning, checklists | | PATTERNS.md | Knowledge work, resume, side quests | | INTEGRATION_PATTERNS.md | Task tools layering, RPI workflow | | PLUGIN_SYSTEM.md | Using and creating plugins | | ANTI_PATTERNS.md | Common mistakes and how to avoid them | | TROUBLESHOOTING.md | Fixing common issues |

Development

bash scripts/validate.sh       # validate skill structure
just check                     # full local quality gate

License

See LICENSE.