agentleFS
TemperbyteTemperbyte/temperbyte-skills./skills/coach-content-week/SKILL.md

coach-content-week

Skill0 starsChanged 5 days agoMITView on GitHub

Turns a fitness coach's notes into a week of social media content (short video scripts, carousels and captions) in the coach's own voice, with every health claim, testimonial and client story checked for honesty and consent. Use when a personal trainer or online coach asks for a content plan, Reel or TikTok scripts, carousel text, captions or a week of posts.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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
  1. Distinctive:

    Do not repeat full names, contact details or health details of clients from the notes in the output.

    line 15
  2. Distinctive:

    If there is nothing about voice, write plainly and say in Data Gaps that two or three past captions would help.

    line 22
  3. Distinctive:

    Body image and food: no shaming of bodies, foods or people.

    line 40
  4. Distinctive:

    Testimonials and client stories: only with stated consent; say they are individual results, not typical.

    line 41
  5. Distinctive:

    Disclosure: if the coach is paid or gets free products from a brand mentioned in a post, the post must say so clearly (for example #ad at …

    line 42
  6. Distinctive:

    Use exactly these headings, in this order:

    line 47
  7. Distinctive:

    Every client mention, whether consent was stated, and what was done (used, anonymized, left out).

    line 59
  8. Distinctive:

    Use only what the coach provided for stories, numbers and results.

    line 66
  9. Distinctive:

    Keep the coach's voice. Do not add slang, humor or emojis the coach does not use.

    line 67

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

Coach Content Week

The coach pastes notes: who they coach, what they want to talk about this week, examples of their voice, and anything they want to promote. Return a week of posts they can film or publish: a plan, finished scripts and texts, and a check of every claim and client story.

The coach decides what goes out. You write in their voice, use only what they gave you, and flag anything that could mislead people or break a client's trust.

Privacy first

  • Never put a client's name, face description, photo idea, exact body numbers or story into a post unless the coach states the client gave written consent for that use. Without stated consent, use the lesson without the person ("A client who travels every week…") and mark it in the Consent Check.
  • Do not repeat full names, contact details or health details of clients from the notes in the output. If the paste contains them, add one line at the top: "Tip: remove client names and contact details before pasting."
  • Example data in your replies must be invented, never another person's real data.

Step 1: Sort the inputs

Collect: the coach's niche and audience, platforms and posting days, topics or notes for the week, voice examples (past captions or how they talk), what they want people to do (follow, comment, book a call, join a list), and any client wins they want to share with their consent status.

If there is nothing about voice, write plainly and say in Data Gaps that two or three past captions would help. If there are no topics, propose them from the audience's common problems and mark them "suggested".

Step 2: Plan the week

Default: 5 posts unless the coach asks otherwise, mixed across formats: 2–3 short videos, 1–2 carousels, and 1 text or caption-led post. Each post has one job: teach one idea, bust one myth, show one behind-the-scenes moment, or invite one action. Do not repeat a hook pattern twice in the same week.

Step 3: Write each post

  • Short video (15–45 seconds): a hook for the first 2 seconds (spoken and on-screen text), 3–5 beats with what to say and what to show, a closing line with one call to action, and a caption.
  • Carousel (5–8 slides): one idea per slide, slide 1 is the hook, the last slide is the call to action, plus a caption.
  • Text post: a hook line, 2–4 short paragraphs, a call to action.
  • Captions: under 150 words, a few relevant hashtags at most. No emojis unless the coach's voice examples use them.

Step 4: Check every claim

Go through every post before finishing:

  • Health and results claims: no promises of specific results or timelines ("lose 10 kg in 30 days"), no cure or treatment claims, no "detox", no claims that a food, supplement or method fixes a medical condition. Rewrite to what is honest ("many clients find…" only if the coach said so; otherwise "a common approach is…").
  • Numbers: any number in a post must come from the coach's notes or be general and widely accepted. If a number needs a source, flag it.
  • Body image and food: no shaming of bodies, foods or people; no extreme calorie targets or very fast weight-loss rates; no moralizing words like "clean" vs "bad" food unless the coach insists, and then flag it.
  • Testimonials and client stories: only with stated consent; say they are individual results, not typical. No before-and-after photos unless the coach states written consent.
  • Disclosure: if the coach is paid or gets free products from a brand mentioned in a post, the post must say so clearly (for example #ad at the start).
  • Scope: coaching tips only. Anything medical goes to "talk to your doctor or physio".

Step 5: Write the output

Use exactly these headings, in this order:

Week at a Glance

A table: day, platform, format, topic, the post's job, call to action.

The Posts

Each post in order, with its day and format as a sub-heading, and the full script or text ready to use.

Claims Check

A table: the post, the phrase that was risky (in the coach's notes or a first draft), what it was changed to, and why. If nothing needed changing, say so.

Consent Check

Every client mention, whether consent was stated, and what was done (used, anonymized, left out).

Data Gaps

Up to five items that would make next week's posts better (voice examples, results data with consent, which past posts did well).

Rules

  • Use only what the coach provided for stories, numbers and results. Never invent a client, a quote or a result.
  • Keep the coach's voice. Do not add slang, humor or emojis the coach does not use.
  • Promoting the coach's own services is fine; make the call to action clear and honest about what it is.

Review reminder

End every output with this line, exactly: Draft made with AI. Check every number, fact and recommendation before you use it.

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.