CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate

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

Quality

72%

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 ./skills/migrate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 dense, largely executable migration runbook whose strongest assets are explicit sequencing, operator-approval gates, thorough post-migration validation, and concrete error-recovery guidance. Its weaknesses are duplicated requirements across sections and per-source sections (Notion, CSV, JSON, Roam) that lack the concrete commands the company and Obsidian paths enjoy.

Suggestions

Deduplicate the safety rules: state the additive-only and no-bypass rules once (in the Contract or "When it fails" section) instead of repeating them across the company-repositories section, and merge the overlapping Phases and Verification steps.

Add a concrete put_page example for the generic path (e.g., one CSV row mapped to slug/frontmatter/compiled_truth) so Notion, CSV, and JSON migrations are as executable as the company-repository and Obsidian paths.

Move the "(v0.12.1+)" version pin out of the workflow prose into a version-compatibility note so time-sensitive details don't burden the main instructions.

DimensionReasoningScore

Conciseness

The body is almost purely instructional with no conceptual padding, but requirements are repeated: the additive-only rule appears as both "Never fix the source files or commit dirty changes automatically" and the Anti-Pattern "Never modify, move, or delete the source files"; the global-schema bypass warning and "missing embeddings are expected" each appear twice; the Phases and Verification sections restate the sample-test and health-check steps; and a version pin "(v0.12.1+)" is embedded inline. This fits "mostly efficient but could be tightened" rather than anchor 4's minor-trimming level.

3 / 5

Actionability

The company-repository and Obsidian paths give exact executable commands with flags ("gbrain sources connect <path> --brain <id> --source <id> --profile company-brain --json", "gbrain sync --brain <id> --source <id> --no-embed --no-pull", "gbrain extract links --source db --dry-run"), but the Notion/CSV/JSON/Roam sections offer only procedural steps like "Map columns to frontmatter fields" with no concrete command or put_page example. Mostly executable guidance with moderate gaps — above anchor 3, below anchor 5's copy-paste coverage of common cases.

4 / 5

Workflow Clarity

Sequencing is explicit with validation gates and feedback loops throughout: "Test with a sample. Import 5-10 files, verify by reading them back", "Only after the operator approves that preview, rerun with --yes", a five-item verification checklist (page count, health, round-trip export, spot-check, search test), and a "When it fails" section with specific failure modes and a resume command. This is a batch operation whose validation is thorough, so no cap applies, and it matches anchor 5's explicit-checkpoint, error-recovery profile.

5 / 5

Progressive Disclosure

Headers, a supported-sources table, and clearly signaled one-level references ("Read skills/conventions/brain-routing.md and skills/conventions/untrusted-content.md first", "Full behavior and errors: docs/guides/company-brain-ingestion.md") give good structure, but no bundle files exist to back the referenced paths, and the ~30-line company-repository procedure plus per-source guides are inlined rather than split into reference files. Good structure with minor organization gaps — below anchor 5's clean overview-plus-references split.

4 / 5

Total

16

/

20

Passed

Description

61%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 identifies a concrete, distinctive niche (migrating seven named note/wiki tools) but omits any "when to use" guidance, does not name the destination system, and leans on the buzzword "Universal" instead of concrete actions. It is serviceable for routing but well below the model examples' standard of stating both what and when explicitly.

Suggestions

Add a "Use when..." clause, e.g., "Use when the user asks to migrate or import an existing vault, wiki, note export, or tabular data into GBrain", to raise completeness above the cap of 3.

Replace the buzzword "Universal" with 1-2 concrete actions, e.g., "Imports pages, converts wikilinks and block refs to typed links, and verifies round-trip", and name the destination (GBrain) in the description itself.

Fold natural trigger phrasings already used in the frontmatter triggers ("migrate from", "import from") and synonyms like "vault" and "wiki" into the description for fuller keyword coverage.

DimensionReasoningScore

Specificity

"Universal migration from Obsidian, Notion, Logseq, markdown, CSV, JSON, Roam" names the domain and one action with a concrete enumeration of seven source formats, but never states what the migration does (e.g., importing pages or converting links). It is more informative than anchor 2's single domain mention but lacks the multiple concrete actions of anchor 4, and "Universal" is a buzzword over-claim.

3 / 5

Completeness

The "what" is clear (migration from seven named source systems), but the description contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3; the destination system (GBrain) is also never named. Not 2 because the "what" is concrete, not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "migration", "Obsidian", "Notion", "Logseq", "markdown", "CSV", "JSON", "Roam". Common variations like "import", "vault", "wiki", "notes", and file extensions are missing, so it falls short of anchor 5's comprehensive synonym coverage but exceeds anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The named tools ("Obsidian", "Notion", "Logseq", "Roam") carve out a distinct migration niche unlikely to trigger the wrong skill. However, "Universal migration" plus the generic formats "markdown, CSV, JSON" leaves minor overlap risk with any import/transform skill, keeping it below anchor 5's minimal-conflict bar.

4 / 5

Total

14

/

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: 1 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

skills/migrate/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.