How do I install the Xmldocer skill?

Run npx skillmds@latest add tmssoftware/xmldocer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Xmldocer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Xmldocer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Xmldocer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Xmldocer?

tmssoftware (@tmssoftware) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Xmldocer by tmssoftware — Agent Skill

Name: Xmldocer
Author: tmssoftware

Xmldocer

Create and update documentation topics in Smart Setup documentation. Use when the user asks to write, update, add, or modify documentation topics in Smart Setup documentation. This includes writing new documentation topics, updating existing topics with new features, adding sections to existing pages, creating examples, and writing release notes entries. Triggers on requests like "document this feature", "add documentation", "update the docs", "write a new topic about Y", "add to release notes".

tmssoftware 28597aa 3 files · 7.3 KB Updated Sep 17, 2026

File contents

Smart Setup Documentation Writer

Write and update Markdown documentation using proper Markdown syntax.

Before Writing

Read references/doc-guidelines.md for formatting rules and custom syntax.
Read references/doc-structure.md for file locations, UID conventions, and TOC management.

Workflow

Updating an Existing Topic

Read the existing topic file.
Find the right section to add or modify content.
Follow the existing style and structure of the file.

Creating a New Topic

Read 1-2 existing topic files from the same product to match style.
If relevant read the product source code related to the feature to ensure accuracy.
Create the file in the proper` folder with proper frontmatter:

---
uid: SmartSetup.TopicName
---

# Topic Title

Content...

Add the topic to <folder>/toc.yaml at the appropriate position:

- name: <Topic Title>
  href: <file-name>.md

Adding Release Notes

Add items to the what's new file under the current version heading, only if user asked to update the release notes.

- **New:** Description of the feature, the main phrase describing the change should be in bold.
- **Improved:** Description of the improvement.
- **Fixed:** Description of the fix.

Key Rules

Always use [text](xref:UID) for cross-topic links, never raw file paths.
Use {{#Note}}...{{/Note}} and {{#Warning}}...{{/Warning}} for alerts.
Use {{#image}}filename.png{{/image}} for images.
Do not invent commands or parametes. Reference the real tool.
Practical examples over theory. Show working workflows.
In reference, focus on the technica details, parameters, and usage of the command/tool. In conceptual, focus on the why, when, and how to use the feature.
Do not duplicate information in conceptual and reference topics. From conceptual, link to the reference for technical details. From reference, link to the conceptual for explanations and examples.
Professional tone, no emojis, no filler.

---name: xmldocerdescription: Create and update documentation topics in Smart Setup documentation. Use when the user asks to write, update, add, or modify documentation topics in Smart Setup documentation. This includes writing new documentation topics, updating existing topics with new features, adding sections to existing pages, creating examples, and writing release notes entries. Triggers on requests like "document this feature", "add documentation", "update the docs", "write a new topic about Y", "add to release notes".---# Smart Setup Documentation WriterWrite and update Markdown documentation using proper Markdown syntax.## Before Writing1. Read [references/doc-guidelines.md](references/doc-guidelines.md) for formatting rules and custom syntax.2. Read [references/doc-structure.md](references/doc-structure.md) for file locations, UID conventions, and TOC management.## Workflow### Updating an Existing Topic1. Read the existing topic file.2. Find the right section to add or modify content.3. Follow the existing style and structure of the file.### Creating a New Topic1. Read 1-2 existing topic files from the same product to match style.2. If relevant read the product source code related to the feature to ensure accuracy.3. Create the file in the proper` folder with proper frontmatter:```markdown---uid: SmartSetup.TopicName---# Topic TitleContent...```4. Add the topic to `<folder>/toc.yaml` at the appropriate position:```markdown- name: <Topic Title> href: <file-name>.md```### Adding Release NotesAdd items to the what's new file under the current version heading, only if user asked to update the release notes.```markdown- **New:** Description of the feature, the main phrase describing the change should be in bold.- **Improved:** Description of the improvement.- **Fixed:** Description of the fix.```## Key Rules- Always use `[text](xref:UID)` for cross-topic links, never raw file paths.- Use `{{#Note}}...{{/Note}}` and `{{#Warning}}...{{/Warning}}` for alerts.- Use `{{#image}}filename.png{{/image}}` for images.- Do not invent commands or parametes. Reference the real tool.- Practical examples over theory. Show working workflows.- In reference, focus on the technica details, parameters, and usage of the command/tool. In conceptual, focus on the why, when, and how to use the feature.- Do not duplicate information in conceptual and reference topics. From conceptual, link to the reference for technical details. From reference, link to the conceptual for explanations and examples.- Professional tone, no emojis, no filler.

Frequently asked questions