Skill 詳細
isomoes-writing
Drafts and polishes weekly, progress, lab, and technical reports.
使用前に確認
自動レビューは関連性のみを確認し、安全性や推奨を保証しません。使用前に出典の説明を読んでください。
SKILL.md
これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。
--- name: isomoes-writing description: Use when drafting, rewriting, or polishing weekly reports, technical blog posts, or similar long-form technical writing, especially when the user wants objective technical prose, stronger narrative flow, or format-specific adaptation between report and blog styles. --- # 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 transitionsGitHub で全文を読む (外部ページ)