Use to manage workflows, compliance, and measurement for customer references.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add Microck/ordinary-claude-skills --skill reference-ops --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Reference Ops?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/microck-reference-ops-ordinary-claude-skills)More formats (shields.io, HTML) on the badges page.
---
name: reference-ops
description: Use to manage workflows, compliance, and measurement for customer references.
---
# Reference Operations Skill
## When to Use
- Running reference matching, scheduling, and follow-up processes.
- Auditing reference utilization, fatigue, and consent records.
- Reporting on advocacy impact for sales leadership.
## Framework
1. **Request Intake** – standardize forms, qualification criteria, and SLA expectations per deal stage.
2. **Matching Logic** – map requests to advocates by persona, industry, use case, language, and availability.
3. **Logistics & Compliance** – schedule calls, provide briefing docs, capture approvals, and log NDAs.
4. **Post-call Workflow** – collect feedback from both parties, update CRM entries, and issue rewards.
5. **Analytics & Governance** – monitor utilization, fatigue thresholds, and gaps by segment.
## Templates
- Reference request form template.
- Matching matrix (request attributes → advocate tags).
- Follow-up checklist and feedback survey.
## Tips
- Integrate with CRM to auto-create tasks and close the loop with reps.
- Flag overused advocates and rotate in new voices regularly.
- Share monthly scorecards with GTM teams to highlight wins and needs.
---
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!
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.
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', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
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.