Agent skill

workshop-technical-setup

Help with workshop technical setup. Use when a customer asks about required setup, tools, or preparation.

View SKILL.md on GitHub Repository
Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/workshop-technical-setup

Metadata

Additional technical details for this skill

metrics
sample_size: 28 avg_thread_length: 4.11 top_phrases: - phrase: "on thu 22 jan" count: 5 percent: 17.9 - phrase: "thu 22 jan 2026" count: 5 percent: 17.9 - phrase: "22 jan 2026 at" count: 5 percent: 17.9 - phrase: "let me know if" count: 5 percent: 17.9 - phrase: "jan 22 2026 at" count: 4 percent: 14.3 - phrase: "am j sanchez email" count: 4 percent: 14.3 - phrase: "j sanchez email wrote" count: 4 percent: 14.3 - phrase: "kent c dodds me" count: 4 percent: 14.3 - phrase: "c dodds me kentcdodds" count: 4 percent: 14.3 - phrase: "dodds me kentcdodds com" count: 4 percent: 14.3
validation
required_phrases: - "on thu 22 jan" forbidden_patterns: [] max_length: 500
sample size
28
related skills 
[
    "course-difficulty-concern",
    "api-documentation-question",
    "technical-issue-course-content",
    "workshop-attendance-confirmation",
    "lesson-content-question"
]
trigger phrases 
[
    "workshop technical",
    "technical setup",
    "setup customer"
]

SKILL.md

Workshop Technical Setup and Preparation

Response Patterns (from samples)

Common openings:

  • "Oh no 😢​"
  • "Hello,"
  • "Thank you!"

Common core lines:

  • "wrote:"
  • "– Kent"
  • "Thanks for reaching out!"

Common closings:

  • "If you have coding questions, you can ask them in the community Discord channel we've set up here."
  • "Best,"
  • "I am really sorry about this. I have changed the permissions so that the form can actually be filled now 😅"

Phrases That Work (4-gram frequency)

  • "on thu 22 jan" — 5 (17.9%)
  • "thu 22 jan 2026" — 5 (17.9%)
  • "22 jan 2026 at" — 5 (17.9%)
  • "let me know if" — 5 (17.9%)
  • "jan 22 2026 at" — 4 (14.3%)
  • "am j sanchez email" — 4 (14.3%)
  • "j sanchez email wrote" — 4 (14.3%)
  • "kent c dodds me" — 4 (14.3%)
  • "c dodds me kentcdodds" — 4 (14.3%)
  • "dodds me kentcdodds com" — 4 (14.3%)

Tone Guidance (observed)

  • Openings trend toward: "Oh no 😢​"
  • Closings often include: "If you have coding questions, you can ask them in the community Discord channel we've set up here."

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.

Didn't find tool you were looking for?

Be as detailed as possible for better results