Use to codify sales rules of engagement, escalation paths, and exception
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill roe-governance-gtmagents-gtm-agents --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Roe Governance Gtmagents Gtm Agents?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-roe-governance-gtmagents-gtm-agents)More formats (shields.io, HTML) on the badges page.
---
name: roe-governance
description: Use to codify sales rules of engagement, escalation paths, and exception
workflows.
---
# Rules of Engagement Governance Skill
## When to Use
- Rolling out new territory models with updated ownership rules.
- Resolving channel, partner, or segment conflicts.
- Documenting escalation paths for deal desk, pricing, or product requests.
## Framework
1. **Stakeholder Map** – identify sales, CS, partner, legal, and ops owners.
2. **Rule Definition** – outline assignment logic, routing triggers, and timeframe SLAs.
3. **Exception Handling** – document approval tiers, SLAs, and data required for review.
4. **Enablement & Change Mgmt** – create briefs, FAQs, and office-hour plans.
5. **Compliance & Audit** – track decision logs, metrics, and quarterly refresh cadence.
## Templates
- ROE decision tree and ownership matrix.
- Exception request form + approval checklist.
- Communication kit (email, deck, FAQ) for GTM + partner teams.
## Tips
- Keep rules simple enough for reps/channel partners to recall.
- Tie every rule to a KPI (speed, fairness, CX) to reinforce intent.
- Archive exceptions in a shared system to surface policy drift.
---
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.