Skip to content
Back to skills

Sales Kit

ASecurity

Create and govern the evidence-backed material sellers and buying champions use at a specific decision stage: sales and pitch decks, one-pagers, objection libraries, battlecards, ROI and value tools, demo scripts, talk tracks, case briefs, proposals, playbooks, and buyer-role cards. Use when a sales moment needs an asset; use outbound-prospecting for finding and contacting prospects and revenue-handoff for pipeline operations.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
ai-agentsgosecurity

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 24, 2026

npx -y skills add MTEnt/special-skills --skill sales-kit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sales Kit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sales Kit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mtent-sales-kit/badge)](https://www.skillsdirectory.com/skills/mtent-sales-kit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sales-kit
description: Create and govern the evidence-backed material sellers and buying champions use at a specific decision stage: sales and pitch decks, one-pagers, objection libraries, battlecards, ROI and value tools, demo scripts, talk tracks, case briefs, proposals, playbooks, and buyer-role cards. Use when a sales moment needs an asset; use outbound-prospecting for finding and contacting prospects and revenue-handoff for pipeline operations.
license: MIT
metadata:
  version: "2.0.0"
  author: MTEnt
---

# Sales Kit

Build the asset the sales moment requires. A generic deck is not the default answer to every enablement problem.

If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [enablement-system.md](references/enablement-system.md) for each asset's structure, proof rules, governance, and output.

## Operating contract

1. Define audience role, buying stage, decision or risk, seller behavior, alternatives, proof, delivery format, owner, and update trigger.
2. Inspect current product, price, implementation, security, legal, customer proof, and competitive evidence.
3. Choose and complete the narrowest useful asset, stating claims, proof, source dates, better-fit competitor cases, and seller concessions.
4. Include usage guidance, editable source, owner, review date, and expiry condition.

Do not invent customer quotations, ROI, security posture, product behavior, competitor failures, or deal outcomes, and never present modeled value as guaranteed savings.

## Return

The finished asset, usage notes, claim and proof sources, role variants, seller guidance, owner, review date, and update condition.

Files in this skill

  • SKILL.md1.7 KB
  • agents/openai.yaml250 B
  • references/enablement-system.md2.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…