agentsclimarketplace
Sign in

Flesh out

Skill nakane1chome/claude-skills/skills/flesh-out

Transform raw/crude document drafts into structured content. Use when a document is a skeleton of ideas, notes, or stream-of-consciousness that needs generative expansion rather than review polish.From its SKILL.md

Install
npx -y skills add nakane1chome/claude-skills --skill flesh-out

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, 617 tokens by cl100k_base, as published. Nobody here has run it

This skill is for generative work on crude/raw content at $ARGUMENTS - not polishing drafts.

Stop after each stage and have changes reviewed with user.

Note: The developer's raw content captures intent. The agent expands and structures but must preserve the developer's meaning. When uncertain about intent, ask - don't assume.

See responsibilities.md for the full agent/developer ownership matrix.

  1. Extract core ideas (developer leads)

    • Read the raw content and identify the key concepts
    • List what the developer appears to be saying (don't fix typos yet)
    • What is the document's function? (its type and role — e.g., design doc, tutorial, proposal)
    • What is the document's goal? (the concrete outcome it exists to produce — e.g., a working implementation, an adopted practice)
    • Identify gaps: "You mention X but don't explain Y - should I research this?"
    • Confirm understanding with developer before proceeding

  2. Research and expand (agent leads with approval)

    • Web search for external concepts if applicable
    • Find industry terminology for rough ideas
    • Identify related work the developer may want to reference
    • Propose expansions - developer approves what to include
    • Verify every reference before presenting: fetch URLs, confirm they resolve, confirm the source supports the claim. Do not present unverified links to the developer.

  3. Structure the content (agent leads with approval)

    • Determine appropriate document structure (based on template if available)
    • Organize ideas into logical sections
    • Does the structure serve the document's function and support its goal?
    • Create hierarchy (headers, sub-sections)
    • Add diagrams or tables where relationships exist

  4. Polish language (agent leads with approval)

    • Fix spelling, grammar, terminology
    • Expand acronyms on first use
    • Ensure consistent usage throughout
    • Add links to external references (verify each URL resolves before adding)

  5. Tidy up (agent leads with approval)

    • Check with the user where to update the glossary
    • Add terms that needed clarification
    • Update references with new links

When to Use This vs Other Skills

Document StateUse
Raw notes, bullet points, stream of consciousnessflesh-out
Typos, incomplete sentences, but has structurereview-steps
Structured but missing sectionsflesh-out (or discuss scope first)
Complete draft needing polishreview-steps
Complete draft needing critical evaluationstrong-edit

Key Difference from Review

Review improves what exists within its structure. Flesh-out creates structure from raw ideas.

Review a skeleton -> correct but incomplete document. Flesh-out a skeleton -> complete document.

What ships with it: 1 file

2.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,782. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.