Create and refine sales playbooks, deal strategies, MEDDPICC analyses, customer decks, and outreach sequences. Use for any sales methodology work, pipeline review, or go-to-market planning.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Build sales artifacts grounded in MEDDPICC methodology and Espen's enterprise AI sales experience.
For every deal analysis, score each dimension (1-3: weak/moderate/strong) and identify gaps:
| Dimension | Question |
|---|---|
| Metrics | What measurable outcomes does the customer expect? |
| Economic Buyer | Who has budget authority? Have we engaged them? |
| Decision Criteria | What technical/business criteria drive the decision? |
| Decision Process | What are the steps, timeline, and approvals needed? |
| Paper Process | What legal/procurement steps are required to close? |
| Implicate the Pain | What happens if they do nothing? Is the pain urgent? |
| Champion | Who inside is selling on our behalf? Can they mobilize? |
| Competition | Who else is being evaluated? What's our differentiation? |
When creating a playbook, use this structure:
# [Product/Segment] Sales Playbook
## Ideal Customer Profile
- Industry, size, tech stack, pain signals
## Value Proposition
- 1-sentence elevator pitch
- 3 key differentiators vs. status quo
- 3 key differentiators vs. competition
## Discovery Questions
- 5-7 open questions that uncover MEDDPICC dimensions
## Objection Handling
| Objection | Response Framework |
|-----------|-------------------|
## Proof Points
- Customer stories, metrics, case studies
## Competitive Positioning
- Feature comparison, narrative reframes
## Sales Motion
- Prospecting → Discovery → Demo → Proposal → Close
- Time-to-close benchmark, typical deal size
# [Campaign Name] Outreach Sequence
## Target Persona
Role, industry, pain points, trigger events
## Sequence (10-14 days)
### Day 1 — Email 1: Pain-led hook
### Day 3 — LinkedIn connect + note
### Day 5 — Email 2: Social proof
### Day 8 — Call attempt + voicemail
### Day 10 — Email 3: Insight share
### Day 14 — Email 4: Break-up
## Personalization Variables
- {{company_pain}}, {{relevant_metric}}, {{mutual_connection}}
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Audit, generate, update, and lint AGENTS.md files across all projects. Use when asked to check project context files, scaffold AGENTS.md for new projects, update stale ones, or run a cross-project audit.
日本語の概要は準備中です。原文の説明を表示しています。
Draft, edit, and publish blog posts for e9n.dev. Use when creating new posts, editing drafts, or refining existing content. Handles Eleventy frontmatter, Tailwind formatting, and Espen's authentic voice.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a full operational status report for the Aivena bot. Checks all subsystems: extensions, webserver, Telegram, chat bridge, heartbeat, cron, database, memory, CRM, calendar, task management, jobs/telemetry, and storage. **Triggers — use this skill when:** - User asks for "status", "bot status", "system status", "operational status" - User asks "is everything running?", "how's Aivena doing?" - User says "health check", "diagnostics", "systems check" - User asks "what's the state of the bot?"
日本語の概要は準備中です。原文の説明を表示しています。
Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate cmux terminal panes — split terminals, run parallel processes, read output from other panes, and use the built-in browser. Use when working inside cmux and you need to run a dev server, watch tests, spawn sub-agents, or preview web pages.
日本語の概要は準備中です。原文の説明を表示しています。
Review code for quality, security, performance, and maintainability. Use when reviewing PRs, auditing a codebase, or refactoring. Covers TypeScript, Node.js, infrastructure-as-code, and full-stack web apps.
日本語の概要は準備中です。原文の説明を表示しています。