smithery/gtmagents

pricing-governance

Use to run pricing councils, track decisions, and enforce approval workflows.

Installation

$ npx skills add smithery/gtmagents --skill pricing-governance

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,239 B
  • docs SUMMARY.md 103 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Pricing Governance Playbook Skill

When to Use

  • Facilitating pricing council meetings or steering committees.
  • Logging approvals, assumptions, and launch timing for pricing changes.
  • Auditing pricing experiments or discount policy adjustments.

Framework

  1. Council Charter – define members, meeting cadence, decision rights, and escalation paths.
  2. Decision Log – capture proposals, outcomes, rationales, and follow-up actions.
  3. Approval Matrix – map thresholds (discount %, price change scope) to required approvers.
  4. Communication Hooks – standardize templates for stakeholder updates and launch checklists.
  5. Audit Trail – store artifacts (models, decks, FAQs) and post-launch performance reviews.

Templates

  • Council agenda + minutes doc.
  • Decision log spreadsheet with filters.
  • Launch readiness checklist with owners/dates.

Tips

  • Keep logs centralized to reduce drift across regions.
  • Pair with enablement-kit to ensure decisions convert to frontline training.
  • Schedule retro sessions at 30/60/90 days post-launch to validate assumptions.