Total Skills
8
Author Profile: nthplusio
Skills published by nthplusio with real stars/downloads and source-aware metadata.
Total Stars
8
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
pm-branches
1
Stars
1
Downloads
0
pm-issues
1
Stars
1
Downloads
0
pm-pivot
1
Stars
1
Downloads
0
pm-report
1
Stars
1
Downloads
0
pm-scripts
1
Stars
1
Downloads
0
pm-setup
1
Stars
1
Downloads
0
pm-status
1
Stars
1
Downloads
0
project-manager
1
Stars
1
Downloads
0
Published Skills
pm-branches
Use this skill when creating a git branch for a Linear or GitHub issue, writing a PR description, opening a pull request, or linking a PR to its tracked issue. Trigger phrases "create a branch", "new branch for this issue", "branch for
Repository SourceNeeds Review
pm-issues
Use this skill when creating, updating, or closing an issue in Linear or GitHub; when the user describes untracked work that should be tracked; when drafting issue content; or when the user says "create an issue", "log this in Linear", "add this to Linear", "open a github issue", "file an issue", "create issue
Repository SourceNeeds Review
pm-pivot
Use this skill when the user changes direction mid-feature, describes a significant scope change, says the approach isn't working, wants to abandon the current approach, or says "we need to rethink this", "let's change direction", "this isn't right", "pivot", "different approach". Also use when the user's current work no longer matches the active tracked issue (Linear or GitHub).
Repository SourceNeeds Review
pm-report
Use this skill when the user asks for a "daily report", "weekly report", "status report", "project report", "send the standup update", "generate a status PDF", "what changed today", "what changed this week", "send a daily update", or any project status summary that should be persisted as a document or sent as email. Produces Markdown, HTML, and/or PDF status reports for the active project showing in-progress work, day-over-day changes, week-over-week changes, and up-next items. Output format is selectable (pdf, html, or both) at runtime. Optional handoff to resend-cli for delivery.
Repository SourceNeeds Review
pm-scripts
Use this skill when the user wants to capture, render, or rerun reusable CLI command sequences for the project — phrases like "save this as a pm script", "run the daily pull", "rerun that linear query", "make this a script", "/pm-script <name>", "list pm scripts", "create a script for this report". Scripts are bash bodies with {{var}} substitution, stored locally so the same data pull or workflow can be replayed deterministically across sessions. Particularly useful for repeatable Linear queries, multi-team data pulls, and feeding the daily/weekly reports.
Repository SourceNeeds Review
pm-setup
Use this skill when the user asks to "set up project manager", "register this project", "configure pm", "onboard this repo", "install Linear CLI", "linear cli auth", "linear authentication for project-manager", "set up linear cli", "configure .linear.toml", or invokes the `/pm-setup` slash command. Also use proactively when the SessionStart hook nudges the user with "project-manager: installed but no projects configured" and they ask how to fix it. Guided wizard that registers a repo as a managed project and installs/authenticates the Linear CLI (preferred transport).
Repository SourceNeeds Review
pm-status
Use this skill when the user asks "where are we", "what's in progress", "what should I work on next", "project status", "catch me up", "what's open", "what's stale", "what's stuck", "anything dragging", "old in-progress issues", or "what's been sitting". Provides a cache-first session briefing with in-progress issues, next suggested work, **stale-issue detection** (issues stuck in-progress longer than --stale-days, default 30), and delta sync on demand. Supports --refresh for full re-pull. Do NOT include past session history unless the user explicitly asks.
Repository SourceNeeds Review
project-manager
Use this skill when the user says "project manager", "pm", "where are we", "what's in progress", "what should I work on next", "let's work on this project", "project status", "open issues", "what's next", "issue tracker", "track this work", "playground from this spec", "interactive spec preview", or asks about Linear issues, GitHub issues, GitHub PRs, or any issue tracking for the current project. Also use proactively when the user describes work that doesn't appear to be tracked, when starting new work on main/master, when branch naming suggests untracked work, or when the user has a spec they're about to file as a Linear initiative or GitHub project. Routes to focused skills (pm-status, pm-issues, pm-branches, pm-pivot, pm-report, pm-scripts, pm-spec, pm-setup) based on the task.
Repository SourceNeeds Review