From llm-essentials
Governs all Markdown file creation, editing, reviews, and modification. Always read the file in full before writing or modifying any Markdown content, even for a small change. The skill applies the exact conventions visible throughout this repository: `<div align = "center">` title banners, `<div align = "justify">` body wrappers, Shields.io badges, emoji section headings (README-tier files only), `:---:` centred table columns, 2-space indented lists and checklists, ATX-style headings, and fenced code blocks with explicit language specifiers. Use this skill when the user asks to create, edit, update, or review any `*.md` file - including `README.md`, `SKILL.md`, `AGENT.md`, `CHANGELOG.md`, and documentation pages. Trigger phrases: "create/edit/update the readme", "write documentation", "update the markdown", "add a changelog entry", "create a skill file", "create an agent file".
How this skill is triggered — by the user, by Claude, or both
Slash command
/llm-essentials:markdown-formatThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<div align = "center">
This skill governs every *.md file in the repository: README.md, SKILL.md, AGENT.md, CHANGELOG.md, and any other
documentation page. Read the entire target file before making any change, even a single-line edit. Apply every rule
below before generating output.
*.md Files)These rules apply to every Markdown file regardless of role.
Every Markdown file in this repository uses two HTML div wrappers. Always include both and never merge them.
<div align = "center">
# Title in Title Case
</div>
<div align = "justify">
Body content goes here.
</div>
Rules for div wrappers:
= operator: <div align = "center"> not <div align="center">.<div ...> tag and immediately before the closing </div> tag.center div contains only the primary heading and optional badges - never body text.justify div wraps the entire body from the first section heading to the last paragraph.# prefix) exclusively - never setext underline style.# Title) lives inside the center div only; all section headings (##, ###) live inside
the justify div.## straight to ####).---) may be used to visually separate major top-level sections within the justify div. * (two spaces + asterisk + space). 1. (two spaces + number + period + space) for every item - let the renderer auto-increment. - [ ] (two spaces + hyphen + space + brackets + space).Use this column alignment pattern consistently:
| Column Type | Alignment Specifier | When to Use |
|---|---|---|
| Label / identifier / enum | :---: (centered) | Short categorical values |
| Description / prose | --- (left-aligned) | Explanatory text |
| Numeric (counts, sizes) | ---: (right-aligned) | Numbers for comparison |
| content | not |content|.text for plain terminal output or unknown formats.python, sql, shell, json, markdown, yaml, text.$ inside shell blocks.| Markup | Use Case | Examples |
|---|---|---|
`backtick` | Inline code, file paths, CLI args, config keys | `SKILL.md`, `--token`, `main()` |
*single asterisk* | Technical terms on first use, module/package names | *bundled package*, *open standard* |
**double asterisk** | Important callouts, required keyword args, warnings | **name**, **Parallel** |
~~strikethrough~~ | Deprecated content only |
-) - use a hyphen-minus (-) always.<b>, <i>, <em>, <strong> inline - use Markdown emphasis only.[visible text](url) - never bare URLs, never reference-style links.[SKILL.md](python-code-format/SKILL.md).https:// scheme.README.md files (top-level and directory-level) follow this specific layout on top of the universal rules.
<div align = "center">
# Title in Title Case
[](link-target)
[](link-target)
</div>
<div align = "justify">
Short one-paragraph description of what the directory or project contains.
## 🚀 Section One
...
## 📦 Section Two
...
</div>
All badges use the Shields.io static badge format with these fixed parameters:
https://img.shields.io/badge/<Label>-%20<Text>-<COLOR>?style=plastic&logo=<LOGO>
style=plastic is mandatory - never use flat, flat-square, or for-the-badge.003B57 (dark teal blue) is the default for skill and agent badges in this repo.%20 to encode spaces within label or text segments.center div, each on its own line, with a blank line between the heading and the first
badge block.[](target-link).README-tier files use a single emoji prefix on every ## section heading. Pick an emoji that is semantically related to
the section's content and is not already used by another section in the same file. Common assignments in this repo:
| Emoji | Typical Section Title |
|---|---|
| 🧠 | Introduction, Background |
| 🚀 | Getting Started, Quick Start |
| 🤖 | Project Capabilities, Agents |
| ⚖️ | License |
| ⚠️ | Disclaimer, Warnings |
| 🧭 | Orchestration, Navigation |
| 📦 | Installation, Registration |
| 🧪 | Testing, Verification |
### or deeper sub-headings.SKILL.md, AGENT.md, or CHANGELOG.md section headings.SKILL.md and AGENT.md files follow the universal rules plus these specific requirements.
Every SKILL.md and AGENT.md must open with YAML frontmatter between --- markers:
---
name: skill-or-agent-name
description:
One or more sentences that tell the LLM *when* to invoke this skill or agent. Include specific trigger phrases at the
end. The description can span multiple indented lines - use 2-space indent for continuation lines.
---
Rules for frontmatter:
name must be kebab-case and match the directory name exactly.description must include concrete trigger phrases so the LLM can auto-invoke.name and description unless the Agent-Skills standard explicitly supports
them (e.g. allowed-tools).---.After the frontmatter, follow this section order:
<div align = "center"> containing # Skill/Agent Name (Title Case, matching name in frontmatter).<div align = "justify"> containing at minimum: a short intro paragraph, Getting Started (numbered rules),
main content sections, and a Quick Checklist at the very end. - [ ] items and test the most likely failure modes.SKILL.md or AGENT.md section headings.--- horizontal rule between sections in SKILL/AGENT files - reserve those for README-tier files.CHANGELOG.md follows Keep a Changelog conventions adapted for this repo.
## [vX.Y.Z] - YYYY-MM-DD
### Added
* Description of new feature or file.
### Changed
* Description of modified behaviour.
### Fixed
* Description of bug fix.
### Removed
* Description of removed content.
## [vX.Y.Z] - YYYY-MM-DD - the ## level only, never # or ###. * (two spaces + asterisk).### Added, ### Changed, etc.) that have at least one entry for that release.## [Unreleased].<div align = "center"> banner present with a blank line after the opening tag?<div align = "justify"> wrapper present with a blank line before the closing tag?#) style?README.md section headings have an emoji prefix at ## level only?style=plastic and wrapped in a link? * (2 spaces + asterisk)? - [ ] (2 spaces + hyphen)?:---:) and description columns left-aligned (---)?-)?SKILL.md / AGENT.md have a YAML frontmatter block as the very first content?name key in frontmatter match the directory name in kebab-case?npx claudepluginhub pyutility/polyskills --plugin llm-essentialsProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.