agentleFS
allthriveaiallthriveai/amplify/.claude/skills/add-inspiration/SKILL.md

add-inspiration

Skill0 starsChanged 3 months agoMITView on GitHub

Captures a person who inspires you. Researches their bio, work, and quotes on the web, then asks what you admire and what you've learned. Writes a structured note to the vault with back-links to your moments and research.

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 10 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

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

    When the user runs /add-inspiration, optionally followed by a person's name and/or URL:

    line 10
  2. Very specific:

    Read the config and resolve the vault path.

    line 20
  3. Very specific:

    Read {vaultPath}/{paths.voice} (Voice.md) if it exists.

    line 22
  4. Distinctive:

    If no name is given, ask: "Who inspires you?

    line 32
  5. Very specific:

    Check if a note already exists at {people}/{Person Name}.md.

    line 34
  6. Distinctive:

    Run 2-3 WebSearch queries to gather background:

    line 38
  7. Distinctive:

    If the user provided a URL, use WebFetch to pull content from it (personal site, profile, interview, etc).

    line 44
  8. Distinctive:

    Ask these three questions one at a time using AskUserQuestion or natural conversation.

    line 56
  9. Distinctive:

    If the user says "skip" or gives no answer to question 3, move on.

    line 67
  10. Distinctive:

    Search the vault for mentions of this person.

    line 71
  11. Distinctive:

    Use Grep with the person's name (and aliases if they have one) across these directories.

    line 77
  12. Very specific:

    Write to {vaultPath}/{paths.people}/{person-name}.md — kebab-case filename, Title Case # Heading — using this template:

    line 83
  13. Distinctive:

    If the user gave an answer to question 3, add it as:

    line 121
  14. Distinctive:

    If back-links were found in Step 4, add:

    line 129
  15. Distinctive:

    Keep quotes accurate. Do not fabricate quotes.

    line 141
  16. Very specific:

    Use Obsidian wiki-links ([[Note Title]]) for back-links.

    line 142
  17. Very specific:

    Don't write a folder README here.

    line 150
  18. Very specific:

    Add one line to {vaultPath}/{paths.wiki}/index.md under ## Entities:

    line 153

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

Add Inspiration

Instructions

When the user runs /add-inspiration, optionally followed by a person's name and/or URL:

Step 0: Load Context

Find the .amplifyrc config file. Check these locations in order:

  1. .amplifyrc in the current working directory
  2. .amplifyrc at the path specified by VAULT_PATH environment variable
  3. .amplifyrc at the fallback vault path (if configured in CLAUDE.md or known from previous sessions)

Read the config and resolve the vault path. Entity pages live at {vaultPath}/{paths.people} (default: Wiki/Entities) — inside the wiki, so the schema in {vaultPath}/CLAUDE.md applies.

Read {vaultPath}/{paths.voice} (Voice.md) if it exists.

Step 1: Parse Input

Extract the person's name from the user's input. They might say:

  • /add-inspiration Matthew Dicks
  • /add-inspiration swyx https://swyx.io
  • /add-inspiration (no name given, ask them)

If no name is given, ask: "Who inspires you? Give me a name."

Check if a note already exists at {people}/{Person Name}.md. If it does, tell the user and ask if they want to update it or pick someone else.

Step 2: Research on the Web

Run 2-3 WebSearch queries to gather background:

  1. "{name}" bio for background info
  2. "{name}" best work books talks projects for key work and links
  3. "{name}" quotes for notable quotes

If the user provided a URL, use WebFetch to pull content from it (personal site, profile, interview, etc).

From the results, compile:

  • Full name and any common aliases (e.g., "Shawn Wang" / "swyx")
  • Bio: 3-5 sentences covering who they are, what they do, why they matter
  • Key work: books, talks, projects, companies, with URLs where available
  • Quotes: 2-4 notable quotes with attribution
  • Domain tags: 2-4 topic tags (e.g., storytelling, developer-community, ai)

Step 3: Interview the User

Ask these three questions one at a time using AskUserQuestion or natural conversation. Wait for each answer before asking the next.

Question 1: What do you admire? "What do you admire about {name}? What draws you to their work?"

Question 2: What have you learned? "What have you learned from {name}? How has their thinking changed yours?"

Question 3: Anything else? "Anything else you want to capture about {name}? Skip if you're done."

If the user says "skip" or gives no answer to question 3, move on.

Step 4: Scan Vault for Back-Links

Search the vault for mentions of this person. Check:

  1. Sources at {paths.sources}: search clipping content and titles
  2. Wiki at {paths.wiki}: scan index.md for related pages, then the pages it names
  3. Stories at {paths.stories}: search note content

Use Grep with the person's name (and aliases if they have one) across these directories.

Collect any matches as back-links: note title, path, and a short excerpt of the mention.

Step 5: Write the Note

Write to {vaultPath}/{paths.people}/{person-name}.md — kebab-case filename, Title Case # Heading — using this template:

---
tags: [inspiration, {domain-tag-1}, {domain-tag-2}]
sources: [{clipping filenames this draws on, or empty}]
created: YYYY-MM-DD
updated: YYYY-MM-DD
aliases: ["{Person Name}", {other aliases if any}]
---

# {Person Name}

## Who they are

{Bio: 3-5 sentences. Factual, specific, no fluff.}

## What I admire

{User's answer to question 1, preserved in their words.}

## What I've learned

{User's answer to question 2, preserved in their words.}

## Their work

{Bulleted list of key work with links where available:}
- [{Title}]({URL}) — one-line description
- [{Title}]({URL}) — one-line description

## Quotes that stick with me

> "{Quote 1}" — {Person Name}

> "{Quote 2}" — {Person Name}

If the user gave an answer to question 3, add it as:

## Notes

{User's additional notes, preserved in their words.}

If back-links were found in Step 4, add:

## Connections in my vault

- [[{Moment or Note Title}]] — "{short excerpt of the mention}"
- [[{Another Note Title}]] — "{short excerpt}"

Writing rules:

  • Preserve the user's exact words in "What I admire," "What I've learned," and "Notes." Do not rewrite their answers.
  • Apply humanizer rules to the bio and any prose you write (no AI vocabulary, no filler, no em dashes, vary sentence length).
  • Keep quotes accurate. Do not fabricate quotes. If you can't verify a quote, don't include it.
  • Use Obsidian wiki-links ([[Note Title]]) for back-links.

Step 6: Update the wiki index and log

The note lands in {paths.people}, which is Wiki/Entities — the wiki's entity layer. So it is a wiki page and follows the schema in {vaultPath}/CLAUDE.md: kebab-case filename, Title Case # Heading, and the standard frontmatter.

Don't write a folder README here. The wiki navigates itself through index.md, and a second hand-maintained list beside it is the thing that goes stale.

Add one line to {vaultPath}/{paths.wiki}/index.md under ## Entities:

- [[{Person Name}]] — {one-line summary from bio}

Append to {vaultPath}/{paths.wiki}/log.md:

## [YYYY-MM-DD] ingest | {Person Name}
Added entity page. Linked to [[{whatever it connects to}]].

The orphan rule applies. The page must link to at least one existing page. The back-links found in Step 4 usually cover it; if nothing connects, that is a signal the wiki is missing a concept page about what you admire in this person's work.

Step 7: Emit Signal

Append to the signals file at {vaultPath}/{paths.signals}/signals.json:

{
  "id": "sig-[timestamp]-[random6hex]",
  "type": "inspiration_added",
  "timestamp": "{ISO 8601}",
  "data": {
    "person": "{Person Name}",
    "tags": ["{domain-tags}"],
    "backLinks": {count},
    "path": "{paths.people}/{person-name}.md"
  }
}

Step 8: Log to Session Memory

Append to today's session log at {vaultPath}/{paths.memory}/sessions/YYYY-MM-DD.md:

- **HH:MM** — inspiration_added: "{Person Name}", tags: [{tags}], back-links: {count}

Step 9: Report

Tell the user what happened:

**Added**: {Person Name}
**Bio**: {one-line summary}
**Tags**: {tags joined with ", "}
**Back-links**: {count} connections found in your vault
**Saved to**: {paths.people}/{person-name}.md

{If back-links > 0: "This person already shows up in {count} of your notes. Check the Connections section."}

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.