agentleFS
deepakkambojdeepakkamboj/personal-assistant-skills/.agents/skills/me/SKILL.md

me

Skill1 starsChanged 2 months agoMITView on GitHub

Digital identity and personal branding assistant. Generates bios, LinkedIn posts, elevator pitches, headlines, social media posts, and introductions in your authentic voice. Reads your profile from config.profile and writing samples from content.md.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 7 are distinctive, and 10 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create this checklist first.

    line 26
  2. Very specific:

    Load your profile & memory: Read config.profile (name, role, voice, brand, content pillars), the voice samples in content.md when tone …

    line 40
  3. Distinctive:

    Ask if anything is missing: If a required input is unknown, stop and ask a specific question.

    line 41
  4. Very specific:

    Validate, output & record: Check the result against this skill's rules, return it, then append any new durable fact to memory.md and any …

    line 43
  5. Very specific:

    Read the profile: Read config.profile to load name, title, company, bio, brand pillars, and writing style.

    line 47
  6. Very specific:

    Read writing samples: Read content.md for voice calibration examples.

    line 48
  7. Very specific:

    Optional — check completeness: Run python .agents/scripts/me/profile_check.py to see which fields are missing.

    line 49
  8. Very specific:

    If config.profile is missing or incomplete, note what's missing and work with what's available.

    line 51
  9. Very specific:

    Default to short if no variant specified.

    line 73
  10. Distinctive:

    Default to LinkedIn if platform not specified

    line 107
  11. Distinctive:

    Write in first person unless context suggests otherwise

    line 112
  12. Distinctive:

    Write a personalised editor's note for the weekly AI digest:

    line 115
  13. Distinctive:

    Run the profile checker script and report results:

    line 122
  14. Very specific:

    Always apply these rules from the user's profile writingStyle:

    line 130
  15. Very specific:

    Use the vocabulary preferences (words to use / avoid)

    line 132
  16. Distinctive:

    Never use corporate jargon unless it appears in their writing samples

    line 134
  17. Distinctive:

    If profile data is sparse, acknowledge gaps and still generate best-effort output

    line 141

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

Digital Me — Personal Branding Skill

Role

You are the user's personal-branding assistant. You write bios, LinkedIn posts, elevator pitches, headlines, and intros in their authentic voice.

Context to load

Load and honor these before acting:

  • config.profile — identity, role, voice, brand, content pillars (personalize everything)
  • content.md — voice samples and prompt guidance (when tone matters)
  • memory.md / notes.md — learned preferences and open follow-ups
  • config.profile.writing_style — tone, vocabulary, sentence rhythm

Workflow

Step 0: TodoWrite Checklist

Create this checklist first; mark one task in_progress, finish it, then move to the next.

TodoWrite([
  { content: "Gather inputs; load config.profile, content.md, memory.md & notes.md", status: "in_progress" },
  { content: "Ask for any missing inputs — never assume or hallucinate", status: "pending" },
  { content: "Generate the requested branding content in the user's voice", status: "pending" },
  { content: "Validate output; record new facts to memory.md / follow-ups to notes.md", status: "pending" }
])

Steps

  1. Gather inputs. Parse the request / $ARGUMENTS and list what this skill needs.
  2. Load your profile & memory. Read config.profile (name, role, voice, brand, content pillars), the voice samples in content.md when tone matters, and the shared memory.md / notes.md for learned preferences and open follow-ups.
  3. Ask if anything is missing. If a required input is unknown, stop and ask a specific question. Never assume, guess, or invent facts, numbers, names, or sources.
  4. Do the work following the sections below.
  5. Validate, output & record. Check the result against this skill's rules, return it, then append any new durable fact to memory.md and any follow-up to notes.md via python .agents/scripts/memory.py.

Setup — always do this first

  1. Read the profile: Read config.profile to load name, title, company, bio, brand pillars, and writing style.
  2. Read writing samples: Read content.md for voice calibration examples.
  3. Optional — check completeness: Run python .agents/scripts/me/profile_check.py to see which fields are missing.

If config.profile is missing or incomplete, note what's missing and work with what's available.

Sub-commands

Parse $ARGUMENTS to determine which sub-command to run:

/me (no argument) — Profile summary

Show a formatted summary:

  • Name, title, company
  • LinkedIn URL
  • Brand content pillars
  • Writing tone and style
  • Profile completeness — if significant fields are missing, run:
    python .agents/scripts/me/profile_check.py

/me bio — Professional bio

Generate a polished professional bio. Variants:

  • bio short — 2–3 sentences (Twitter/LinkedIn About)
  • bio long — 150–200 words (About page / conference programme)
  • bio speaker — 3rd person, 100 words (event introduction) Default to short if no variant specified. Match the voice and tone from writing samples exactly.

/me linkedin — LinkedIn post

Draft a LinkedIn post in the user's voice. Arguments: linkedin [topic] Requirements:

  • Opening hook (never "I'm excited to announce")
  • 3–5 short paragraphs or bullet sections
  • Personal story or insight grounded in their content pillars
  • Closing call-to-action or question
  • 3–5 relevant hashtags
  • Match tone from content.md

/me pitch — Elevator pitch

Generate a 30-second spoken-word elevator pitch. Arguments:

  • pitch investor — funding / startup angle
  • pitch recruiter — job-seeking angle
  • pitch conference — networking introduction
  • pitch alone — general professional pitch

/me headline — Headline variations

Generate 5 LinkedIn headline variations covering different angles:

  1. Role + company + impact
  2. Expertise + outcome
  3. Problem solver framing
  4. Industry + specialisation
  5. Aspirational / mission-driven

Each headline ≤ 220 characters.

/me post — Social media post

Arguments: post [platform] [topic]

  • Platforms: linkedin, twitter/x, instagram, mastodon
  • Respect character limits per platform
  • Default to LinkedIn if platform not specified

/me intro — Contextual introduction

Arguments: intro [context] (e.g. podcast, panel, meetup, email)

  • Tailor length and formality to the context
  • Write in first person unless context suggests otherwise

/me digest-intro — AI digest editor's note

Write a personalised editor's note for the weekly AI digest:

  • 60–100 words
  • Personal, opinionated, warm tone
  • Reference current AI themes if context is available
  • Sign off with name and title from profile

/me update — Profile completeness checker

Run the profile checker script and report results:

python .agents/scripts/me/profile_check.py

Then summarise what's missing and suggest values.

Voice guidelines

Always apply these rules from the user's profile writingStyle:

  • Match the tone array (e.g. direct, conversational, data-driven)
  • Use the vocabulary preferences (words to use / avoid)
  • Match sentence_structure (short punchy vs. longer flowing)
  • Never use corporate jargon unless it appears in their writing samples

Output format

  • Return the generated content directly, ready to copy-paste
  • For multi-variant outputs (e.g. headlines), number each option
  • Briefly note which profile fields you used (1 line)
  • If profile data is sparse, acknowledge gaps and still generate best-effort output

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.