CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conversation-archive

Import AI-assistant chat exports (ChatGPT, Claude, Perplexity) and agent session transcripts into the brain as one dated page per conversation under conversations/, validate each page against the native conversation parser, extract facts via the native conversation-facts flow, and keep the archive gap-free with a detect-and-backfill loop. Then answer archive questions: "when did I first discuss X", trace how an idea evolved across past conversations, pull a specific thread.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugin-variants/gbrain-daily/skills/conversation-archive/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

The body is an unusually strong operational manual: fully executable commands, a correctly sequenced import/backfill pipeline with real validation checkpoints and error-recovery feedback loops, and dense project-specific knowledge with essentially zero generic filler. Its two weaknesses are structural: the same critical rules are restated three or four times across the Invariants, Anti-Patterns, and Contract sections (conciseness), and everything lives inline in one long file with no reference bundle for the detailed catalogs (progressive disclosure).

Suggestions

De-duplicate the triple restatement: keep the three invariants in their root-caused section and have the Anti-Patterns and Contract sections reference them by name ('invariant 2') instead of re-explaining each one.

Move the detailed catalogs — the redaction/PII pattern list, the native-vs-manual delta, and the append_page concurrency mechanics — into a references/ file (e.g. references/redaction-patterns.md, references/append-semantics.md) and keep one-line pointers in SKILL.md, shortening the body substantially.

The Contract section's admission that it 'exists for the conformance test' duplicates the body wholesale; consider generating or condensing it to a short bulleted guarantee list that cites the governing sections.

DimensionReasoningScore

Conciseness

The body is genuinely dense — nearly every line is project-specific operational knowledge (gbrain CLI semantics, page ceilings, CAS/slug-collision behavior, --max-bytes checkpoint fingerprinting) with no explanations of concepts Claude already knows. However, the same rules are restated multiple times: the three invariants appear in their own section, again in Anti-Patterns, and again in the Contract; secret/PII redaction rules appear in Step 1.5, the native-vs-manual delta paragraph, Anti-Patterns, and the Contract; slug-collision guidance appears three times. That deliberate triple-statement plus a Contract section that admits it 'exists for the conformance test' is more than minor over-explanation — it fits 'mostly efficient but could be tightened'.

3 / 5

Actionability

Guidance is copy-paste ready throughout: exact CLI invocations with flags ("gbrain transcripts ingest ~/Downloads/conversations.json", "gbrain extract-conversation-facts --types conversation --dry-run --limit 5", "gbrain conversation-parser scan conversations/chatgpt/2025-03-15-agent-memory", "gbrain append <slug> --file new.md"), a complete page template with required frontmatter, named parser patterns with exact line shapes, and concrete output-format templates for the import receipt and tracing answer. The one absent artifact — a full converter script — is explicitly justified ('Provider formats drift between export versions — inspect the actual JSON before writing the converter'), satisfying the pseudocode exception.

5 / 5

Workflow Clarity

The import procedure is a clearly sequenced six-step pipeline (parse → redact pre-write → convert → trial-before-bulk → import → parser validation → fact extraction) with explicit validation checkpoints at exactly the right places: 3-5-conversation trial run before bulk, gbrain conversation-parser scan before bulk conversion, --dry-run cost preview before the paid run, and a gap diff where 'a second pass reporting zero gaps is the done signal — one pass is not'. Feedback loops are spelled out for error recovery (fix the converter and regenerate rather than hand-patch; resume_command after a cost-cap stop; tail_changed refusal → re-read → append again), meeting the top anchor for a batch workflow.

5 / 5

Progressive Disclosure

Section headers are clear and every cross-link to sibling skills/conventions is clearly signaled with its purpose (one level deep, never nested), so navigation is not the problem. But this is a ~450-line monolithic SKILL.md with no bundle files at all (no references/, scripts/, or assets/ exist) — detailed catalogs that would fit reference files (the redaction pattern catalog, the three-invariants root-cause narrative, the append/edit_page concurrency mechanics, the native-vs-manual delta) are all inlined, matching 'content that should be separate is inline' with good-but-not-optimal organization.

3 / 5

Total

16

/

20

Passed

Description

71%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.

The description is specific and information-dense, enumerating the full pipeline (import, validate, extract, backfill, retrieve) in concrete terms with strong natural trigger phrases. Its one structural weakness is that the 'when to use' guidance is absent from the description text itself — it lives in separate frontmatter fields (when_to_use, triggers) — which caps completeness at the 'clear what, weakly implied when' anchor. Folding an explicit 'Use when...' clause with the concrete trigger phrases into the description would make it a top-anchor example.

Suggestions

Add an explicit 'Use when...' clause to the description text itself (e.g. 'Use when the user mentions a chatgpt/claude/perplexity export, asks to import or search past conversations, or asks "when did I first discuss X"') so completeness is not capped at 3.

Include file-format synonyms in the description, such as 'conversations.json' and 'export file', to push trigger-term coverage from good to comprehensive.

Add one boundary phrase to the description (e.g. 'downloaded export files, not live account syncing') to reduce overlap risk with any live chat-connector skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: "Import AI-assistant chat exports (ChatGPT, Claude, Perplexity) and agent session transcripts into the brain as one dated page per conversation under conversations/", "validate each page against the native conversation parser", "extract facts via the native conversation-facts flow", "keep the archive gap-free with a detect-and-backfill loop", plus retrieval actions ("trace how an idea evolved", "pull a specific thread"). Every clause names a specific operation, matching the 'multiple specific concrete actions; comprehensive coverage' anchor.

5 / 5

Completeness

The 'what' is clearly and comprehensively answered (import → validate → extract facts → gap-heal, then retrieval/tracing), but the description text contains no explicit 'Use when...' clause — usage timing is only weakly implied by the retrieval examples. Per the guideline that a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3, this matches the 'clear what, when missing or weakly implied' anchor (explicit trigger guidance exists only in the separate frontmatter when_to_use/triggers fields, not in the description being evaluated).

3 / 5

Trigger Term Quality

Good natural-phrase coverage: provider names ("ChatGPT, Claude, Perplexity"), "chat exports", "session transcripts", and the highly natural user phrasing "when did I first discuss X". A few common variations are absent from the description text itself (e.g. file extensions like conversations.json, "search my conversations"), so it sits just below the 'comprehensive coverage including synonyms and file extensions' anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — the export-file import lane ("chat exports", "session transcripts" into dated conversations/ pages) plus archive tracing — with distinct provider-named triggers. Minor overlap risk remains with sibling skills for live chat syncing and whole-brain idea tracing ("trace how an idea evolved across past conversations"), which the description does not explicitly disambiguate, so it fits 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict anchor.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 17 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

plugin-variants/gbrain-daily/skills/conversation-archive/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.