Claude-skill-registry learning-path-guidance

Recommend learning paths. Use when a customer asks which courses to take and in what order.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/learning-path-guidance" ~/.claude/skills/majiayu000-claude-skill-registry-learning-path-guidance && rm -rf "$T"
manifest: skills/data/learning-path-guidance/SKILL.md
source content

Learning Path and Course Sequencing

Response Patterns (from samples)

Common openings:

  • "Hello,"
  • "Hey,"
  • "Hi there,"

Common core lines:

  • ">>"
  • ">"
  • "Best,"

Common closings:

  • "Best,"
  • "P.S. I'm in the process of improving the onboarding experience with the workshop app. Part of that is a new tutorial that uses the app to teach you how to use it! Check it out here: epicweb.dev/tips/setup-the-epic-workshop-app-tutorial-xrh8i"
  • "Happy learning!"

Phrases That Work (4-gram frequency)

  • "https www totaltypescript com" — 16 (21.6%)
  • "totaltypescript com typescript learning" — 11 (14.9%)
  • "com typescript learning path" — 11 (14.9%)
  • "www totaltypescript com typescript" — 10 (13.5%)
  • "let me know if" — 10 (13.5%)
  • "me know if you" — 9 (12.2%)
  • "know if you have" — 6 (8.1%)
  • "if you have anymore" — 6 (8.1%)
  • "you have anymore questions" — 5 (6.8%)
  • "have anymore questions best" — 5 (6.8%)

Tone Guidance (observed)

  • Openings trend toward: "Hello,"
  • 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
  • NOT introduce policy details that are not present in the verified response lines above.