Orchestrate Pm Alignment

What it does

When your agent uses it

• A product manager (or someone managing products) wants to reflect on their own performance
• Check their behaviors against a standard of excellence
• Practice a difficult scenario
• Audit a decision

Example prompts

• “am I being a good PM?”
• “check how I”
• “coach me”
• “/orchestrate-pm-alignment”

What it can do on your machine

Read from SKILL.md and the folder at commit 43a0566. It shows what the files ask for, not the result of running them.

• Tool permissions

  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.

• Runs code

  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.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Orchestrate Pm Alignment loads about 1.5k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 195 tokens; SKILL.md has 685 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~195

When it runs · the whole SKILL.md, loaded when a task matches

~1.5k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~3.7k

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.

Safety

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.

SKILL.md

The full file from gnurio/nurijanian-skills at commit 43a0566, republished under its MIT licence (© gnurio). 685 words, ~1,521 tokens.

name

orchestrate-pm-alignment

description

PM alignment coach and router. Use this skill whenever a product manager (or someone managing products) wants to reflect on their own performance, check their behaviors against a standard of excellence, get coaching, practice a difficult scenario, audit a decision, or understand their blind spots. Trigger on phrases like: "am I being a good PM?", "check how I'm doing", "coach me", "how would my team see me?", "let's roleplay a scenario", "audit my decision", "what am I missing as a PM", "what are my blind spots", "test me as a PM", "I want to improve as a PM", or any time a PM is reflecting on their own practice. Also trigger when someone mentions PM self-improvement, PM development, or wanting to think through how they handled a team situation.

pm_context = {
  "role": null,             # their title/level if shared
  "team": null,             # their team's makeup if described
  "situations_discussed": [],
  "decisions_audited": [],
  "clusters_with_gaps": [], # which of the 7 clusters they're weak in
  "clusters_with_strengths": [],
  "blind_spots_identified": [],
  "patterns": []            # recurring themes across the session
}

© gnurio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/orchestrate-pm-alignment of gnurio/nurijanian-skills.

• SKILL.md
• references/pm-excellence-behaviors.md

Open the folder on GitHubat commit 43a0566