Isomoes Writing

Use this skill to turn rough technical notes into clean, format-aware writing without changing the underlying facts.

Overview

This skill separates routing from style guidance:

• Read command.md first to identify the writing mode and shared rules.
• Then read only the relevant format guide such as report.md or blog.md.
• Preserve technical meaning, concrete facts, and stated metrics.

When to Use

Use this skill when the user asks for any of the following:

• a weekly report, progress report, lab report, or research update
• a technical blog post, blog intro, blog rewrite, or article polish
• conversion of bullet points into paragraphs
• more objective, clearer, or more readable technical writing
• adaptation of the same material into different writing formats

Do not use this skill for code generation, literature review, or citation-heavy journal rewriting.

Working Pattern

1. Identify the target format and audience.
2. Read command.md for the routing rules and shared constraints.
3. Read only the matching format guide.
4. Rewrite the content in that house style.
5. Keep claims proportional to the provided evidence.

Format Files

• command.md - format selection and shared writing rules
• report.md - weekly report and technical progress report rules
• blog.md - technical blog and article rules

Output Bar

Before finishing, make sure the draft is:

• faithful to the source notes
• cleaner and easier to read than the input
• specific about methods, tools, metrics, and scope
• matched to the requested format rather than generically polished

Common Mistakes

• Writing a weekly report like a marketing update
• Writing a blog post like a dry internal report
• Dropping concrete metrics while improving flow
• Turning bullets into paragraphs without adding transitions