dissect
Skill18 starsChanged 4 months agoMITView on GitHub
Deconstruct any piece of content that's performing (a viral LinkedIn post, a Reel caption, a YouTube hook, a Reddit thread) into its underlying mechanism — hook type, structure, format, and engagement driver — and hand back a ready-to-use recreation brief. Use when the user pastes a post/caption/hook and says "why is this working", "break this down", "dissect this", "reverse-engineer this post", or just drops content with no instruction. Push to run it whenever someone wants to understand what makes a piece of content work so they can recreate the mechanism for their own audience.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- afaraha8403/balakittheir own version, first seen Nov 6, 2026
- duncan-buildroom/freeskillsword for word, first seen Oct 13, 2026
- mbwsims/claude-universetheir own version, first seen Apr 14, 2026
Other versions3 projects use a version of this.
Word for word · 1
- duncan-buildroom/freeskills★ 65100% same
Edited · 0
None found.
Wrote their own version · 2
- mbwsims/claude-universe★ 71same name
- afaraha8403/balakit★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository52 other files it gives its agents.
- ad-studioSkill
- brainstormingSkill
- build-siteSkill
- carousel-creatorSkill
- cold-outreachSkill
- content-engineSkill
- content-promptSkill
- daily-digestSkill
- daily-post-ideasSkill
- defuddleSkill
- digital-guide-builderSkill
- dm-writerSkill
- edu-siteSkill
- faceless-videoSkill
- first-customer-closerSkill
- frontend-designSkill
- higgsfield-generateSkill
- hooksSkill
- ig-channel-remixSkill
- infographicSkill
- launch-planSkill
- lead-magnetSkill
- linkedin-post-batchSkill
- linkedin-postSkill
- meeting-notesSkill
- money-model-auditSkill
- objection-handlerSkill
- offer-builderSkill
- one-lead-magnetSkill
- outlinesSkill
- personalizeSkill
- positioning-filterSkill
- pricing-calculatorSkill
- productize-serviceSkill
- proposal-generatorSkill
- saas-ad-studioSkill
- sanitize-projectSkill
- shortifySkill
- substackSkill
- ui-ux-pro-maxSkill
- viral-format-minerSkill
- viral-remixSkill
- warm-outreachSkill
- web-design-guidelinesSkill
- yapSkill
- youtube-clipping-agentSkill
- yt-descriptionSkill
- yt-introSkill
- yt-searchSkill
- yt-thumbnailSkill
- yt-titlesSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
If they just paste content with no other instruction, run the dissect automatically.
- Distinctive: line 25
If the content is a URL and not the text itself, ask them to paste the text directly.
- Distinctive: line 31
Read the content carefully before producing output.
- Distinctive: line 119
After the output, add one line:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dissect — Extract What's Working from Any Content
You've found something that's performing. Now you need to know why — so you can recreate the mechanism for your audience without copying the content.
This skill strips a piece of content down to its raw parts: the hook mechanism, the structure, the format, and the engagement driver. The output is a ready-to-use recreation brief.
Input
The user will paste one of:
- A LinkedIn post (text)
- A TikTok or Reel description / caption / transcript snippet
- A YouTube title + description or hook line
- A Reddit thread title + top comment
- Any other content that's getting traction in their niche
If they just paste content with no other instruction, run the dissect automatically. No need to ask what they want.
If the content is a URL and not the text itself, ask them to paste the text directly.
The Dissect Process
Read the content carefully before producing output. Your analysis should be specific to this piece of content, not generic. Never produce templated observations like "the hook creates curiosity" — say what kind of curiosity and how.
Output Format
Produce the following six sections in order. Use these exact headers.
HOOK MECHANISM
Type: [Pick the primary type:]
- Bold claim
- Specific number or result
- Challenged assumption ("Most people think X. Wrong.")
- Open loop (raises a question without answering it)
- Story start (drops into a scene)
- Contrast setup ("I did X. Then Y happened.")
- Direct address ("If you're [specific person], read this.")
What's working: [2–3 sentences. Be specific. What does this hook do to the reader's brain? What gap does it create? Why does someone reading this feel compelled to keep going? Reference the actual words.]
STRUCTURE PATTERN
Flow: [Map the content's movement in 4–6 steps. Use a simple arrow format:]
Example: Hook → Problem setup → Counterintuitive insight → Proof → Framework → CTA
[Then break down each section with a one-line description of what it does. Be specific to this content.]
Tension management: [How does the content hold attention from section to section? What keeps the reader moving forward?]
FORMAT
Type: [Text post / numbered list / story arc / educational breakdown / before-after / contrarian take / case study / framework reveal]
Length: [Short = under 150 words / Medium = 150–400 words / Long = 400+]
Platform fit: [What platform is this optimized for, and what signals tell you that? Line length, pacing, CTA style, formatting conventions.]
Visual/structural elements: [Bullets, line breaks, bold, emojis, numbered steps — what formatting choices are doing work here?]
ENGAGEMENT DRIVER
Primary driver: [Pick the dominant one:]
- Debate (people will disagree and comment)
- Aspiration (makes them want what's described)
- Recognition (makes them say "that's me")
- Fear or urgency (makes them worried about missing something)
- Curiosity (creates a knowledge gap they need closed)
- Social proof (makes them want to be associated with the result)
Why it works for this niche: [1–2 sentences on why this specific driver lands with this specific audience. What does it tap into emotionally or professionally?]
WHAT TO STEAL
[3 bullet points. Each one names a specific, transferable element from this content that has nothing to do with the original topic — the mechanism, not the subject matter.]
Examples of the right kind of observation:
- "The hook leads with a specific number before context — the specificity creates credibility before the claim is even explained."
- "Section 3 uses contrast ('what I stopped doing') before showing the positive — the negative framing makes the payoff hit harder."
- "The CTA is benefit-first ('get the template') not action-first ('click here') — lowers resistance."
RECREATION BRIEF
Mechanism to recreate: [One sentence — the underlying hook/structure mechanism, stripped of its original topic]
Your angle: [One sentence — how a business owner in a different niche could use this same mechanism with their own proof/topic]
Recommended platform: [Where this format will land best for them]
First line to write: [Give them the opening line of their recreated version — a placeholder using [YOUR RESULT] or [YOUR NICHE] style brackets where their specific info goes. Make it immediately usable.]
Closing Note
After the output, add one line:
"Ready to recreate this? Tell me your niche and I'll draft your version using this brief."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

