# Workshop Technical Setup

> Workshop Technical Setup is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

- Skill name: `workshop-technical-setup`
- Category: [Productivity](https://www.openparable.com/skill/productivity/1)
- Source: https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/workshop-technical-setup/SKILL.md
- Repository: majiayu000/claude-skill-registry (498 GitHub stars when collected)

## 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.

---

Source: https://www.openparable.com/skill/productivity/workshop-technical-setup (OpenParable). Cite the canonical URL above.
