gamma-migration-deep-dive
Deep dive into migrating to Gamma from other presentation platforms. Use when migrating from PowerPoint, Google Slides, Canva, or other presentation tools to Gamma. Trigger with phrases like "gamma migration", "migrate to gamma", "gamma import", "gamma from powerpoint", "gamma from google slides".
70
64%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-migration-deep-dive/SKILL.mdQuality
Discovery
79%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 excels at trigger term coverage and completeness, with explicit 'Use when' and 'Trigger with' clauses that make it easy for Claude to select. However, it lacks specificity about what concrete actions the skill performs—'deep dive into migrating' is vague and doesn't enumerate actual capabilities like converting slide formats, handling embedded media, or mapping layouts. The description would benefit from replacing the vague opener with concrete action verbs.
Suggestions
Replace 'Deep dive into migrating' with specific concrete actions, e.g., 'Converts slide decks, maps layouts, transfers embedded media, and handles formatting differences when migrating to Gamma from other platforms.'
Remove fluff phrases like 'deep dive' and instead list 2-3 specific migration tasks the skill handles (e.g., 'import .pptx files, remap slide templates, resolve formatting issues').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'deep dive into migrating' but does not list any concrete actions (e.g., convert slides, map layouts, transfer animations, handle embedded media). 'Deep dive' is vague fluff rather than a specific capability. | 1 / 3 |
Completeness | It explicitly answers both 'what' (migrating to Gamma from other presentation platforms) and 'when' (with a 'Use when' clause and explicit trigger phrases). Both are clearly stated. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'gamma migration', 'migrate to gamma', 'gamma import', 'gamma from powerpoint', 'gamma from google slides', plus mentions of specific source platforms (PowerPoint, Google Slides, Canva). These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Gamma' as a specific target platform and migration as the specific task creates a very clear niche. It is unlikely to conflict with general presentation skills or other migration skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for migrating presentations to Gamma with clear steps and useful reference tables. However, it suffers from relying on unverified/assumed API surfaces (createGammaClient, generateFromTemplate), lacks validation checkpoints between critical batch steps, and is somewhat verbose for what could be a more concise guide. The code examples are illustrative but not confidently executable.
Suggestions
Add an explicit validation step between content extraction (Step 2) and batch migration (Step 3)—e.g., 'Review extracted text for at least one presentation before running batch migration' with a concrete check.
Clarify or verify the Gamma API surface used in examples (createGammaClient, gamma.generate, gamma.generateFromTemplate)—either reference the actual SDK documentation or note these are illustrative patterns that need adaptation.
Split the lengthy extraction and migration scripts into separate referenced files (e.g., scripts/extract-pptx.ts, scripts/migrate-to-gamma.ts) and keep SKILL.md as a concise overview with usage examples.
Add a retry/recovery mechanism to the batch migration script for failed items, since batch operations without feedback loops are fragile.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary verbosity. The inventory script (Step 1) is quite long for what it does, and the overview section explains the concept of Gamma migration at length. The tables and checklists are useful but the overall document could be tightened—e.g., the 'Key insight' callout explains something that could be a single sentence. | 2 / 3 |
Actionability | The TypeScript code examples are fairly concrete but rely on assumed APIs (createGammaClient, pollUntilDone, gamma.generate, gamma.generateFromTemplate) that are not defined or verified as real. The PPTX extraction code is more grounded but uses xmldom in a way that may not be fully executable without additional setup. Step 4's template recreation mixes UI instructions with code that references unverified API endpoints. | 2 / 3 |
Workflow Clarity | The 5-step sequence is clearly laid out and Step 5 provides a validation checklist, which is good. However, there are no explicit validation checkpoints between the batch migration steps—no 'verify extraction output before proceeding to generation' step, and no error recovery loop for the batch migration (failed items are just logged, not retried). For a batch/destructive operation like migrating many presentations, this gaps caps the score at 2. | 2 / 3 |
Progressive Disclosure | The skill references external resources (Gamma docs, gamma-core-workflow-a, gamma-install-auth) but no bundle files are provided to support them. The document is quite long (~200 lines of content) and could benefit from splitting the extraction scripts and migration scripts into separate referenced files. The structure within the file is decent with clear sections, but it's borderline monolithic. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.