feat(skills): lokf-scaffolding and lokf-librarian

[noelmcloughlin]

Two generic skills to manage a lokf/knowledge sidecar in any "folder-native" platform (GIT, Cloud Storage, local volume).

Audience:

• lokf project maintainer ("lokf eats its own dog food")
• end users (mechanism of advertising I leave to maintainer)

LOKF Librarian

Maintain lokf/ - the host repository's knowledge captured as a Linked Open Knowledge Format (LOKF) bundle. LOKF is a semantic profile of OKF: the same directory of Markdown + YAML frontmatter, but every field, type, and relationship is bound to a public vocabulary (schema.org / DCAT / PROV-O), so the bundle expands losslessly to JSON/JSON-LD and RDF and is queryable with SPARQL. This skill covers the full lifecycle: scrape -> build/maintain -> audit -> hand off for review -> keep fresh on a schedule.

LOKF Scaffolding

Create a fresh lokf/ sidecar - a machine-readable, SPARQL-queryable LOKF knowledge bundle - inside whatever repository this skill is invoked from. This skill lays down the directory, tooling, docs, and a small dummy bundle skeleton, then hands off to the lokf-librarian skill to fill it with real knowledge.

Notes

1. GIT scenario - maybe the lokf-librarian SKILL should log last git commit (since last run) and only execute if more recent commits are found. But could be future consideration.

2. I did not execute on this repository as this is at discretion of project maintainer.

3. I did not consider how this should be documented (for end users) for same reason.

[noelmcloughlin]

Maybe sidecar name should be .lokf not lokf.

[noelmcloughlin]

Updated SKILLS:

• fable audit and minor improvements
• adopt .lokf/ instead of lokf/ as knowledge home
• updated logging policy (don't log "ran librarian, no changes detected" entry to avoid useless PRs).

I think they are good to go now.