idea-to-content-skill

name	idea-to-content-skill
description	Turns raw or messy ideas into structured, publish-ready content through planning, writing, formatting, and refinement. Use when user asks to rewrite, clean up, improve clarity, or turn ideas into posts, captions, explanations, or structured content.

Purpose

This skill transforms unstructured ideas into clear, publish-ready content using a structured multi-stage workflow.

When to use this skill

Use this skill when the user:

• Shares messy or incomplete ideas
• Wants content written for posting or publishing
• Requests clearer explanations or rewrites
• Provides brainstorming notes or fragmented thoughts

When NOT to use this skill

Do not use this skill when:

• The user asks for factual explanations unrelated to rewriting or content creation
• The request is about coding, math, or technical problem solving
• The user is not asking to transform or structure ideas

Workflow: Idea to Publish-Ready Content

Step 1: Extract Core Idea

• Identify the main message from the user's input
• Ignore noise or repetition
• If unclear, ask for clarification before proceeding

Step 2: Determine Content Type

• Decide the most suitable format:
  • Caption
  • Short post
  • Explanation
  • Narrative

Step 3: Generate Initial Draft

• Expand the idea into structured writing
• Ensure logical flow between sentences
• Keep tone natural and human

Step 4: Format for Readability

• Apply structure from assets/content-templates.md
• Improve clarity and pacing
• Ensure content is easy to read and understand

Iterative Refinement Process

Quality Check

Evaluate the draft for:

• Clarity
• Logical flow
• Redundancy
• Readability

Refinement Loop

• Fix identified issues
• Improve structure and tone
• Simplify where necessary
• Re-check quality
• Repeat until content meets publish-ready standards

Finalization

• Remove any remaining repetition
• Tighten language
• Ensure the output is polished and ready to publish

Validation Rules (internal)

• After Step 1: Core idea must be clear before continuing
• After Step 3: Content must have logical flow
• Before final output: Content must be readable, concise, and coherent

Output rules

• Always return final polished content
• Do not show internal steps unless explicitly requested
• Keep tone natural, simple, and human
• Avoid unnecessary complexity
• Do not introduce unrelated ideas

Quality checklist (internal)

• Is the core idea preserved?
• Does it read smoothly aloud?
• Is it clear and easy to understand?
• Is it concise and focused?
• Is it ready to publish without edits?

Error Handling

Unclear input

• Ask a clarifying question before continuing

Overly short input

• Expand carefully without inventing unrelated meaning

Conflicting ideas

• Prioritize the strongest or most consistent idea and simplify

Output feels unfocused

• Refocus on the main idea and simplify structure

Resource Usage

• Refer to references/writing-guidelines.md for tone, clarity, and editing rules
• Use assets/content-templates.md to guide structure and formatting