Gh kb note

Skill aymandakirgh/ghclaudetoolkit/skills/gh-kb-note

Use when the user wants to write, edit, or restructure a note in the gh-kb Obsidian vault, or mentions a knowledge-base note, a second-brain note, wikilinks, an Obsidian note, or capturing something into gh-kb. Triggers on "add a kb note", "gh-kb", "write an Obsidian note", "note this in the vault", "wikilink this", "knowledge base entry", "second brain", "capture this for the team", "kb note about X". Enforces the H1 → #tags → TL;DR → H2 → [[wikilinks]] structure, anti-hairball linking, #da-validare for unverified claims, Italian internal prose, and the correct org chart — then reminds to rebuild the tools/kb-rag index.From its SKILL.md

Install

npx -y skills add aymandakirgh/ghclaudetoolkit --skill gh-kb-note

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.5 KB, as published. Nobody here has run it

gh-kb-note

Author and edit notes in the gh-kb Obsidian vault to a consistent, queryable shape.

Note structure (in this exact order)

# H1 — one clear title, the concept the note is about. One H1 per note.
#tags — a line of hashtags right under the H1: the topic, the domain, status. Keep tags reusable (prefer existing tags over inventing near-duplicates).
TL;DR — 1–3 sentences capturing the whole note. Someone reading only this should get the point.
## H2 sections — the body, broken into scannable sections. Short paragraphs, lists where they help.
[[wikilinks]] — link to related notes inline, where the connection is real.

Anti-hairball linking

Links are load-bearing, not decoration. Link only where a reader would actually want to jump.

Don't link every proper noun on sight, or create a wall of links at the bottom.
Do link the 2–5 notes this one genuinely depends on or extends.
Prefer a few strong links over many weak ones. A hairball (everything links to everything) destroys the graph's signal. If a link wouldn't help a reader, drop it.

Unverified claims → `#da-validare`

Internal notes capture fast, so not everything is checked. Tag any claim, number, or assertion you haven't verified with #da-validare (inline, next to the claim or in the section's tag line). This makes the unverified surface searchable so it can be confirmed later. Never present an unverified number as fact.

Language

Internal prose is Italian. Write the note body in Italian (tags, code, and proper nouns stay as they are). This matches the team's internal-content convention.

Org chart — get it right

KB notes are the team's memory; wrong roles propagate. Canonical:

Persona	Ruolo
Federico	CEO
Michelangelo	Socio / Sherpa — NON è il CTO
Giacomo	CTO
Ayman	dipendente AI-ops / builder — non founder

Do not call Michelangelo CTO. Do not call Ayman a founder. When a note references roles, match this table.

After writing — rebuild the index

The vault is fronted by a RAG index. Always end by reminding the user to rebuild it:

Ricorda di rigenerare l'indice: esegui la rigenerazione di tools/kb-rag così la nuova nota diventa ricercabile.

If you can run it for them and they've asked, do so; otherwise leave the reminder explicitly.

Editing existing notes

When editing, preserve the structure above, keep existing tags/wikilinks that still apply, add #da-validare to anything newly asserted-but-unverified, and end with the same index-rebuild reminder.