How do I install the Write Wiki skill?

Run npx skillmds@latest add majiayu000/write-wiki 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 Write Wiki safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Write Wiki?

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 Write Wiki free to use?

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

Who published Write Wiki?

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

Write Wiki by majiayu000 — Agent Skill

Name: Write Wiki
Rating: 4.2 (5 reviews)
Author: majiayu000

Write Wiki

Create user documentation for the HMIS wiki following writing guidelines. Use when creating documentation for end users (pharmacy staff, nurses, doctors, administrators). Creates documentation directly in the sibling ../hmis.wiki directory.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Write Wiki Documentation

Create end-user documentation directly in the sibling ../hmis.wiki directory following the project's wiki writing guidelines.

IMPORTANT: Wiki files live ONLY in the sibling ../hmis.wiki directory. Do NOT create wiki markdown files inside the main project repository - this causes git submodule issues.

Arguments

$0 - Module and feature name (e.g., Pharmacy/Stock-Transfer)

Target Audience

Pharmacy staff, nurses, doctors, administrators
Non-technical healthcare professionals
Focus on how to use features, not implementation details

Required Structure

Every wiki page must include these sections:

Overview - What the feature does and why (2-3 sentences)
When to Use - Specific scenarios and business triggers
How to Use - Step-by-step with navigation paths
Understanding Messages - Success, warning, and error messages
Best Practices - Tips for effective use
Troubleshooting - Common problems and solutions
Configuration (Admin) - Settings that affect the feature
FAQ - Common questions

Writing Rules

Active voice: "Click the Submit button" (not "The button should be clicked")
Imperative mood: "Enter the patient ID"
Bold UI elements: Pharmacy > Reports > Stock Ledger
One action per step in numbered procedures
No code, no technical details - no Java classes, SQL, file paths, or method names

What NOT to Include

Code snippets, file paths, line numbers
Java class names, method signatures
Database schema or SQL queries
JSF component IDs or backend beans
Developer debugging information

File Location

Create files at: ../hmis.wiki/$0.md

Ensure the wiki repo exists first:

test -d "../hmis.wiki" || (cd .. && git clone https://github.com/hmislk/hmis.wiki.git && cd hmis)

After creating, suggest using /publish-wiki to commit and push to the GitHub Wiki.

---name: write-wikidescription: Create user documentation for the HMIS wiki following writing guidelines. Use when creating documentation for end users (pharmacy staff, nurses, doctors, administrators). Creates documentation directly in the sibling ../hmis.wiki directory.--- # Write Wiki Documentation Create end-user documentation directly in the sibling `../hmis.wiki` directory following the project's wiki writing guidelines. **IMPORTANT**: Wiki files live ONLY in the sibling `../hmis.wiki` directory. Do NOT create wiki markdown files inside the main project repository - this causes git submodule issues. ## Arguments - `$0` - Module and feature name (e.g., `Pharmacy/Stock-Transfer`) ## Target Audience - Pharmacy staff, nurses, doctors, administrators - Non-technical healthcare professionals - Focus on **how to use features**, not implementation details ## Required Structure Every wiki page must include these sections: 1. **Overview** - What the feature does and why (2-3 sentences) 2. **When to Use** - Specific scenarios and business triggers 3. **How to Use** - Step-by-step with navigation paths 4. **Understanding Messages** - Success, warning, and error messages 5. **Best Practices** - Tips for effective use 6. **Troubleshooting** - Common problems and solutions 7. **Configuration (Admin)** - Settings that affect the feature 8. **FAQ** - Common questions ## Writing Rules - **Active voice**: "Click the Submit button" (not "The button should be clicked") - **Imperative mood**: "Enter the patient ID" - **Bold UI elements**: **Pharmacy** > **Reports** > **Stock Ledger** - **One action per step** in numbered procedures - **No code, no technical details** - no Java classes, SQL, file paths, or method names ## What NOT to Include - Code snippets, file paths, line numbers - Java class names, method signatures - Database schema or SQL queries - JSF component IDs or backend beans - Developer debugging information ## File Location Create files at: `../hmis.wiki/$0.md` Ensure the wiki repo exists first: ```bash test -d "../hmis.wiki" || (cd .. && git clone https://github.com/hmislk/hmis.wiki.git && cd hmis) ``` After creating, suggest using `/publish-wiki` to commit and push to the GitHub Wiki.

Frequently asked questions