nakane1chome/flesh-out
skills/flesh-out/SKILL.md
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.
testing
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add nakane1chome/claude-skills flesh-outInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 11:04 AM154.8s2 files scanned
SKILL.md
- name:
- flesh-out
- description:
- 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.
- argument-hint:
- <file|folder>...
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.mdfor the full agent/developer ownership matrix.
-
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
-
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.
-
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
-
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)
-
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 State | Use | |----------------|-----| | Raw notes, bullet points, stream of consciousness | flesh-out | | Typos, incomplete sentences, but has structure | review-steps | | Structured but missing sections | flesh-out (or discuss scope first) | | Complete draft needing polish | review-steps | | Complete draft needing critical evaluation | strong-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.
Related Skills
nakane1chome/myBadSkill
tools
VerifiedTrustedCommunity
Helps with things
SKILL.mdUpdated Apr 23, 2026
nakane1chome/strong-edit
data-ai
VerifiedTrustedCommunity
Critical editorial analysis of articles. Examines structure, argument strength, relevance, and readability. Use for substantive editing - challenging what's said and how, not just polish.
SKILL.mdUpdated Apr 23, 2026
nakane1chome/sdlc-cross-review
testing
VerifiedTrustedCommunity
Review a document against its SDLC lifecycle context — assess completeness and check consistency with parent documents in the document hierarchy.
SKILL.mdUpdated Apr 23, 2026
nakane1chome/review-steps
testing
VerifiedTrustedCommunity
Structured review for polishing documents. Fixes language, improves clarity, checks structural consistency, and compares against best practice. Use when a draft has structure but needs a thorough review pass.
SKILL.mdUpdated Apr 23, 2026