We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈5

  Distinctive · estimate

  This author's own choices. Worth a look.

• 1

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   After conversion, work with the markdown content normally.

   line 24
2. Distinctive:

   If the user provides a .docx file, convert to markdown first

   line 42
3. Distinctive:

   If the user wants .docx output, convert back using pandoc

   line 44
4. Very specific:

   If pandoc is not installed, inform the user: brew install pandoc (macOS) or sudo yum install pandoc (AL2)

   line 45
5. Distinctive:

   Never modify the original .docx file without user confirmation

   line 51
6. Distinctive:

   Always verify pandoc is available before attempting conversion

   line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.