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

@marlonvidal/tech-manager-os

v1.0.1

Published

AI-powered CLI for engineering managers — process meeting notes, manage your team, track your career.

Downloads

227

Readme

tech-manager-os

npm version CI License: MIT

A local-first operating system for engineering managers — scaffold your vault, process meeting notes, and extend with Claude Code skills.

tech-manager-os (CLI: tmr) helps engineering managers stay organized using plain Markdown files, Obsidian, and Claude Code. Everything stays local — no cloud, no database, no vendor lock-in.


Quick Start

npm install -g @marlonvidal/tech-manager-os
tmr init          # Scaffold vault + generate CLAUDE.md (5 quick prompts)
tmr config        # Set your AI provider and API key
tmr install tmr-inbox   # Install the inbox processing skill
tmr process       # AI-route your inbox files

For a full walkthrough, see the User Guide.


CLI Command Reference

| Command | Description | |---------|-------------| | tmr --help | Show all commands | | tmr --version | Show version | | tmr init | Scaffold vault + generate CLAUDE.md | | tmr config | Configure AI provider and API key | | tmr process | AI-powered inbox processing (requires API key) | | tmr process --plain | Plain text output (no colors/spinners) | | tmr process --dry-run | Preview routing decisions without moving files | | tmr watch | Auto-process inbox on file changes | | tmr install <skill> | Install a Claude Code skill into .claude/skills/ | | tmr install <skill> --force | Reinstall even if already installed | | tmr update | Update all installed skills to latest versions | | tmr team create [team-name] | Create a team | | tmr team add [team-name] [email] | Add a member to a team (prompts if args omitted) | | tmr team archive [team-name] [email] | Archive a team member | | tmr team list [team-name] | List all teams, or members of a specific team | | tmr leadership add [email] | Add a leadership contact (prompts if arg omitted) | | tmr leadership list | List all leadership contacts | | tmr project add <name> | Add a project | | tmr project list | List all projects | | tmr show <email> | Display profile for any email (teams, leadership, relationships) |


Claude Code Skills

Skills extend your vault with AI-powered workflows invoked directly from Claude Code — no CLI required.

| Skill | Slash Command | What it does | |-------|--------------|-------------| | tmr-inbox | /tmr-inbox | Routes Granola meeting notes from inbox/ to the right folders, normalizes filenames, scaffolds missing profiles, extracts tasks | | tmr-inbox setup | /tmr-inbox setup | One-time setup: creates my-tasks/tasks.md and Dataview view files |

Install a skill:

tmr install tmr-inbox

Skills live in .claude/skills/ inside your vault. They are plain Markdown files that Claude Code reads as instructions. See the Skill Authoring Guide to write and publish your own.


Vault Structure

tmr init creates this structure in your chosen directory:

your-vault/
├── CLAUDE.md              # Claude Code context: your identity, folder map, communication style
├── inbox/                 # Drop meeting notes here (Granola syncs here automatically)
├── archive/               # Processed originals, organized by year/month
├── config/                # Messaging templates and process references
├── my-career/
│   ├── assessments/
│   └── feedbacks/
├── my-leadership/         # Your managers and skip-levels
├── my-tasks/              # tasks.md + Dataview view files (today, this-week, this-month, this-quarter)
├── my-teams/
│   ├── archived/          # Archived team members
│   ├── feedback-templates/
│   ├── members/           # One folder per direct report ({email}/)
│   └── teams/             # Named team groupings
├── my-company/
│   ├── meetings/          # Company-wide meeting notes
│   ├── members/           # Company contacts not in your team
│   └── projects/          # Active initiatives
├── knowledge-base/
│   ├── branding-guidelines/
│   ├── company/
│   ├── files/
│   ├── people/
│   ├── process/
│   └── security/
└── .claude/skills/        # Installed Claude Code skills

See examples/sample-vault/ for a realistic starter vault.


How It Works

  1. tmr init — answers 4 prompts (name, email, role, company) → scaffolds the vault → generates CLAUDE.md with your identity and folder map
  2. Granola records meetings and syncs transcripts into inbox/ via the Obsidian Granola plugin
  3. tmr process (CLI) or /tmr-inbox (Claude Code skill) routes each note to the correct team/leadership/company folder, extracts tasks, and updates context files
  4. tmr install <skill> — pull new skills from the registry to extend your vault with new AI workflows
  5. tmr update — keep all installed skills up to date

Requirements

  • Node.js 18+ (20.17.0 LTS recommended)
  • npm (or use npx @marlonvidal/tech-manager-os without installing globally)
  • AI API key — OpenAI, Anthropic (Claude), or Google Gemini — required for tmr process
  • Claude Code (optional) — required for skill-based workflows (/tmr-inbox)
  • Obsidian + Granola plugin (optional) — recommended for automatic meeting note sync

See SECURITY.md for API key storage and best practices.


Setup Guides


Architecture

  • CLI layer: TypeScript + Commander.js
  • AI provider: Adapter pattern — OpenAI, Anthropic, Gemini (used only by tmr process)
  • Skills layer: Claude Code SKILL.md files installed in .claude/skills/
  • Storage: Local Markdown files — no database, Obsidian-compatible
  • Build: TypeScript → dist/ via tsup; binary entry point dist/cli.js

Development Scripts

| Script | Description | |--------|-------------| | npm run build | Compile TypeScript to dist/ via tsup | | npm run dev | Run CLI directly via ts-node | | npm test | Run full test suite | | npm run test:coverage | Run tests with coverage report | | npm run lint | ESLint check | | npm run lint:fix | ESLint auto-fix | | npm run format | Prettier format | | npm run typecheck | TypeScript type check (no emit) | | npm run validate | lint + typecheck + test + build |


License

MIT — see LICENSE