Sub-skill of canned-responses: Required Customization (+2).
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill required-customization --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Required Customization?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-required-customization)More formats (shields.io, HTML) on the badges page.
---
name: canned-responses-required-customization
description: 'Sub-skill of canned-responses: Required Customization (+2).'
version: 1.0.0
category: business
type: reference
scripts_exempt: true
---
# Required Customization (+2)
## Required Customization
Every templated response MUST be customized with:
- Correct names, dates, and reference numbers
- Specific facts of the situation
- Applicable jurisdiction and regulation
- Correct response deadlines based on when the inquiry was received
- Appropriate signature block and contact information
## Tone Adjustment
Adjust tone based on:
- **Audience**: Internal vs. external, business vs. legal, individual vs. regulatory authority
- **Relationship**: New counterparty vs. existing partner vs. adversarial party
- **Sensitivity**: Routine inquiry vs. contentious matter vs. regulatory investigation
- **Urgency**: Standard timeline vs. expedited response needed
## Jurisdiction-Specific Adjustments
- Verify that cited regulations are correct for the requester's jurisdiction
- Adjust timelines to match applicable law
- Include jurisdiction-specific rights information
- Use jurisdiction-appropriate legal terminology
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
