Agent skill
student-discount-request
Student or academic inquirer asks about educational discounts.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/student-discount-request
SKILL.md
Student Discount Request
Response Patterns (from samples)
Common openings:
- "Hi,"
- "Hey,"
- "Hello,"
Common core lines:
- "Thanks for your interest in the course!"
- "Hi,"
- "Thanks for reaching out!"
Common closings:
- "Best,"
- "The upgrade option is only available to move up to the Pro package from whichever level you start on. So you can upgrade from Basic or Standard to Pro, but not from Basic to Standard as a half-step."
- "https://www.totaltypescript.com/tutorials"
Phrases That Work (4-gram frequency)
- "thanks for your interest" — 33 (28.9%)
- "for your interest in" — 33 (28.9%)
- "interest in the course" — 33 (28.9%)
- "your interest in the" — 28 (24.6%)
- "https www totaltypescript com" — 23 (20.2%)
- "in the course we" — 23 (20.2%)
- "to the pro package" — 21 (18.4%)
- "thanks for reaching out" — 20 (17.5%)
- "we don't currently offer" — 17 (14.9%)
- "to upgrade to the" — 16 (14%)
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?