Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ArrowsHQ/arrows-sales-skills --skill arrows-process-gaps-reportgit clone --depth 1 https://github.com/ArrowsHQ/arrows-sales-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/arrowshq/arrows-sales-skills/arrows-process-gaps-report)<a href="https://agentmods.dev/skills/arrowshq/arrows-sales-skills/arrows-process-gaps-report"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-process-gaps-report/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/arrowshq/arrows-sales-skills/arrows-process-gaps-report"><img src="https://agentmods.dev/badge/skills/arrowshq/arrows-sales-skills/arrows-process-gaps-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00214 | $0.14935 |
| Opus 5.5 | $0.00086 | $0.05974 |
| Sonnet 5.5 | $0.00043 | $0.02987 |
| Haiku 4.5 | $0.00021 | $0.01494 |
Grade A, and why
arrows-process-gaps-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 558 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finds what's falling through the cracks, measured against how this person (or their team) says they sell. Not a pipeline review of every deal: only the gaps, the money behind them, and what to do this week.
| Part | What it answers | Where the standard comes from |
|---|---|---|
| Headline | $ at risk, $ gone quiet, promises missed this month | CRM, email, calls |
| Part 1: Gaps by deal | What should be getting done and isn't: at risk (red), other gaps (gold), on track (green), with one line on why | Their stages, methodology and rules (arrows-sales-process.md, arrows-how-we-work.md), or the baseline below |
| Part 2: Habits | What they want to be doing that isn't happening, with counts | ## What I do on my best deals and ## What slips (arrows-how-i-work.md), ## Every rep, every deal (arrows-how-we-work.md) |
| This week | The 3–5 moves that close the biggest gaps | Both parts |
| By rep (leaders) | Each rep's gaps and habits side by side, and what the top rep does that others don't | Same, per owner |
Delivered as a visual report they can share (the same page every run), with a short summary in the chat. No questions unless the scope is truly unclear.
Progress
Post a short progress line once at the top, then one line per source as it finishes, with a real number:
Sales Skills by Arrows · Process gaps report ■■□□□ Reading your calls
✓ CRM: 38 open deals ($1.2M), 4 owners
✓ Calls: 22 calls in the last 30 days
✓ Email: checked 31 threads for promised follow-ups
– Calendar: not connected (using CRM meeting dates)
Stages: Reading your CRM / Reading your calls / Reading your email ■□□□□ · Checking against your process ■■■□□ · Building your report ■■■■□ · Done ■■■■■.
Step 1: Scope and standard
Who's covered. Use scope if given. Otherwise read ## About me in arrows-how-i-work.md (rep, leader, or both). With no profile, match their email to a CRM owner: owns most open deals → rep; others own most → leader; a real share of both → both. Seeing every deal proves nothing (small-company reps often have admin access).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed · +1 lines 7db6fec7982a
- 9d ago Changed · -58 tokens per session 624a67613bee
- 10d ago First seen · 557 lines · 272 tokens per session scan A 27c62d8642fd
arrows-process-gaps-report is a skill published in the GitHub repository ArrowsHQ/arrows-sales-skills (4 stars, last pushed today), licensed Apache-2.0. It adds 214 tokens to every session and 14,935 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-06.
Other skills, from other repositories
evm
Help users answer one question: "Are we on track?" using Earned Value Management metrics. This skill replaces gut-feel status reporting and traffic-light dashboards with four computed numbers (SV, SPI, CV, CPI) that tell you exactly where a project stands — in schedule and in budget — at any point in time.
geo-prospect
CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
ai-assisted-performance-review
Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or…
role-redesign-for-ai
Redesign a job role that AI now does a large part of — deliberately, instead of quietly expecting the same headcount to absorb 140% output. Use when AI has changed what a role spends time on, when writing a revised role charter or job description post-AI, when a team asks 'what is my job now', or when planning…