Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review.
$ npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills utility-pm-workflow-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/utility-pm-workflow-builder .claude/skills/utility-pm-workflow-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "utility-pm-workflow-builder" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/utility-pm-workflow-builder into .claude/skills/utility-pm-workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "utility-pm-workflow-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/product-on-purpose/pm-skills/tree/main/skills/utility-pm-workflow-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills utility-pm-workflow-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/utility-pm-workflow-builder .agents/skills/utility-pm-workflow-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "utility-pm-workflow-builder" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/utility-pm-workflow-builder into .agents/skills/utility-pm-workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "utility-pm-workflow-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills utility-pm-workflow-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/utility-pm-workflow-builder .cursor/skills/utility-pm-workflow-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "utility-pm-workflow-builder" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/utility-pm-workflow-builder into .cursor/skills/utility-pm-workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "utility-pm-workflow-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/product-on-purpose/pm-skills.git --path skills/utility-pm-workflow-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills utility-pm-workflow-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/utility-pm-workflow-builder .gemini/skills/utility-pm-workflow-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "utility-pm-workflow-builder" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/utility-pm-workflow-builder into .gemini/skills/utility-pm-workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "utility-pm-workflow-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install product-on-purpose/pm-skills utility-pm-workflow-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/utility-pm-workflow-builder .github/skills/utility-pm-workflow-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "utility-pm-workflow-builder" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/utility-pm-workflow-builder into .github/skills/utility-pm-workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "utility-pm-workflow-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills utility-pm-workflow-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/utility-pm-workflow-builder .opencode/skills/utility-pm-workflow-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "utility-pm-workflow-builder" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/utility-pm-workflow-builder into .opencode/skills/utility-pm-workflow-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "utility-pm-workflow-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
utility-pm-workflow-builderGuides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review.
Utility Pm Workflow Builder is an agent skill from product-on-purpose/pm-skills. Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored handoffs. Use when creating a new multi-skill workflow or promoting a repeated ad-hoc chain into a durable one. To build a single skill instead, use utility-pm-skill-builder; to run a sequence without…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/trigger-fixtures.json`, `references/EXAMPLE.md` and `references/TEMPLATE.md`).
It sits in Agent Workflows, covering Skill authoring. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Utility Pm Workflow Builder loads about 2.2k tokens when it runs, and up to ~7.1k if it reads all its reference files. Until then it costs about 156 tokens; SKILL.md has 947 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 947 words, ~2,203 tokens.
.claude/skills/utility-pm-workflow-builder/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
This skill creates new multi-skill workflows for the pm-skills library. It
produces a Workflow Implementation Packet - a draft _workflows/<name>.md
file, a draft commands/workflow-<name>.md command, and the cross-cutting
update checklist - in a staging area for review before promotion to
canonical locations. The builder authors; it never executes a chain and it
never promotes its own output.
/chain run (orchestrator Mode B) proved reusable and its completion
output suggested promoting the chain to a durable workflow; hand this
skill the exact chain expression from that suggestion/chain
command or utility-pm-workflow-orchestrator directlyutility-pm-skill-builder,
utility-pm-skill-validate, or utility-pm-skill-iterate_workflows/<name>.md
directly; the overlap analysis below will point you there when coverage
is highAccept the idea in any of three entry forms, all converging on the same downstream flow:
measure-experiment-results -> discover-stakeholder-summary), usually
pasted from the orchestrator's completion suggestion, plus the context
the run used.If the idea is vague, ask ONE clarifying question (the recurring trigger and the final artifact), then proceed. Do not interrogate.
Scan the _workflows/ directory at run time for the current inventory
(list every *.md except README.md). Never rely on a remembered count
or a hardcoded list. Compare the idea against ALL existing workflows:
Kill gate (>70% coverage overlap): recommend, in order, (a)
customizing the existing workflow, (b) adding a step to it, or (c) just
using /chain for the occasional run. Do not proceed.
Why Gate (any meaningful overlap): ask for 2-3 specific scenarios where the existing workflows fail to produce what is needed. Do not pass the gate without that evidence or an explicit user override (record the override in the packet's Decision section).
Select and order the steps with the user. Apply the chain-expression
contract's validation rules at authoring time
(skills/utility-pm-workflow-orchestrator/references/PARSE-CONTRACT.md,
Mode B Chain Expression Contract):
skills/<name>/SKILL.md
by EXACT name. Never approximate or auto-correct; on a miss, refuse the
step and OFFER the closest real names (an offer, never a substitution).utility-pm-skill-*,
utility-pm-release-conductor, utility-pm-changelog-curator,
utility-update-pm-skills, foundation-prioritized-action-plan),
dispatch skills that fan out to sub-agents (utility-pm-critic,
utility-pm-workflow-orchestrator, and peers), and existing workflows
(a workflow never nests a workflow). Self-reference is impossible by
construction: this builder is itself Tier-3.Write the complete Workflow Implementation Packet to
_staging/workflows/<name>/ (gitignored; the same review model as the
skill builder). Never write to canonical locations.
_staging/workflows/<name>/
├── workflow.md <- draft _workflows/<name>.md
├── command.md <- draft commands/workflow-<name>.md
└── PACKET.md <- decision, overlap analysis, checklist, promotion stepsUse references/TEMPLATE.md as the packet format. The workflow draft must
carry the full section inventory the current _workflows/*.md files share
(see the TEMPLATE's embedded skeleton); the command draft mirrors the
existing commands/workflow-*.md shape, including one literal
skills/<name>/SKILL.md path per step and the $ARGUMENTS footer. Derive
a linear mermaid context-flow diagram from the final sequence (step names
as nodes, execution order as edges).
Present the packet and stop. The builder itself never promotes. On
approval, the user (or a follow-up session) moves the drafts to their
canonical paths and works the packet's Cross-Cutting Checklist, which
names every count and documentation surface that adding a workflow trips,
including the validator-blind .github/workflows/release.yml release-note
template. The builder never edits those cross-cutting files itself.
The packet follows references/TEMPLATE.md:
_workflows/<name>.md contentcommands/workflow-<name>.md contentSee references/EXAMPLE.md for one complete worked packet.
Before presenting the packet, verify:
_workflows/ directory (no remembered list, no hardcoded count)skills/<name>/SKILL.md path and ends with the $ARGUMENTS footer_staging/workflows/<name>/; no canonical path touched.github/workflows/release.yml release-note rowreferences/TEMPLATE.mdreferences/EXAMPLE.mdskills/utility-pm-workflow-orchestrator/references/PARSE-CONTRACT.md_workflows/sprint-planning.md, _workflows/customer-discovery.mdcommands/workflow-sprint-planning.mdskills/utility-pm-skill-builder/SKILL.md© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in skills/utility-pm-workflow-builder of product-on-purpose/pm-skills.
Open the folder on GitHubat commit 1cef1a9
Utility Pm Workflow Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Utility Pm Workflow Builder this skillproduct-on-purpose/pm-skills | 715 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Skill CreatorAzure/azqr | 795 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase | 10k | 11 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Claude Code Command Developmentanthropics/claude-plugins-official | 38k | 10 repos | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Plugin Structureanthropics/claude-plugins-official | 38k | 10 repos | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
anthropics/claude-plugins-official
Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.
anthropics/claude-plugins-official
Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.
rohitg00/ai-engineering-from-scratch
Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Categories
Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Utility Pm Workflow Builder is an agent skill from product-on-purpose/pm-skills. Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review.
Utility Pm Workflow Builder fits situations like: creating a new multi-skill workflow; promoting a repeated ad-hoc chain into a durable one.
Run `npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a claude-code`. Or copy the skill folder (skills/utility-pm-workflow-builder in product-on-purpose/pm-skills) into .claude/skills/utility-pm-workflow-builder in your project. Claude Code loads it when a task matches its description.
Run `npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a codex`. Or copy the skill folder (skills/utility-pm-workflow-builder in product-on-purpose/pm-skills) into .agents/skills/utility-pm-workflow-builder in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill utility-pm-workflow-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/utility-pm-workflow-builder, .gemini/skills/utility-pm-workflow-builder, .github/skills/utility-pm-workflow-builder and .opencode/skills/utility-pm-workflow-builder in your project.
SKILL.md names no scripts, command-line tools or credentials: Utility Pm Workflow Builder is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Utility Pm Workflow Builder is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.9k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Utility Pm Workflow Builder: Skill Creator (Azure/azqr, 795 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Claude Code Command Development (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 715 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.
Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.