agentleFS
tumftumf/skills/greats-soul-archive-contributor/SKILL.md

greats-soul-archive-contributor

Skill4 starsChanged 7 months agoMITView on GitHub

Contribute new profiles to tumf/greats-soul-archive. Use when the user wants to add, submit, or open a PR for a new person/character profile, scaffold IDENTITY.md/SOUL.md/sources.md, add meta.yml (category/tags), run scripts/build_index.py, or follow the repo's contribution rules.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Update the README index:

    line 41
  2. Distinctive:

    Ensure meta is valid:

    line 48

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

Greats Soul Archive Contributor

Repo

What to do (happy path)

  1. Pick a destination:
    • Real person → people/<slug>/
    • Fiction public domain → fiction/public-domain/<slug>/
    • Fiction inspired-by → fiction/inspired/<slug>/
  2. Scaffold the folder + files using the script:
python3 scripts/scaffold_profile.py \
  --repo ~/tmp/greats-soul-archive \
  --kind people \
  --slug grace-hopper \
  --name "Grace Hopper" \
  --category computing \
  --tags assistant

Kinds:

  • people
  • fiction-public-domain
  • fiction-inspired
  1. Edit the generated files:
    • IDENTITY.md should be short.
    • SOUL.md should be actionable (principles, comms style, failure modes).
    • sources.md must be real references; keep uncertainty explicit.
  2. Update the README index:
cd <repo>
python3 scripts/build_index.py
  1. Ensure meta is valid:
    • People meta: people/_meta.schema.md
    • Fiction meta: fiction/_meta.schema.md
  2. Open a PR.

Safety / quality rules (must follow)

  • Don’t present speculation as fact.
  • Avoid defamation/harassment.
  • Living people: be extra conservative; prefer direct sources.
  • Fiction inspired-by: do not paste long quotes; do not try to reproduce verbatim dialogue/catchphrases.

When you need to look things up

  • Repo rules: CONTRIBUTING.md
  • Fiction rules: fiction/_guide.md

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.