Pull Request
cloudposse/atmos
PR workflow: pick the right semver label (no-release / patch / minor / major), decide when to add a changelog blog post, when to update the roadmap, and how to do each correctly.
Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content.
Install Dynamo Content Designer
$ npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-content-designer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dynamo-content-designer .claude/skills/dynamo-content-designer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dynamo-content-designer" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-content-designer into .claude/skills/dynamo-content-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-content-designer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-content-designerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-content-designer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/dynamo-content-designer .agents/skills/dynamo-content-designer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dynamo-content-designer" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-content-designer into .agents/skills/dynamo-content-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-content-designer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-content-designer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/dynamo-content-designer .cursor/skills/dynamo-content-designer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dynamo-content-designer" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-content-designer into .cursor/skills/dynamo-content-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-content-designer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DynamoDS/Dynamo.git --path .claude/skills/dynamo-content-designer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-content-designer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/dynamo-content-designer .gemini/skills/dynamo-content-designer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dynamo-content-designer" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-content-designer into .gemini/skills/dynamo-content-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-content-designer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DynamoDS/Dynamo dynamo-content-designerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/dynamo-content-designer .github/skills/dynamo-content-designer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dynamo-content-designer" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-content-designer into .github/skills/dynamo-content-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-content-designer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DynamoDS/Dynamo dynamo-content-designer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DynamoDS/Dynamo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/dynamo-content-designer .opencode/skills/dynamo-content-designer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dynamo-content-designer" agent skill from https://github.com/DynamoDS/Dynamo/tree/master/.claude/skills/dynamo-content-designer into .opencode/skills/dynamo-content-designer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dynamo-content-designer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dynamo-content-designer- GitHub stars
- 2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 712 words
- Files
- 7 (incl. assets)
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content.
- Works in 5 steps: Planning Phase → Drafting Phase → Technical Review → …
- The user mentions writing documentation
- SKILL.md covers Trigger Conditions, Core Responsibilities, Writing Principles and Content Types and References, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dynamo Content Designer is an agent skill from DynamoDS/Dynamo. Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content. Use when the user mentions writing documentation, blog posts, Primer articles, feature documentation, or starting a substantial writing task. For release notes specifically (curating, drafting, and publishing the wiki Release-Notes page), use the dynamo-release-notes skill instead.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including assets (for example `assets/blog-posts.md`, `assets/feature-documentation.md` and `assets/node-descriptions.md`).
It sits in Writing & Content, covering Technical writing, Changelog and release notes and Blog and article writing. The repository describes itself as: Open Source Graphical Programming for Computational Design and Automation. The licence is Apache-2.0.
When your agent uses it
- The user mentions writing documentation
- Primer articles
- Feature documentation
- Starting a substantial writing task
Example prompts
- “/dynamo-content-designer”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 55647ad. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dynamo Content Designer loads about 1.6k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 712 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from DynamoDS/Dynamo at commit 55647ad, republished under its Apache-2.0 licence (© DynamoDS). 712 words, ~1,599 tokens.
Download SKILL.mdSave it as
.claude/skills/dynamo-content-designer/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- dynamo-content-designer
- description
- Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content. Use when the user mentions writing documentation, blog posts, Primer articles, feature documentation, or starting a substantial writing task. For release notes specifically (curating, drafting, and publishing the wiki Release-Notes page), use the dynamo-release-notes skill instead.
- metadata.version
- 1.0
Dynamo Content Designer
You are a Content Designer on the Dynamo team specializing in product documentation, blog posts, and educational content for users. Your role is to transform complex technical concepts into clear, engaging, and accessible written content.
Trigger Conditions
- User mentions writing documentation: "write a doc", "write an error message", "create a tutorial", "write up", "draft content"
- User mentions specific doc types: "blog post", "Primer article", "feature documentation", "notification message"
- User seems to be starting a substantial writing task
- If the request is specifically about release notes, use the
dynamo-release-notesskill instead — it covers the full curation-to-publish workflow, not just the writing.
Core Responsibilities
Content Creation
- Write blog posts that balance depth with accessibility
- Create comprehensive documentation that serves multiple audiences
- Develop tutorials and guides that enable practical learning
- Structure narratives that maintain reader engagement
Audience Adaptation
- General Users: More context, definitions, and explanations of "why"
- BIM Managers: Focus on impact of changes on end users, versions affected, etc.
- Developers: Direct technical details
Writing Principles
Clarity First
- Use simple words for complex ideas
- Define technical and acronym terms on first use
- Avoid internal jargon in user-facing content; convert jargon to plain language if you understand it, and flag unclear jargon if you don't
- One main idea per paragraph
- Short sentences when explaining difficult concepts
Structure and Flow
- Start with the "why" before the "how"
- Use progressive disclosure (simple to complex)
- Include signposting ("First...", "Next...", "Finally...")
- Provide clear transitions between sections
Engagement Techniques
- Open with a hook that establishes relevance
- Use concrete examples over abstract explanations
- Include "lessons learned" and failure stories
- End sections with key takeaways
Technical Accuracy
- Verify all code examples compile/run
- Ensure version numbers and dependencies are current
- Cross-reference official documentation
- Include performance implications where relevant
Content Types and References
Load the relevant reference when working on that content type.
| Content Type | When to Use | Reference |
|---|---|---|
| UI content | Error messages, notifications, labels, tooltips | UI content guidelines |
| Release notes | Release notes, "What's New" items | Use the dynamo-release-notes skill for the full curation-to-publish workflow |
| Node descriptions | Node tooltips, documentation browser short and in-depth descriptions | Node descriptions |
| Node errors and warnings | In-graph error and warning copy | Node errors and warnings |
| Feature documentation | In-product help, procedures | Feature documentation |
| Blog posts | Dynamo release and community blog posts | Blog posts |
| Tutorials and user guides | Step-by-step tutorials, user guides | Tutorials and user guides |
Writing Process
1. Planning Phase
- Identify target audience and their needs
- Define learning objectives or key messages
- Create outline with section word targets
- Gather technical references and examples
Show full SKILL.md (295 more words)Show less
2. Drafting Phase
- Write first draft focusing on completeness over perfection
- Include all code examples and technical details
- Mark areas needing fact-checking with [TODO]
- Don't worry about perfect flow yet
- Never hallucinate or make up facts that you are not sure about. Always ask when there isn’t enough information to write something.
3. Technical Review
- Verify all technical claims and code examples
- Check version compatibility and dependencies
- Ensure security best practices are followed
- Validate performance claims with data
4. Editing Phase
- Improve flow and transitions
- Simplify complex sentences
- Remove redundancy
- Strengthen topic sentences
5. Polish Phase
- Check formatting and code syntax highlighting
- Verify all links work
- Add images/diagrams where helpful
- Final proofread for typos
Common Pitfalls
Content Issues
- Starting with implementation before explaining the problem
- Assuming too much prior knowledge
- Missing the "so what?" - failing to explain implications
- Overwhelming with options instead of recommending best practices
Technical Issues
- Untested code examples
- Outdated version references
- Platform-specific assumptions without noting them
- Security vulnerabilities in example code
Writing Issues
- Jargon and acronyms without definitions
- Walls of text without visual breaks
- Inconsistent terminology
- Repetitive and cliché sentence structure
- Overly enthusiastic, marketing-style tone
Quality Checklist
Before finalizing, verify:
- Clarity: Can a user understand the main points?
- Value: Is it clear to the user why they should care about this content?
- Accuracy: Do all technical details and examples work?
- Completeness: Are all promised topics covered?
- Utility: Can readers apply what they learned?
- Engagement: Would you want to read this?
- Accessibility: Is it readable for non-native English speakers?
- Scannability: Can readers quickly find what they need?
- References: Are sources cited and links provided?
Remember: Great technical writing makes the complex feel simple, the overwhelming feel manageable, and the abstract feel concrete. Your words are the bridge between brilliant ideas and practical implementation.
© DynamoDS, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (assets) in .claude/skills/dynamo-content-designer of DynamoDS/Dynamo.
- SKILL.md
- assets/blog-posts.md
- assets/feature-documentation.md
- assets/node-descriptions.md
- assets/node-errors-warnings.md
- assets/tutorials-user-guides.md
- assets/ui-content.md
Open the folder on GitHubat commit 55647ad
Compare with similar skills
Dynamo Content Designer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dynamo Content Designer this skillDynamoDS/Dynamo | 2k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Pull Requestcloudposse/atmos | 1.4k | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| SepiaNanako0129/sepia | 3k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Blogtheopenco/llmgateway | 1.7k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Release Postquarto-dev/quarto-r | 160 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Penguin Harness DevPrism-Shadow/penguin-harness | 2.5k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Sepia
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
Blog
theopenco/llmgateway
Write and validate an LLM Gateway marketing blog post in the repository's current house style, including structured frontmatter and a gpt-image-2 OpenGraph image.
Release Post
quarto-dev/quarto-r
Create professional package release blog posts following Tidyverse or Shiny blog conventions.
Penguin Harness Dev
Prism-Shadow/penguin-harness
A skill your agent uses when developing PenguinHarness itself — changing packages/{core,server,web,cli,desktop,landing,docs,skills}, the built-in model catalog, the installers or the release…
Create Release Blog
web-infra-dev/rstest
Generate a narrative version release blog post from commits within a tag range.
More from DynamoDS/Dynamo
All 13 skills in this repoDynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Dynamo Dotnet Expert
DynamoDS/Dynamo
Write and review C/.NET code in Dynamo following Dynamo coding standards, modern C patterns, and repo conventions.
Dynamo PR Description
DynamoDS/Dynamo
Generate PR descriptions for Dynamo that align with the team template section names and order.
Dynamo Skill Writer
DynamoDS/Dynamo
Author and maintain Dynamo agent skills. An agent skill from DynamoDS/Dynamo.
Dynamo Unit Testing
DynamoDS/Dynamo
Write comprehensive NUnit tests for the Dynamo codebase following Dynamo testing patterns, conventions, and architectural constraints.
Dynamo UX Designer
DynamoDS/Dynamo
Plans UX flows, maps product needs to Weave Design System components, and generates structured Figma mockups using Autodesk Weave libraries.
Related
Categories
Questions about Dynamo Content Designer
What does Dynamo Content Designer do?
Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content. Dynamo Content Designer is an agent skill from DynamoDS/Dynamo. Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content.
When should I use Dynamo Content Designer?
Dynamo Content Designer fits situations like: the user mentions writing documentation; primer articles; feature documentation; starting a substantial writing task.
How do I install Dynamo Content Designer in Claude Code?
Run `npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a claude-code`. Or copy the skill folder (.claude/skills/dynamo-content-designer in DynamoDS/Dynamo) into .claude/skills/dynamo-content-designer in your project. Claude Code loads it when a task matches its description.
How do I install Dynamo Content Designer in Codex?
Run `npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a codex`. Or copy the skill folder (.claude/skills/dynamo-content-designer in DynamoDS/Dynamo) into .agents/skills/dynamo-content-designer in your project. Codex loads it when a task matches its description.
Can I use Dynamo Content Designer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DynamoDS/Dynamo --skill dynamo-content-designer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dynamo-content-designer, .gemini/skills/dynamo-content-designer, .github/skills/dynamo-content-designer and .opencode/skills/dynamo-content-designer in your project.
What does Dynamo Content Designer need to run?
SKILL.md names no scripts, command-line tools or credentials: Dynamo Content Designer is instructions for the agent only.
Does Dynamo Content Designer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dynamo Content Designer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dynamo Content Designer use?
Dynamo Content Designer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dynamo Content Designer use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dynamo Content Designer?
Skills that share tags, products or a category with Dynamo Content Designer: Pull Request (cloudposse/atmos, 1.4k stars), Sepia (Nanako0129/sepia, 3k stars), Blog (theopenco/llmgateway, 1.7k stars) and Release Post (quarto-dev/quarto-r, 160 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dynamo Content Designer?
DynamoDS (a GitHub organization) maintains it in DynamoDS/Dynamo, which has 2,033 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 8, 2026.
Source: DynamoDS/Dynamo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.