Content Design
OfficialAutomatically generate website copy, email subject lines, and social media posts tailored to your brand's voice.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
n8n:content-design, not the name it is listed under, so the command below uses that name.- 1
Run this in your project
terminal$ npx skills add n8n-io/n8n --skill n8n:content-design -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
n8n-io
Matched to the vendor's own GitHub organisation.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned n8n-io/n8n at 9f5c752cd1.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 9f5c752cd1
- Scanned
- 1 file, 335 lines
About this skill
What it does
This skill enables AI agents to generate, review, and audit UI copy for SaaS products, specifically within the n8n ecosystem. It specializes in crafting clear, concise labels, error messages, tooltips, and other interface elements, prioritizing user understanding and adhering to established terminology, voice, and tone guidelines. The skill can draft new copy options, critique existing content, or scan files for inconsistencies.
When to use it
- Generating UI copy for new features or components within n8n.
- Reviewing existing UI copy to ensure consistency with brand guidelines and user experience best practices.
- Auditing codebases (Vue components, i18n JSON) for content-related errors or inconsistencies.
- Improving empty states, loading states, and error messages for a more user-friendly experience.
- Evaluating proposed feature names to ensure clarity within the product interface.
Key capabilities
- Drafting UI Copy: Generates 1-3 ranked options for new copy, including surface target, i18n key suggestion, and rationale.
- Reviewing Existing Copy: Provides a table of issues (terminology, tone, grammar) with suggested fixes.
- Auditing Codebases: Scans files for guideline violations using Grep and Glob patterns.
- Adherence to Guidelines: Checks copy against terminology glossaries, voice & tone guidelines, and existing UI patterns.
- Prioritizes Clarity: Focuses on concise language and user needs before injecting personality.
Example prompts
- "Draft a tooltip for the 'Save' button in the workflow editor."
- "Review this error message: 'An unexpected error occurred.' Suggest improvements."
- "Audit all Vue components under
packages/frontend/editor-ui/src/**/*.vuefor terminology violations."
Tips & gotchas
- The skill requires access to relevant files (Vue components, i18n JSON) for auditing and review.
- It prioritizes clarity over personality; avoid prompts requesting overly creative or informal language.
- When drafting copy, be specific about the surface (button, modal, tooltip, etc.) and user action/system state.