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

daily-report-skill

v1.0.0

Published

Auto-generate daily/weekly work reports from git, GitHub, monitoring data and Obsidian KM — push to Telegram in company format

Readme

daily-report-skill

Auto-generate daily/weekly work reports using Obsidian KM as the single source of truth.

What it does

Data Sources → Obsidian Journal → Company Format → Telegram
  1. Collect — git commits, GitHub events, site monitoring, Claude memory
  2. Persist — write to obsidian/journal/YYYY-MM-DD.md (knowledge retention)
  3. Output — transform to company report format → push to Telegram

Install

# npm
npm install -g daily-report-skill

# Add to Claude Code
claude mcp add-skill daily-report-skill

Usage

/daily-report          # Generate today's report
/daily-report --weekly # Generate weekly report
/daily-report --dry-run # Preview without sending
/daily-report --date 2026-03-25 # Specific date
/daily-report --auto   # Skip review, send directly

Modes

| Mode | Description | |------|-------------| | daily | Scan today's data → journal → TG | | weekly | Aggregate week's journals → weekly review → TG | | backfill | Fill past day's journal from git (KM only, no TG) |

Report Format

5-section company daily report:

  1. 今日完成 (Completed)
  2. 工作進度 (Progress)
  3. 問題與風險 (Issues & Risks)
  4. AI 自動化亮點 (AI Automation Highlights)
  5. 明日計劃 (Tomorrow's Plan)

Data Sources

  • Local git repos (all under workspace)
  • GitHub API events (pushes, releases, PRs)
  • Site health monitoring state
  • Claude Code memory files
  • Existing Obsidian journal entries

License

MIT