CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-history-ingest

Ingest OpenClaw session/history data into Obsidian as distilled knowledge. Use for importing or mining ~/.openclaw sessions, memory files, or logs; use wiki-agent for targeted topic-only cross-agent recall.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered operational skill: concrete commands with locking semantics, privacy filtering, manifest-based incremental processing, and explicit validation and failure handling for both the ingest and the QMD refresh. The main improvable areas are minor redundancy between the layout tree and the ranked source list, and a few template placeholders plus unverifiable external reference paths.

Suggestions

Merge the 'Key data sources ranked by value' list into the data-layout tree (e.g., annotate each path with its value rank) to remove the duplicated walkthrough of the same five sources.

Move the manifest JSON schema and the QMD refresh procedure into a reference file (e.g., references/qmd-refresh.md), keeping SKILL.md to a short pointer plus the status-vocabulary list.

Replace template placeholders like `lifecycle_changed: <obsidian-wiki memory now --date>` with a literal example invocation so the field is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense operational instruction that assumes competence — no padding explaining what JSONL or Obsidian is, and it states rules tersely ("Skip credentials/ entirely. Skip agents/*/agent/models.json"). Below anchor 5 because the data-layout tree and the 'Key data sources ranked by value' list cover the same ground twice, and the manifest JSON example includes illustrative counts that could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready commands dominate: `obsidian-wiki memory sync OPENCLAW_HISTORY_INGEST memory=<memory> ... --takeaways "..."`, `${QMD_CLI:-qmd} update/embed/ls/get`, plus executable JSON/JSONL/manifest examples. Not anchor 5 because some snippets remain templates — `lifecycle_changed: <obsidian-wiki memory now --date>` and placeholder counts in the manifest block — leaving minor gaps for a first-time executor.

4 / 5

Workflow Clarity

A clearly sequenced 7-step pipeline with explicit checkpoints and feedback loops appropriate to a batch operation: delta classification (New/Modified/Unchanged), "Report a concise delta summary before deep parsing", and the QMD section's validate-then-branch flow ("If the output says vectors are needed or embeddings may be stale, run qmd embed") with explicit failure handling ("If QMD refresh fails, do not roll back the vault changes; report the QMD status separately") and a recorded status vocabulary. The batch-operation validation cap does not apply because validation is present.

5 / 5

Progressive Disclosure

The single bundle reference is well-signaled and real: "See `references/openclaw-data-format.md` for field-level notes and parsing guidance" points to an existing file, and externalized procedure lives in named external skills (llm-wiki/SKILL.md). Below anchor 5 because several in-bundle/external paths (`.skills/llm-wiki/references/MEMORY.md`, `references/` inside llm-wiki) cannot be verified from this bundle and add navigation risk, and the SKILL.md itself is long enough (260 lines) that some inline detail (manifest schema, QMD refresh) could be split into references.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description in third-person voice: it states what the skill does, gives explicit 'Use for' trigger conditions with concrete artifact names, and even disambiguates a neighboring skill. The only gaps are a few missing synonyms (transcripts, JSONL, MEMORY.md) and slightly thin coverage of the ingest pipeline's specifics.

DimensionReasoningScore

Specificity

"Ingest OpenClaw session/history data into Obsidian as distilled knowledge" plus "importing or mining" names the domain, destination, and several concrete actions (ingest, import, mine, distill). It sits above anchor 3 (only 1-2 actions) because multiple actions are named, but below anchor 5 because coverage of what the ingest covers (e.g., clustering, privacy filtering, manifest tracking) is not hinted at.

4 / 5

Completeness

It explicitly answers both: what ("Ingest OpenClaw session/history data into Obsidian as distilled knowledge") and when ("Use for importing or mining ~/.openclaw sessions, memory files, or logs") with concrete trigger phrases, matching the anchor-5 example pattern. The explicit 'Use for...' clause satisfies the trigger-guidance requirement, so no cap applies.

5 / 5

Trigger Term Quality

Natural trigger terms are present: "importing", "mining", "sessions", "history data", "memory files", "logs", "~/.openclaw", "Obsidian" — phrases a user of this niche would plausibly say. Not anchor 5 because common synonyms and artifact names users might mention ("transcripts", "JSONL", "MEMORY.md", "daily notes") are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow (OpenClaw artifacts → Obsidian wiki) and it actively disambiguates against a sibling skill: "use wiki-agent for targeted topic-only cross-agent recall." Minimal conflict risk; clearly distinguishable.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Ar9av/obsidian-wiki

Path

.skills/openclaw-history-ingest/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.