writing-prose
Always use this skill when writing or editing prose. Do **NOT** use for agent context files, readmes, tool descriptions, or other functional writing tasks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Always use this skill when writing or editing prose. Do **NOT** use for agent context files, readmes, tool descriptions, or other functional writing tasks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Manage Obsidian vault frontmatter with rematter — validate schemas, sync to external destinations (Astro, etc.) with media options, rename fields, manage filenames. Load whenever performing bulk operations in Obsidian vaults (or other collections of markdown with frontmatter).
Use when asked to automate an action for OpenCode, for example run a formatter after edits, or running a script right before git commits, those are hooks and you should use this skill to implement them.
Guide the learner through a structured goal-setting exercise grounded in research on Mental Contrasting with Implementation Intentions (MCII). The exercise helps developers set concrete learning goals, visualize meaningful outcomes, anticipate realistic obstacles, and build if-then plans to overcome them.
Facilitates deliberate skill development during AI-assisted coding. Offers interactive learning exercises after architectural work (new files, schema changes, refactors). Use when completing features, making design decisions, or when user asks to understand code better. Supports the user's stated goal of understanding design choices as learning opportunities.
Generates a repo-specific orientation.md resource for the learning-opportunities skill. Only invoke via slash command (/orient:orient). Do not trigger automatically.
Use when asked to add or modify hooks for Claude Code specifically. Or, if the user is asking to automate an action, for example run a formatter after edits, or running a script right before git commits, those are hooks and you should use this skill to implement them.
| name | writing-prose |
| description | Always use this skill when writing or editing prose. Do **NOT** use for agent context files, readmes, tool descriptions, or other functional writing tasks. |
Apply these rules to any writing task: generating prose, or editing existing prose you're given to review and improve.
These rules eliminate common patterns in low quality writing (both AI-generated and human) that frustrate readers with empty predictability, causing them to disengage.
Full guidance is modularized in these guides:
After writing prose, you MUST start a review loop with the writing-prose-editor subagent. It will score the version of the work that you have generated or edited across 8 dimensions, assigning 1-5 points for each (40 points max). If the score is below 32, you must revise the prose based on the specific feedback provided by the editor and repeat the review loop until you achieve a passing score (≥ 32/40). DO NOT self-score or self-approve to bypass the editor's authority. They are your manager, you must go through their approval process.
writing-prose-editor subagentIterate until passing. The editor is the authoritative scorer.