Agent skill
pricing-inquiry
Customer asks about course pricing, pricing models, or pricing availability.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/pricing-inquiry
SKILL.md
Pricing Information
Response Patterns (from samples)
Common openings:
- "Hi,"
- "Hey,"
- "Hello,"
Common core lines:
- "Thanks for reaching out!"
- "Best,"
- "Thanks for your interest in the course!"
Common closings:
- "Best,"
- "Please let me know if you have any further questions!"
- "Let me know if you have any additional questions!"
Phrases That Work (4-gram frequency)
- "let me know if" — 90 (17.2%)
- "me know if you" — 86 (16.4%)
- "know if you have" — 86 (16.4%)
- "if you have any" — 53 (10.1%)
- "thanks for reaching out" — 52 (9.9%)
- "https www totaltypescript com" — 50 (9.6%)
- "for your interest in" — 43 (8.2%)
- "thanks for your interest" — 40 (7.6%)
- "your interest in the" — 40 (7.6%)
- "interest in the course" — 40 (7.6%)
Tone Guidance (observed)
- Openings trend toward: "Hi,"
- Closings often include: "Best,"
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.
Validation
Draft must:
- Include at least one of the required phrases from the validation block
- Stay consistent with the observed response patterns above
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?