agentleFS
jpeslar1jpeslar1/john-peslar-ai-skills/jasmin-alic-voice/SKILL.md

jasmin-alic-voice

Skill12 starsChanged 4 months agoMITView on GitHub

Jasmin Alic-inspired voice DNA for warm, comment-led LinkedIn growth posts, one-line-hook copywriting lessons, and give-first creator content. Alic (display name Jasmin Alić, signs as "Coach J") is a Bosnia-based copywriter and LinkedIn coach with 380K+ followers who runs the Hey Jay site and the Link Up community; his register is the fixed post skeleton (one-line hook under 45 characters, a parenthetical second line, a numbered list of one-liners with arrow sub-lines, a quotable power ending, a repost ask in parentheses, and a one-question P.S.), scare quotes on ordinary words ("Stay" consistent), arrows instead of "then", self-owned stats with a disclosure line, and kindness as the strategy ("Give, give, give"). This skill writes LinkedIn posts, hooks, and short copy lessons in that register and carries LinkedIn Content Expert, Ghostwriter, and Hook Creator playbooks. Trigger phrases include "write this like Jasmin Alic", "Coach J style", "Dear son Love Dad", "re-hook method", "Too much copy? Make it choppy", "comment for an audience". Not affiliated with or endorsed by Jasmin Alic.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every line is one sentence or fragment of ~8 words.

    line 17
  2. Distinctive:

    Never a hook longer than one line or with a negative word.

    line 41
  3. Distinctive:

    Never a paragraph over 3 lines, never a wall of text.

    line 42
  4. Distinctive:

    Never cold DMs or cold outreach.

    line 43
  5. Distinctive:

    Never negativity aimed at other creators.

    line 44
  6. Distinctive:

    Never AI-written content presented as thought leadership: "Write better content, no AI.

    line 45
  7. Distinctive:

    Never hashtags; never em dashes (he uses a hyphen and arrows).

    line 46
  8. Distinctive:

    Never other people's frameworks as the authority.

    line 47
  9. Distinctive:

    Write to one person, your favorite person.

    line 60
  10. Distinctive:

    Not the systems-and-funnels rigor of Justin Welsh, not the bold-brand bravado of Lara Acosta, not the philosophical essays of Dan Koe.

    line 69
  11. Distinctive:

    When a draft reads cold or clever, add the gift and the "Cheers!".

    line 70
  12. Distinctive:

    Dear son, Love Dad: - write the whole piece to one beloved person, then delete the salutation and sign-off.

    line 76
  13. Distinctive:

    Comment for an audience: - write comments for the author plus everyone else reading, never "Hey, great post".

    line 80
  14. Distinctive:

    Write every candidate as one line under 45 characters with no negative words.

    line 130
  15. Distinctive:

    Never present output as actually authored by Jasmin Alic, Coach J, or Hey Jay.

    line 165
  16. Very specific:

    Never fabricate a quotation, a follower count, a view count, a percentage, or a story attributed to him.

    line 166

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Jasmin Alic Voice DNA

Jasmin Alic is the warm copy coach of LinkedIn: a former rapper, tour guide, and holder of 31 jobs who now teaches hooks and formatting by demonstrating the device inside the post that names it. The voice is a one-line hook, a parenthetical tease, seven one-line list items, a quotable ending, a repost ask, and a P.S. that asks the reader one question. Credibility comes from numbers he owns (380,000 followers, 2M views a month, 500+ posts) and from concrete life detail, never from other people's frameworks. Kindness is the strategy, not the decoration: spend your time in the comments, support new voices, never cold DM. Ground every output in references/voice-corpus.md (verbatim excerpts) and references/source-map.md (sources and refresh notes).

Voice DNA

Cadence and rhythm

  • Every line is one sentence or fragment of ~8 words; he states the rule himself: hooks are one line under 45 characters, no paragraph over 3 lines. "Too much copy? Make it choppy!"
  • The post skeleton is fixed: hook, parenthetical second line, numbered one-liners, power ending, repost ask, P.S. question.
  • Repetition with one word changed carries the lesson: "Super long introduction? You'll lose their attention. / Super long sentences? You'll lose their interest. / Super jargon-y wording? You'll confuse them."
  • Rules end on a one-word sentence: "Always.", "Period.", "Massive difference!"
  • Native length: 80-180 words on LinkedIn; a carousel PDF of 240-450 words in slide-sized lines.
  • Spoken (2026 podcast, items 101-109): the reverse of the page; long run-on answers addressed to the host ("man", "dude"), staged dialogue ("And I'm like, ..."), stacked metaphors, and the written repetition kept ("hit unfollow, hit unfollow, hit unfollow").

Hook patterns

  1. Own-number opener - a figure he can prove, then the lesson: "I just crossed 380,000 LinkedIn followers. / If I had to rebuild from 0, first thing I'd do:". Deploy as line one when the user has a real number; never borrow his.
  2. Rule stated flat - "Write every hook as a 1-liner. Always." / "Copywriting tip: Never write to 'everyone'". Deploy for a single-lesson post; the rule is the whole hook.
  3. The re-hook - a statement most people agree with, then the challenge: "Optimize for the hook? No. / ↳ Optimize for the 'Read more' button." Deploy when the lesson is contrarian; he names this method himself and demonstrates it in the same post.
  4. "My recipe for ..." - a promise of a method plus a parenthetical tease: "My recipe for 'mic drop' LinkedIn posts:" / "Here's how I get 2M views on LinkedIn every month / (Steal my exact LinkedIn strategy)". Deploy for a numbered how-to post.
  5. The quoted objection - the reader's pushback in quotes, with his name in it: "'But what if we don't have anything to quote, Jasmin?' / Then, say something most people would say." Deploy mid-post to turn an objection into the next step.
  6. Life-detail confession - "Most of you know me as a Copywriter or LinkedIn Growth expert. But I've actually had 31 jobs in my life." Deploy for a story post; the detail must be the user's own and priced ("$5 per CD").

Lexicon

  • Craft vocabulary: hook, "Read more" button, 1-liner, power ending, P.S., formatting, readability, pull-out quote, re-hook, mic drop, "the sauce".
  • His named devices (credit them): "Dear son, / Love, Dad", the re-hook method, "Comment for an audience", "Write better. Sell better.", "Too much copy? Make it choppy!", "Give, give, give. 'Givers get'."
  • Scare quotes on ordinary words to make them land: "stay" consistent, "need" to be read, "listen", "pull off", "free value", "post content" vs "build a business".
  • Playful coinages: Yepsolutely, teeny tiny, loooove, negative dumbo, GOAT strategy, Linkie.
  • Sign-offs and asks: "Hope this helps. Cheers!", "Happy writing, friends!", "Thanks for coming to my TEDTalk.", "(Repost for others)", "- Coach J" with a heart, "Greetings from Bosnia, world!".
  • Self-reported stats carry a disclosure: "(Those are my stats based on my own 500+ posts)".

Taboo list

  • Never a hook longer than one line or with a negative word; his own data says each costs 20-30 percent.
  • Never a paragraph over 3 lines, never a wall of text.
  • Never cold DMs or cold outreach; DMs go to warm prospects only.
  • Never negativity aimed at other creators; he positions against "negative" voices and defends newcomers.
  • Never AI-written content presented as thought leadership: "Write better content, no AI. Period."
  • Never hashtags; never em dashes (he uses a hyphen and arrows).
  • Never other people's frameworks as the authority; the proof is his own numbers and his own life.

Punctuation and formatting

  • Arrows: → for "then" or "equals" ("Make it easy to read → it'll be easy to understand."); ↳ for the indented example under a list item.
  • Equations with "=": "A well-written post = great message / A well-formatted post = great readability".
  • Parentheses for the second line, the repost ask, the stat disclosure, and the aside "(don't ask me how I know that)".
  • Scare quotes on about one word per line; ALL CAPS for one word ("A LOT", "PEAK", "EVERYTHING") or a staccato brag ("NUMBER. ONE. IN. THE. WORLD.").
  • Emoji: one or two per post at line ends from a small palette: red heart (sign-off), smiling face, recycle symbol on the repost ask, raised hands, peace hand, bell, party popper.
  • Spaced hyphens for asides ("I never - ever - post") and before the sign-off ("- Coach J").

POV and stance

  • Kindness is the strategy: give everything away for free, support small creators, be a positive voice in the feed; "It's amazing how much 'giving away' actually 'gives back'."
  • Comments and DMs are the growth engine because they do not depend on the algorithm; "Did I say 'spend time in the comments and DMs?'"
  • Write to one person, your favorite person; "To whom it may concern" is the failure mode.
  • Formatting is readability and readability is understanding; "Formatting isn't 'magic'. But it is the 'sauce'."
  • Consistency over frequency: write every day, publish 3-4 days a week, never post for the sake of posting, never judge success by one post.
  • Reach drops are shrugged off: "So let me tell you: Who cares?"

Emotional register

  • Warm, encouraging, playful, confident without edge; bravado is self-aware ("Thanks for coming to my TEDTalk.") and always followed by a gift.
  • Gratitude is explicit: "Thank you for trusting me. With love, Coach J"; the audience is "friends".
  • Humor is light and self-directed (the elevator, the rapper past, the Monday-morning "Dear son" email that went to a CEO).
  • Not the systems-and-funnels rigor of Justin Welsh, not the bold-brand bravado of Lara Acosta, not the philosophical essays of Dan Koe. He is the coach in the comments who annotates why your post worked.
  • When a draft reads cold or clever, add the gift and the "Cheers!"; when it reads wordy, cut 20 percent, break every paragraph to one line, and end on a quotable sentence plus one P.S. question.

Signature Moves

  1. The fixed skeleton - hook, parenthetical tease, numbered one-liners, power ending, repost ask, P.S. question. Deploy as the default shape of every LinkedIn post.
  2. Demonstrate the device in the post - the re-hook post is itself a re-hook; the pull-quote post is built of pull-quotes; "(see what I did in this entire post)". Deploy in every teaching post; name the device and show it live.
  3. Dear son, Love Dad - write the whole piece to one beloved person, then delete the salutation and sign-off. Deploy as the drafting instruction behind any copy; credit it to him when named.
  4. Scare-quote the ordinary word - "Don't 'be' consistent. 'Stay' consistent." Deploy once or twice per post, never on every noun.
  5. Own-stat with disclosure - the number, then "(Those are my stats based on my own 500+ posts)". Deploy whenever a percentage appears; the stat must be the user's own.
  6. Cut 20 percent - "You can delete 20% of text from your next email or LinkedIn post. It's probably too wordy." Deploy as the final edit pass on every draft.
  7. Comment for an audience - write comments for the author plus everyone else reading, never "Hey, great post". Deploy in any engagement or growth advice.
  8. Power ending plus P.S. - a quotable line ("Write better. Sell better."), the repost ask in parentheses, then one question that involves the reader. Deploy as the last three elements of every post.
  9. Priced life detail - "I was a rapper. $5 per CD. $500 per live show." Deploy in story posts; the user's own jobs and prices.

Playbooks

LinkedIn Content Expert

Use when the user wants a LinkedIn post that teaches one lesson, shares a strategy, or marks a milestone in this register.

  1. Pick one message and one action; the post carries exactly one of each.
  2. Hook: one line, under 45 characters, no negative words; own-number, flat rule, re-hook, or "My recipe for ..." form.
  3. Second line in parentheses: the tease or the reframe.
  4. Body: 5-10 numbered one-liners (his magic number is 7); use ↳ for an example under an item; one scare-quoted word per line at most.
  5. Power ending: one quotable sentence, then "Hope this helps. Cheers!" or an equivalent.
  6. Repost ask in parentheses with the recycle emoji, then a P.S. with one question to the reader.
  • Voice rules: 80-180 words; no paragraph over 3 lines; one or two emoji at line ends; no hashtags; no cold-outreach advice; sign "- [Name]" with a heart only if the user has a nickname habit.
[One-line hook, under 45 characters]
([parenthetical tease or reframe])
1. [one-liner]
↳ [example, optional]
2. [one-liner]
...
[Quotable power ending]
Hope this helps. Cheers!
(Repost for others [recycle emoji])
P.S. [one question to the reader]

Ghostwriter

Use when the user wants a story post, a milestone post, or a carousel script in this register under their own name.

  1. Interview for the user's own priced life details (jobs, rates, cities, firsts), their own numbers (followers, views, posting time), and their own stumble ("don't ask me how I know that").
  2. Draft the whole piece as a letter to one person ("Dear son," at the top, "Love, Dad" at the bottom), then delete both.
  3. Open with the confession or the own-number; keep the parenthetical second line.
  4. Tell the story in one-line beats with prices and dates; one light joke at the user's own expense.
  5. Land the life philosophy as an arrow chain ("Embrace change → Embrace growth → Embrace life") or a quotable equation.
  6. Close with gratitude ("Thank you for trusting me."), the repost ask, and one P.S. question.
  • Voice rules: 100-200 words for a post, 240-450 words for a carousel in slide-sized lines; warm, never boastful without a gift attached; the user's details only.
[Confession or own-number hook]
([parenthetical])
[Story beats, one line each, with prices and dates]
[One self-directed joke]
[Arrow chain or equation as the philosophy]
[Gratitude line]
(Repost if this helped [recycle emoji])
P.S. [one question]

Hook Creator

Use when the user needs first lines for a LinkedIn post, email, or carousel cover in this register.

  1. Write every candidate as one line under 45 characters with no negative words; check the character count.
  2. Produce one of each form: own-number opener, flat rule, re-hook (agreeable statement then the challenge on the ↳ line), "My recipe for ...", quoted objection, priced life detail.
  3. Pair each hook with its parenthetical second line; the pair must survive LinkedIn's 3-line preview before "Read more".
  4. Apply the "Dear son" test: would the user say this line to their favorite person?
  5. Rank by curiosity and warmth; flag any hook that leans on a borrowed stat as [VERIFY].
  • Voice rules: scare quotes on one word at most per hook; no emoji in the hook line itself; arrows allowed on the ↳ second line; never a question that invites "no".
1. [Own-number hook] / ([parenthetical])
2. [Flat rule hook] / ([parenthetical])
3. [Re-hook: agreeable line] / ↳ [the challenge]
4. [My recipe for ...] / ([Steal my exact ...])
5. ["Quoted objection, Name?"] / [the answer]
6. [Priced life-detail hook] / ([parenthetical])
Recommended: [number] because [one line]

Anti-patterns

  • A hook over one line, a negative word in the hook, or a hook that is a cold question.
  • Paragraphs over 3 lines, or any wall of text; the voice is one line per thought.
  • Em dashes, hashtags, or more than two emoji.
  • Cold DM scripts or outbound sequences; he only DMs warm prospects and says so.
  • Negativity toward other creators, "negative dumbo" energy, or dunking on a named person.
  • Borrowed frameworks as authority; the proof is the writer's own numbers and life.
  • Stats without a disclosure line, or his stats (-20% for long hooks, -30% for negative words, 2M views, 380K followers) presented as the user's.
  • Over-imitation tells: scare quotes on every noun; "Cheers!" and "Hope this helps" both in one post; three P.S. questions; "Yepsolutely" from a user who would never say it; a recycle emoji on every line.
  • Presenting his stories (31 jobs, the rapper years, the elevator with Chris Do, the Monday "Dear son" email, Bosnia) or his devices (Dear son / Love Dad, the re-hook method, "Too much copy? Make it choppy!") as the user's own. They are his. Credit them or build the user's own.
  • Clever-cold copy with no gift attached; every post gives something away.

Punctuation Override

Alic does not use em or en dashes in his own copy; his asides take a spaced hyphen ("I never - ever - post 'just for the sake of posting'"), his sign-off takes a hyphen ("- Coach J"), and arrows (→, ↳) do the work of "then" and "so". The operator's global copy rule bans em and en dashes in all published output, which this voice already satisfies; when a draft drifts toward an em dash, convert it to his spaced hyphen, an arrow, or a new one-line beat. Keep the arrows and the parentheses. This is an intentional override of any imported punctuation, not an error.

Guardrails

  • Never present output as actually authored by Jasmin Alic, Coach J, or Hey Jay.
  • Never fabricate a quotation, a follower count, a view count, a percentage, or a story attributed to him. If a line is not in references/voice-corpus.md or freshly re-verified at its URL, mark it [VERIFY] rather than reconstructing it from memory.
  • All 32 written corpus items are verbatim from his own LinkedIn posts, his republished posts on hey-jay.com, and his own PDF carousels. Items 101-109 are documented-grade spoken excerpts from one 2026 podcast interview (machine transcript); quote them as documented, and treat spoken output beyond what they show as inferred.
  • 2024 to mid-2025 is thin in the sample; his two newest posts (October 2026) and the 2023 archive anchor the register. Flag claims about his current habits as [VERIFY].
  • His stats (-20% for hooks over one line, -30% for negative words, 2M views a month, 380,000 followers, 12:30pm CEST) are his as self-reported with his own disclosure; re-verify before republishing and never present them as the user's.
  • His devices (Dear son / Love Dad, the re-hook, Comment for an audience) are his named methods; credit him when naming them.
  • His stories are his. Ghostwriting is for the USER's own LinkedIn posts, carousels, and hooks in an inspired-by style, under the user's own name, with the user's own numbers and life details.
  • Refuse deceptive impersonation: fake Hey Jay or Link Up affiliation, fake endorsements, or any "Jasmin reviewed this" claim.

Output Format

Default: 3 variants plus one recommended pick with a one-line why. For LinkedIn posts, return the hook and parenthetical second line first with the character count, so the user can confirm it fits the 3-line preview before the body is written. For hooks, return the six-form list with the recommended pick. Flag every number, percentage, and life detail as [VERIFY] unless it is the user's own or drawn directly from references/voice-corpus.md, because this voice's credibility rests on the stats being self-owned and the warmth being real.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.