migrate

Universal migration from Obsidian, Notion, Logseq, markdown, CSV, JSON, Roam

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/migrate/SKILL.md

Quality

Content

85%

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

The body is well-structured with strong workflow validation and progressive disclosure, but actionability is uneven: only Obsidian has executable commands while other sources rely on procedural steps without CLI syntax.

Suggestions

Add executable gbrain CLI commands for the other sources (Notion, CSV, JSON, Roam), mirroring the concrete 'gbrain extract links' example used for Obsidian.

Document actual command syntax for the tools listed in 'Tools Used' (get_page, get_stats, get_health, search) so the steps are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no explanation of concepts Claude already knows; every section (Contract, sources table, Phases, Verification, Anti-Patterns, Output Format) earns its place.	3 / 3
Actionability	Only the Obsidian section gives an executable command ('gbrain extract links'); Notion, Logseq, CSV, JSON, and Roam are procedural instructions without command syntax, and 'Tools Used' lists tool names without CLI usage.	2 / 3
Workflow Clarity	The batch migration has explicit validation checkpoints: a 5-10 file sample test before bulk import, a dedicated Verification section, and Anti-Patterns warning against skipping verification.	3 / 3
Progressive Disclosure	A single self-contained file with no dead or nested references and well-organized sections; the concise overview (table + Phases) and brief per-source detail are appropriately inline.	3 / 3
	Total	11 / 12 Passed

Description

72%

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 distinctive and uses natural trigger terms, but it lists only the high-level action 'migration' and omits an explicit 'when to use' clause, capping specificity and completeness.

Suggestions

Add a 'Use when...' clause naming trigger scenarios, e.g. 'Use when migrating notes or docs from Obsidian, Notion, Logseq, or Roam into GBrain'.

List concrete actions beyond 'migration' (convert cross-references, verify round-trip, build typed links) to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the migration domain and seven concrete sources, but the only action stated is 'migration' with no list of concrete operations (convert, verify, link).	2 / 3
Completeness	States what the skill does but lacks a 'Use when...' trigger clause in the description, so the 'when' is only implied.	2 / 3
Trigger Term Quality	The source names (Obsidian, Notion, Logseq, Roam) and 'migrate from' are exactly the natural terms a user would say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (migration of named note/wiki tools into GBrain) with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: garrytan/gbrain
Path: skills/migrate/SKILL.md
Commit: 3fafb69

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

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.