Agent skill
course-difficulty-concern
Customer expresses concern about course difficulty level or prerequisite knowledge needed.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/course-difficulty-concern
SKILL.md
Course Difficulty or Prerequisites
Response Patterns (from samples)
Common openings:
- "Hey,"
- "Hello,"
- "Hi there,"
Common core lines:
- "Thanks for reaching out!"
- "Best,"
- "Hey,"
Common closings:
- "Best,"
- "We've initiated a refund. It can take 5-10 days for the banks to reconcile and return the money to your account."
- "It may take 5-10 business days for the refunded amount to show up in your account, depending on how quickly it's processed by your financial institution."
Phrases That Work (4-gram frequency)
- "let me know if" — 10 (13%)
- "me know if you" — 8 (10.4%)
- "know if you have" — 8 (10.4%)
- "if you have any" — 8 (10.4%)
- "thanks for reaching out" — 8 (10.4%)
- "thanks for the feedback" — 5 (6.5%)
- "feedback and giving the" — 5 (6.5%)
- "and giving the course" — 5 (6.5%)
- "giving the course a" — 5 (6.5%)
- "the course a go" — 5 (6.5%)
Tone Guidance (observed)
- Openings trend toward: "Hey,"
- 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?