agentleFS
Sign inStart free
sam-ash-cysam-ash-cy/sams-agentic-workflow/skills/about-me/SKILL.md

about-me

Skill2 starsChanged 10 days agoMITView on GitHub

Use when the user asks to set up, fill in or update their "about me" profile, goals or working preferences, or when `saw about-me show` reports no answers and the user agrees to an interview. Interviews them (~50 questions in six groups) and writes the answers to the global or project about-me file.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. whawkinsiv/solo-founder-skills★ 260same name
    2. whawkinsiv/claude-code-skills★ 258same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Ask which scope, unless the user said.

    line 20
  2. Distinctive:

    Read the file. Answered questions are prefill: show the current answer and ask only whether it changed.

    line 21
  3. Distinctive:

    Write each answer under its question with Edit, in the user's words, one or two lines.

    line 24
  4. Distinctive:

    Stop early whenever the user wants.

    line 28

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

About-me interview

The profile is plain Markdown: ## section, ### question, the answer underneath. saw puts the merged answers in every session's context (features.about_me).

ScopeFileUse for
global (default)~/.saw/about-me.mdwho the user is, across all projects
projectdocs/about-me.mdthis project's goals and rules; committed, so nothing personal
local.saw/about-me.local.mdpersonal notes for this project; gitignored

A project or local answer replaces the global answer to the same question.

Steps

  1. Ask which scope, unless the user said. Run saw about-me --scope <scope> to create the file from the template if it's missing.
  2. Read the file. Answered questions are prefill: show the current answer and ask only whether it changed.
  3. Go through the six sections in order. Ask one section at a time with AskUserQuestion: up to 4 questions per call, two calls per section, each with 2–4 likely answers (the user can always type their own). For open questions (what are you building, success in a month) ask in plain text instead. Every question is skippable; never push.
  4. For the project scope, skip personal questions (role, experience, working week) and keep answers safe to commit: no names, emails, paths or secrets.
  5. Write each answer under its question with Edit, in the user's words, one or two lines. Leave skipped questions blank. Don't reorder or delete questions the user didn't ask to remove.
  6. Show saw about-me show and ask if anything reads wrong.
  7. Suggest settings the answers imply (for example saw config set autonomy.level act --scope global, style.tone, features.tdd), as commands for the user to approve, not changes made silently.

Stop early whenever the user wants; partial profiles work.

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