# Team License Purchase

> Handle team and bulk license purchases. Use when an organization asks to buy multiple licenses for a team.

- Skill: `majiayu000/team-license-purchase` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/team-license-purchase`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/team-license-purchase/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/team-license-purchase

---

# Team License Purchase

## Response Patterns (from samples)

Common openings:
- "Hello,"
- "Hi,"
- "Hey David,"

Common core lines:
- "Thanks for your interest in the course!"
- "Thanks for reaching out!"

Common closings:
- "Let me know if you have any additional questions!"
- "Best,"
- "Please let me know if you have any further questions!"

## Phrases That Work (4-gram frequency)

- "let me know if" — 177 (34.8%)
- "https epicreact dev coupon" — 161 (31.7%)
- "me know if you" — 148 (29.1%)
- "know if you have" — 133 (26.2%)
- "if you have any" — 132 (26%)
- "please let me know" — 68 (13.4%)
- "for your interest in" — 56 (11%)
- "thanks for your interest" — 53 (10.4%)
- "your interest in the" — 51 (10%)
- "interest in the course" — 51 (10%)

## Tone Guidance (observed)

- Openings trend toward: "Hello,"
- Closings often include: "Let me know if you have any additional questions!"

## What NOT To Do

- Don't introduce policy details that are not present in the verified response lines above.
- Don't paraphrase or reframe the customer's question in a way that changes meaning.
- Don't add refund/discount promises unless they appear in the extracted responses for this topic.
- Don't invent discount codes or promotional links.
- Don't quote custom bulk pricing unless it is explicitly in the verified response lines above.

## Validation

Draft must:
- [ ] Include at least one of the required phrases from the validation block
- [ ] Stay consistent with the observed response patterns above
- [ ] NOT introduce policy details that are not present in the verified response lines above.