How do I install the Pproj Skills skill?

Run npx skillmds@latest add bladnman/pproj-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pproj Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pproj Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pproj Skills free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pproj Skills?

bladnman (@bladnman) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pproj Skills by bladnman — Agent Skill

Name: Pproj Skills
Author: bladnman

File contents

Project Skills

Common project workflow actions. Each command is goal-oriented — it describes the desired end state, not the exact steps. The agent figures out how to get there.

Commands

Command	Shortcut	What it does
dev	pdev	Get the dev server running
install	pinstall	Build the project and install it as a production artifact
save	psave	Quick checkpoint — commit everything, no verification
test	ptest	Run project validation checks without committing
push	ppush	Publish checkpoint — commit everything and push, no required verification
pr	ppr	Create or show a pull request
merge	pmerge	Merge one or all pull requests from GitHub

Routing

Match the user's input to a command file. The user may use the full name, the p-prefixed shortcut, or a synonym — all route to the same command.

Input	Command file
`dev`, `pdev`	`commands/dev.md`
`install`, `pinstall`, `build`, `ship`	`commands/install.md`
`save`, `psave`	`commands/save.md`
`test`, `ptest`, `verify`, `check`	`commands/test.md`
`push`, `ppush`	`commands/push.md`
`pr`, `ppr`	`commands/pr.md`
`merge`, `pmerge`, `merge <number>`, `pmerge <number>`, `merge all`, `pmerge all`	`commands/merge.md`

Philosophy

These commands represent desired outcomes, not prescriptive recipes:

dev = "get me a running dev server" — detect the best way automatically
install = "build this and put it where it goes" — production artifact, installed, running
save = "checkpoint where I am" — fast, no fuss
test = "check this when needed" — run project validation without committing
push = "publish this checkpoint" — everything committed and pushed, no required tests
pr = "get a PR up" — verified, pushed, PR created or shown
merge = "bring that PR home" — merge on GitHub, sync locally

If something can't be done (no git repo, no dev script found), say so clearly. If something is optional and missing (no remote upstream), just skip it silently.

---name: pproj-skillsdescription: Project workflow commands. Use when user says: pdev, pinstall, psave, ptest, ppush, ppr, pmerge — or dev, install, save, test, push, pr, merge as standalone messages.---# Project SkillsCommon project workflow actions. Each command is goal-oriented — it describes the desired end state, not the exact steps. The agent figures out how to get there.## Commands| Command | Shortcut | What it does ||---------|----------|-------------|| **dev** | **pdev** | Get the dev server running || **install** | **pinstall** | Build the project and install it as a production artifact || **save** | **psave** | Quick checkpoint — commit everything, no verification || **test** | **ptest** | Run project validation checks without committing || **push** | **ppush** | Publish checkpoint — commit everything and push, no required verification || **pr** | **ppr** | Create or show a pull request || **merge** | **pmerge** | Merge one or all pull requests from GitHub |## RoutingMatch the user's input to a command file. The user may use the full name, the `p`-prefixed shortcut, or a synonym — all route to the same command.| Input | Command file ||-------|-------------|| `dev`, `pdev` | `commands/dev.md` || `install`, `pinstall`, `build`, `ship` | `commands/install.md` || `save`, `psave` | `commands/save.md` || `test`, `ptest`, `verify`, `check` | `commands/test.md` || `push`, `ppush` | `commands/push.md` || `pr`, `ppr` | `commands/pr.md` || `merge`, `pmerge`, `merge <number>`, `pmerge <number>`, `merge all`, `pmerge all` | `commands/merge.md` |## PhilosophyThese commands represent **desired outcomes**, not prescriptive recipes:- **dev** = "get me a running dev server" — detect the best way automatically- **install** = "build this and put it where it goes" — production artifact, installed, running- **save** = "checkpoint where I am" — fast, no fuss- **test** = "check this when needed" — run project validation without committing- **push** = "publish this checkpoint" — everything committed and pushed, no required tests- **pr** = "get a PR up" — verified, pushed, PR created or shown- **merge** = "bring that PR home" — merge on GitHub, sync locallyIf something can't be done (no git repo, no dev script found), say so clearly. If something is optional and missing (no remote upstream), just skip it silently.

Frequently asked questions

Pproj Skills