Agent skill
partnership-collaboration-inquiry
Third parties inquire about partnerships, sponsorships, or promotional opportunities.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/partnership-collaboration-inquiry
SKILL.md
Partnership and Collaboration Inquiry
Response Patterns (from samples)
Common openings:
- "Hi there,"
- "Hey,"
- "Hello,"
Common core lines:
- "Best,"
- "https://x.com/mattpocockuk"
- "https://bsky.app/profile/mattpocock.com"
Common closings:
- "Best,"
- "Thanks for reaching out, but we politely decline."
- "We support any questions related to course and functionality, you’ll have to contact Matt directly for this kind of collaboration. We don’t have Matt’s email, you’ll have to reach out on his personal website or Twitter."
Phrases That Work (4-gram frequency)
- "support any questions related" — 177 (36.5%)
- "any questions related to" — 177 (36.5%)
- "we support any questions" — 162 (33.4%)
- "questions related to the" — 152 (31.3%)
- "related to the course" — 152 (31.3%)
- "to the course and" — 152 (31.3%)
- "the course and platform" — 151 (31.1%)
- "course and platform functionality" — 151 (31.1%)
- "https bsky app profile" — 151 (31.1%)
- "and platform functionality but" — 150 (30.9%)
Tone Guidance (observed)
- Openings trend toward: "Hi there,"
- 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?