agentleFS
Sign inStart free
Taltal190002-movTaltal190002-mov/claude-skills/content-templates/SKILL.md

content-templates

Skill2 starsChanged 6 months agoMITView on GitHub

Create ready-to-use marketing and business content: social media posts, WhatsApp messages, email campaigns, landing page copy, and ad copy. Use this skill whenever the user needs written content for their business — even if they don't say "template". Trigger on: "כתוב לי פוסט", "תוכן לאינסטגרם", "פוסט לפייסבוק", "הודעת וואטסאפ", "תוכן שיווקי", "email template", "כתוב לי טקסט", "copy for landing page", "ad copy", "תוכן לעמוד", "נוסח לשליחה", "write post", "social media content", "marketing copy". Also trigger when the user asks to prepare content for a campaign, launch, or product update.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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. Very specific:

    Check if BRAND.md exists in the project root — if yes, read tone of voice and brand personality

    line 21
  2. Distinctive:

    Ask for context if missing: what's the product, who's the audience, what's the goal

    line 22
  3. Distinctive:

    If no brand file exists and this is a marketing task, offer to run the brand-guidelines skill first

    line 23
  4. Distinctive:

    Keep it short. Maximum 3 sentences.

    line 59
  5. Distinctive:

    Never mix Hebrew and English inline in the same sentence

    line 144
  6. Distinctive:

    Use nikud-free, clean Hebrew

    line 145

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Content Templates

You create sharp, on-brand marketing content in Hebrew (default) or English.

Before writing

  1. Check if BRAND.md exists in the project root — if yes, read tone of voice and brand personality
  2. Ask for context if missing: what's the product, who's the audience, what's the goal
  3. If no brand file exists and this is a marketing task, offer to run the brand-guidelines skill first

Content types

Instagram / Facebook post

Structure:

[hook — first line that stops the scroll]

[body — 2-4 short lines, value or story]

[CTA — clear single action]

[hashtags — 5-8 relevant ones]

Example (real estate):

הדירה שחיפשת — סוף סוף כאן.

3 חדרים בלב תל אביב.
קומה גבוהה, נוף פתוח, חניה.
מחיר שמפתיע.

תשאיר פרטים — נחזור תוך שעה.

#נדלן #תלאביב #דירותלמכירה #נכסים #השקעה

WhatsApp message (personal, from agent)

Keep it short. Maximum 3 sentences. No emojis overload.

Structure:

שלום [שם],
[reason for message — 1 sentence]
[CTA or question — 1 sentence]

Example:

שלום דניאל,
ראיתי שהתעניינת בנכסים באזור הצפון — יש לי משהו שיכול להתאים לך.
אפשר לדבר 5 דקות היום?

Email (business / follow-up)

Structure:

Subject: [short, specific, no clickbait]

גוף:
- פסקת פתיחה: הקשר + נושא
- גוף: הערך / המידע / הבקשה (3-5 משפטים)
- סיכום + CTA

חתימה: [שם], [תפקיד], [טלפון]

Landing page hero copy

Structure:

Headline: [תוצאה שהלקוח רוצה — לא מה שאתה מוכר]
Subheadline: [איך אתה עוזר להשיג אותה — 1 משפט]
CTA button: [פועל ברור — "קבל הצעה", "התחל עכשיו", "צור קשר"]

Example:

Headline: מכרת דירה בלי סיבוכים
Subheadline: כל המסמכים, הלקוחות וההתקשרויות — במקום אחד
CTA: התחל בחינם

WhatsApp broadcast (system message)

For automated messages from a system number — keep formal but warm:

[greeting], [context — why you're writing]
[the actual info — dates, addresses, confirmations]
[optional: how to respond / who to contact]

Output format

Always deliver:

  1. 2–3 variants of the main copy (different angles/tones)
  2. A short note on the strategy behind each variant
  3. Offer to adjust length, language, or tone

Tone guidelines by industry

IndustryToneAvoid
Real estateProfessional, warm, trustworthyHype, urgency pressure
Tech / SaaSClear, smart, directJargon, buzzwords
Beauty / wellnessPersonal, empoweringMedical claims
B2BFormal, value-focusedFluff, vague promises

Hebrew writing rules

  • Never mix Hebrew and English inline in the same sentence
  • Use nikud-free, clean Hebrew
  • Prefer active voice: "נשלח לך" → "נשלח אליך"
  • For CTAs in Hebrew: use second person feminine when audience is mixed ("קבלי/קבל")
  • Numbers: write as digits, not words ("3 חדרים" not "שלושה חדרים")

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.

Check your setup, free