sales-marketing-sla

sales-marketing-sla is a skill for Claude Code from matellez/claude-skills. It costs 219 tokens per session (3,059 once invoked), scanned A, original, MIT.

A framework for the written agreement between marketing and sales about lead quality, handoff, and follow-up. A lead is a potential customer, and an SLA is a shared agreement about what each team must do and when.

In plain words
What is it for?
Use it to define marketing-qualified leads, set handoff and response rules, document responsibilities, and measure whether sales follows up.
Why use it?
It removes arguments caused by unclear definitions of a good lead and unclear responsibility after handoff. Both teams can work from the same measurable expectations.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to define marketing-qualified leads, set handoff and response rules, document responsibilities, and measure whether sales follows up.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/matellez/claude-skills/sales-marketing-sla
Install

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.

Any agent
npx skills add matellez/claude-skills --skill sales-marketing-sla
Clone the repo
git clone --depth 1 https://github.com/matellez/claude-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for sales-marketing-sla

README.md
[![agentmods](https://agentmods.dev/badge/skills/matellez/claude-skills/sales-marketing-sla/github.svg)](https://agentmods.dev/skills/matellez/claude-skills/sales-marketing-sla)
Your own site
<a href="https://agentmods.dev/skills/matellez/claude-skills/sales-marketing-sla"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/sales-marketing-sla/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.

agentmods 80×15 button for sales-marketing-sla

Your own site · 80×15
<a href="https://agentmods.dev/skills/matellez/claude-skills/sales-marketing-sla"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/sales-marketing-sla.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 219 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,059 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00219 $0.03059
Opus 5 $0.00110 $0.01529
Sonnet 5 $0.00044 $0.00612
Haiku 4.5 $0.00022 $0.00306

Measured 12d ago against content hash 0d2a4b474997, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sales-marketing-sla 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 12d ago.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

leadership/sales-marketing-sla/SKILL.md · 361 lines

How it starts

The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sales-Marketing SLA: Defining, Documenting, and Enforcing the Handoff

This skill builds the operational agreement between marketing and sales around lead quality and follow-up. The marketing-to-sales handoff is the most common source of revenue leakage in B2B SaaS. Marketing generates leads that sales does not work. Sales blames marketing for bad lead quality. Marketing blames sales for ignoring good leads. Both sides have data that supports their position. Neither side has a shared definition of what a good lead actually is.

The problem is almost never lead quality or sales effort in isolation. It is the absence of a written, agreed-upon, and measured definition of what marketing is responsible for delivering and what sales is responsible for doing with it. This skill builds that definition.


HOW TO SET UP THIS SKILL

This skill works out of the box. For more specific output, provide:

  • Average deal size and sales cycle length
  • Current MQL definition if one exists
  • Current SLA if one exists, even informally
  • How many MQLs marketing generates per month and what percentage sales works within the expected timeframe
  • The primary source of conflict between sales and marketing right now
  • Whether this is being built from scratch or rebuilt after a breakdown

Why Most MQL Definitions Fail

Most MQL definitions fail for one of three reasons.

Reason 1: The definition was built by marketing without sales input.

Marketing defined an MQL based on what data they could track: a form fill, a content download, a demo request. Sales was told about the definition after it was built. Sales never agreed to it, never believed in it, and never prioritized MQLs that came from that definition.

Reason 2: The definition is based on activity, not fit.

An MQL defined as "any contact who downloads a whitepaper" captures students, competitors, and consultants doing research. It does not filter for the companies that can actually buy. Activity-based MQL definitions produce high volumes of low-quality leads and erode sales confidence in the MQL program entirely.

Read the full file on GitHub · 361 lines

Changes

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.

  1. 12d ago First seen · 361 lines · 219 tokens per session scan A 0d2a4b474997

Subscribe to this mod's changes

sales-marketing-sla is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 219 tokens to every session and 3,059 once invoked, about $0.0011 per session on Opus 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-08-31.

Related

Other skills, from other repositories

skill-builder

Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.

yusufkaraaslan/Skill_Seekers · 38 tokens

market-research-workflow

Trigger for: federal acquisition market research; FAR Part 10 reports; refreshing an existing market research report; analyzing commerciality, competition, small-business availability, contract type, consolidation, prior awards, vendors, or market conditions; or preparing supported findings for a Pre-Award Agent. A…

1102tools-dev/federal-contracting-skills · 159 tokens

acquisition-policy-workflow

Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing…

1102tools-dev/federal-contracting-skills · 115 tokens

igce-builder-lh-tm

Trigger for: Labor-Hour IGCE, LH estimate, Time-and-Materials IGCE, T&M estimate, burdened hourly rate, burden multiplier, labor-category ceiling hours, materials estimate, proposed LH/T&M rate validation, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable LH/T&M estimates using BLS OEWS…

1102tools-dev/federal-contracting-skills · 147 tokens

rudder-data-graphs

Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.

rudderlabs/rudder-agent-skills · 40 tokens

rudder-typer-workflow

Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.

rudderlabs/rudder-agent-skills · 43 tokens