Originally when I was designing nostr:npub12237stmmxapc2ta7s...

Laan Tungir

npub1rmz9gu6de0m0u4ysrn39crrud099ahvfgs6pvasl4hpjr5ud7yus54xv06

hex

6e5c5210f0a9608ca8614018348e26fe1dfa5c7b8f7018853caf3ed7ecc364dd

nevent

nevent1qqsxuhzjzrc2jcyv4ps5qxp53cn0u806t3ac7uqcs57270khanpkfhgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgspa3z5wdxuhah72jgpecjup37xhjj7mky5gdqkwc06msep6wxlzwgz2svpt

Kind-1 (TextNote)

2026-03-15T00:35:28Z

Originally when I was designing nostr:npub12237stmmxapc2ta7spx0e06dkdzgz9vg0z2jglqqru44peus4juqg598qn I copied the OpenClaw idea of having a "soul" file that defines the overall the personality of the agent. 

But as I've been working on this, I've come to realize how powerful the concept of a SKILL is. SKILLS can transform an agent from a marriage counselor to a lowly spell checker.

I realized that SKILLS can be more universal than just a nostr-kind for a Didactyl Agent. A SKILL can live in the "Check Spelling" button in your word processor. 

You don't want your "check spelling" button to have a soul. 

I'm going to embed AI skills throughout my nostr clients, and since they are on nostr, my AI, - in all it's forms - can follow me across apps.

Nostr brought the idea of your data following you across every app. Sign in with your key, and there is your data.

SKILLS bring the idea of your AI following you across every app. Sign in and there is your AI.

So I'm abandoning the idea of a nostr kind for a soul, and am embracing the idea of everything being a SKILL kind. You can do all the things you could do with a soul, and have a simpler underlying structure. 

KISS - #didactyl

nostr:nevent1qvzqqqqqqypzq8ky23e5mjlkle2fq88ztsx8c672tmwcj3p5zempltwry8fcmufeqqstrmec9zwm3re4gkwvlu4lxpvhx4up75lms97xmqrhj4934r6x2rsyde9qu

原始 JSON

{
  "kind": 1,
  "id": "6e5c5210f0a9608ca8614018348e26fe1dfa5c7b8f7018853caf3ed7ecc364dd",
  "pubkey": "1ec454734dcbf6fe54901ce25c0c7c6bca5edd89443416761fadc321d38df139",
  "created_at": 1773534928,
  "tags": [
    [
      "p",
      "52a3e82f7b3743852fbe804cfcbf4db3448115887895247c001f2b50e790acb8"
    ],
    [
      "q",
      "b1ef38289db88f35459ccff2bf3059735781f53fb817c6d8077954b1a8f4650e",
      ""
    ],
    [
      "p",
      "1ec454734dcbf6fe54901ce25c0c7c6bca5edd89443416761fadc321d38df139"
    ],
    [
      "t",
      "didactyl"
    ]
  ],
  "content": "Originally when I was designing nostr:npub12237stmmxapc2ta7spx0e06dkdzgz9vg0z2jglqqru44peus4juqg598qn I copied the OpenClaw idea of having a \"soul\" file that defines the overall the personality of the agent. \n\n\nBut as I've been working on this, I've come to realize how powerful the concept of a SKILL is. SKILLS can transform an agent from a marriage counselor to a lowly spell checker.\n\n\nI realized that SKILLS can be more universal than just a nostr-kind for a Didactyl Agent. A SKILL can live in the \"Check Spelling\" button in your word processor. \n\n\nYou don't want your \"check spelling\" button to have a soul. \n\n\nI'm going to embed AI skills throughout my nostr clients, and since they are on nostr, my AI, - in all it's forms - can follow me across apps.\n\n\nNostr brought the idea of your data following you across every app. Sign in with your key, and there is your data.\n\n\nSKILLS bring the idea of your AI following you across every app. Sign in and there is your AI.\n\n\nSo I'm abandoning the idea of a nostr kind for a soul, and am embracing the idea of everything being a SKILL kind. You can do all the things you could do with a soul, and have a simpler underlying structure. \n\n\nKISS - #didactyl\n\nnostr:nevent1qvzqqqqqqypzq8ky23e5mjlkle2fq88ztsx8c672tmwcj3p5zempltwry8fcmufeqqstrmec9zwm3re4gkwvlu4lxpvhx4up75lms97xmqrhj4934r6x2rsyde9qu",
  "sig": "feada38ece06ff348c089ef56523633b7256524fc0ead647fa3c13a5dce544289c7544b6b29468d88c35991a63a4dba30183401e993b9283168bb704a01d0cd7"
}